- User Since
- Jan 18 2019, 4:03 PM (46 w, 2 d)
@zsdc It looks like after boot the DHCP DNS and search does indeed disappear, it just appears to take a minute, so I guess this can be closed (though it seems odd it would get added at all, but I guess that's alright).
Thu, Dec 5
Please reopen T1786 in case of further troubles.
I can't so I've reopened this one; I don't have permissions to do this :(
Mon, Nov 25
This is still broken for me on the most recent 1.3 rolling releases:
Tue, Nov 19
Hey, the comment I made above (which is now deleted) was incorrect, this works on 1.2 rolling, it is still broken on 1.3. Sorry for the confusion.
Mon, Nov 18
It looks like the domain and search are now working (and not showing the DHCP one as expected, so that is fixed too), but the DHCP nameservers are still there:
Sun, Nov 17
So just an update, this issue is still present on more recent VyOS 1.3:
It looks like this is indeed fixed now!
Just a note, I updated my docs above cause they were missing the OSPF+OSPFv3 portion of the interface config that enabled BFD :)
Oct 10 2019
I made a test lab at home for this, so let me know if you have any other settings or anything you need documentation for. Unfortunately my Arista device does not support multiple BGP instances at this time, so I've been unable to document BFD for BGP (I need a separate instance than my main one) so far, but I'll be trying other ways soon.
Oct 7 2019
I have a VyOS <-> Arista configuration, which should be similar to Cisco, if that works for y'all?
Oct 6 2019
Yes I'm currently utilizing the rolling releases in service after basic functionality testing, and so far BFD has worked flawlessly for all protocols I've tested.
Sep 25 2019
This feature is currently in the 1.2 rolling release.
Sep 21 2019
Just some feedback here, but this has been working flawlessly in all my environments so far for BGP, OSPF, and OSPFv3 ... you guys are awesome!
Apr 2 2019
@hagbard This now works; I tested with 1.2.0-rolling+201904010337. Thanks!
Mar 13 2019
Added a priority of normal, as this could potentially cause outages (situations where the interface comes up and causes an IP conflict, or causes dynamic routing issues due to the connected route)
Feb 26 2019
This bug is confirmed present on 1.2.0 final release as well.
Feb 23 2019
Just tested the most recent nightly (1.2.0-rolling+201902222123) and it works! Thank you so much y'all.