Also supported in EdgeOS

Pull request: https://github.com/vyos/vyos-build/pull/48

Could we work around this by implementing an overlay for every commit, with the entire stack of overlays being combined with the root overlay when a save is issued?

After some more investigation, dhcpd6.leases in /config/ and /opt/vyatta/etc/config/ are the same.
In the same config folder there's also dhcpdv6.leases (with the letter "v" before 6) that's a leftover from an older image.

-rw-r--r-- 1 root root       3262 Jun 12 14:55 dhcpd6.leases
-rw-r--r-- 1 root root       2615 Jun 12 14:23 dhcpd6.leases~
-rw-r--r-- 1 root root      27726 Jun 12 14:30 dhcpd.leases
-rw-r--r-- 1 root root      28072 Jun 12 14:22 dhcpd.leases~
-rwxrwxr-x 1 root vyattacfg  8141 Oct 27  2018 dhcpdv6.leases
-rwxrwxr-x 1 root vyattacfg 17618 Oct 27  2018 dhcpdv6.leases~

If I delete these two, I get a nice traceback when running show dhcpv6 server leases:

vyos@vyos:~$ show dhcpv6 server leases 
Traceback (most recent call last):
  File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 81, in <module>
    leases = get_leases(lease_file, state='active')
  File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 44, in get_leases
    leases = IscDhcpLeases(lease_file).get()
  File "/usr/lib/python3/dist-packages/isc_dhcp_leases/iscdhcpleases.py", line 110, in get
    with open(self.filename) as lease_file:
FileNotFoundError: [Errno 2] No such file or directory: '/config/dhcpdv6.leases'

So it seems that at some point the dhcpd leases filename was changed without updating the name everywhere else (and leaving the old files dangling).

Fully supportive of this. My ISP (Swisscom) require the setting of DHCP option 60 (vendor-class-identifier) in order for an IP to be granted to xDSL lines.

Why plural and not singular dhcp-option?

https://github.com/jestabro/vyos-1x/tree/load-config

For completeness, this was discussed in slack:

@etfeet you also get

mdadm: WARNING /dev/sda3 and /dev/sda appear to have very similar superblocks.
      If they are really different, please --zero the superblock on one
      If they are the same or overlap, please remove one from the
      DEVICE list in mdadm.conf.

maybe you can try my post above also then?

@jmlccdmd Strange is the superblock on /dev/sda, without uefi we use sda1 for raid and with uefi sda3.
Could you clear the superblock from sda and sdb and maybe try again?

It looks like the check that determines if 'mdadm --zero-superblock' is needed does not work.
Also ill try to get the config in with update-initramfs so that it does not go to md127.

Just discovered the problem, my mistake, sorry!

Just did a fresh build w/o problems - seems you downloaded the sources instead of git clone as suggested by @runborg

When you downloaded vyos-build did you download it or used git clone? It complains about an invalid git repository so i suppose you used the download option?

Yes, this is a fresh container...

Is the vyos-builder container newly created?

This is the command used to enter docker container:

What command did you use when starting the docker container? Make iso also require sudo to run but missing sudo that not generate that error message

SNMP can be used as a workaround, but it is not suitable for much more than a couple metrics because is it very inefficient. Moreover the prometheus node exporter provide many more metrics out of the box.

In T1416#37376, @c-po wrote:

Unfortunately this was a miss understanding between @zsdc and me, but the provided fix targeted the same direction.

You can scrap SNMP to prometheus. Not sure if you want any gauges not covered by snmp

All you need for ssh keys to work for AMI is to add cloud-init package in configure step:

All items should be fixed.

This bug must be fixed in current rolling, because of T1416. @dongjunbo, check this, please.

Unfortunately this was a miss understanding between @zsdc and me, but the provided fix targeted the same direction.

I have ran into this as well where we have a router plugged into a juniper switch, the router loads faster then the juniper so at the moment the router comes up all the interfaces are down, then the switch comes up.

Fix pushed.

It was resolved with https://github.com/vyos/vyatta-cfg-quagga/pull/27/files#diff-2d07759ce6afdf217934849f11a824f6

Is there any chance to get this feature back into 1.2.x? I could heavily use this for management traffic and for pinning tunnels to specific interfaces.

I was looking on this issue. Please find below a description of what I think is the root cause for this issue:

@hagbard
Yes, it is still an issue. I just did some test with my hardware. If all interfaces are disconnected, I can't create the l2tpv3 interface. If I have the interface up and a default route set, I can create a l2tpv3 interface on the system.

It didn't fix my problem. I don't think it is caused by the igb driver.

I've tried upgrade version from 3.8.2 to 3.9.0 by replacing the ddclient executable (downloadable from the official site) in /usr/sbin/ddclient
This version needs also the libdata-validate-ip-perl package installed.
After that, reload the configuration and it works.

In T1416#37304, @c-po wrote:

Please test and verify with latest rolling

IMHO this was fixed by @rherold and is merged into the latest rolling. Please verify if the issue still exists.

I can reproduce this Bug. Please priotize it's critical not to have iBGP

@SteveP latest ISO has the driver updates, please test.

@dmbaturin is there any reason the IPv6 peer-group is under address-family ipv6-unicast and the IPv4 peer-group is not? Seems this one was missed during migration?

Please test and verify with latest rolling

Added pull requests:
https://github.com/vyos/vyos-1x/pull/69
https://github.com/vyos/libvyosconfig/pull/2
https://github.com/vyos/vyatta-cfg/pull/18
https://github.com/vyos/vyatta-conntrack/pull/1

build-ami is working for me if I remove disable-password-authentication from the config template and add in a password into the config template. I have come across another issue though. I was able to get it to work in us-east-1 and us-east-2, but I can't deploy into us-gov-west-1. First problem was it couldn't find a debian-jessie image but that was solved by changing the owner from 379101102735 to 256493402735. Now it's throwing an 401 when attempting to list all subnets. I'm guessing that the python code pulled from ansible is configured for a specific region or the cli command used in GovCloud is slightly different. Either way it's not working.