Jessie based VyOS - Crux
Wed, Apr 17
Please retest on 1.2.1
Tue, Apr 16
ok. @UnicronNL please reject my PR then. thx.
@yun What is the exact frr command you tried?
the command you tried manully.
@hagbard This commit adds a route to the kernel routingtable and bypassing FRR, this is no good and this would break. Please make the script add the appropiate commands to frr instead. This way frr will be in charge of populating the kernel table. Also note that this route needs to be removed on dhcp release
@hagbard that commit sets a kernel route. that is not good.
@yun it's only that single line.
Any news about this ?
I would to see this committed. But do we also know what causes the issue? Is it with FRR or was this script just missing the ip command to set the default gw?
Sat, Apr 13
Thu, Apr 11
Wed, Apr 10
With apologies (not having used Phabricator before), I think I may not have filed this bug report correctly. I also did not intend to "triage" it when filing it, as this should be done by a responsible adult! :-)
Tue, Apr 9
Sun, Apr 7
Assuming this works - please reopen if not
Fri, Apr 5
https://github.com/vyos/vyos-replace/pull/1 awaiting review, I have no commit privs.
Wed, Apr 3
Fri, Mar 29
Thu, Mar 28
Not sure if the l2tp/vti modification merits inclusion - that depends on personal configuration of which tunnel is inside the other. I can't think of any reason not to make igmp-proxy start later though, but what would the most universal value be? I set mine to 902 since the l2tp tunnel was changed to 901, but perhaps it should start even later than dhcp, to make sure all addresses are assigned to the system prior.
Could you tell us the exact modifications? Or even better - send a Pull Request via GutHub so we could include it into VyOS.
That worked, thanks. Had to set it to 901, the vpn node was 900. Added a sed to the preconfig script so it survives updates.
Wed, Mar 27
@c-po accel-ppp is a server, the pppoe client in vyos is rp-pppoe, which causes the issue.
ppp works and Acks the IPv6 address:
@c-po, Accel-ppp support next option in [pppoe] section
You can try playing around with the priority in the l2tpv3 node.def files. Higher priority means its executer later. DHCP for instance uses 900-something.
I can confirm that as soon as IPv6 is enabled on pppoe0 the interface is no longer renamed from ppp0 to pppoe0.
I switched to a L2TPv3 tunnel for better performance than OpenVPN, still will not come up at boot if it depends on the vti interface.
@tomjepp please test