So far I have seen that BFD for static routes in FRR is currently under development:
https://github.com/FRRouting/frr/issues/3369
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Sep 28 2020
Sep 27 2020
Yeah, I'm going to second the motion on this one. I've been down the road of SNMP before, and just navigating the available metrics and trying to figure out what they are is less than straightforward. I mean, I've been at this sysadmin thing for a bit over 10 years now and I couldn't manage something useable out of it. It might be because I'm not a great sysadmin, but a lot of people are not great sysadmins. 馃槢 Having this feature would be great for accessibility and discoverability.
This issue also exists in:
Version: VyOS 1.3-rolling-202009271030 Release Train: equuleus
Write redundant and intrusive code for all interface types, which may introduce unknown errors (I can鈥檛 guarantee 100% accuracy without testing)
@c-po I am thinking about a problem. Placing proxy-ndp under the child node of interface may generate redundant implementation code and is intrusive. In fact, for proxy-ndp, only one configuration file is needed. Is this Reasonable? I don't even know how to fully test whether the intrusive code affects the basic functions of the router.
Sep 26 2020
It looks like this problem is around here
https://github.com/vyos/vyatta-cfg/blob/current/etc/bash_completion.d/vyatta-cfg#L280-L290
backported to crux
Testing on crux
That鈥檚 how it is now and it doesn鈥檛 work.
vyos@r2-roll# set interfaces ethernet eth0 vif 15 ip proxy-arp-pvlan [edit] vyos@r2-roll# commit
Cant we run dhcpd as dhcp user which is also a member of hostsd group?
@kroy could you be so kind and write a smoketest for it, too?
This is a problem again.
Sep 25 2020
PR should correct this
cpo@LR1.wue3# commit [ interfaces ethernet eth1 ] Interface MTU too high, maximum supported MTU is 9000!
Yes that's correct. And there is already some sort of check implemented for the node traffic-policy, so it does not fail when the pppoe interface does not exist yet. It just shows a warning: https://github.com/vyos/vyatta-cfg-qos/blob/bbf2b2f06b7a0f883f7134df5e2b3e089015738e/scripts/vyatta-qos.pl#L198
I think I know what's happening here.
I would also like to add that wouldn't it make more sense to set the protocol mode under host aswell rather behind "facility".
Sep 24 2020
I saw that the new build was online, so I added the image, rebooted and tried to issue the command again.
Everything seems to work, no error when committing and the route is added.
After the fix an error is reported on the CLI: