added to helium branch
Sat, Oct 21
An AMI updated by hand was submitted to Amazon for testing.
Fri, Oct 20
@dmbaturin tells that this does not work as expected
so i suggest reopen this task
Thu, Oct 19
Hi, can you please share the VHD file as well?
Wed, Oct 18
The proposed "maximum-paths" looks to set the maximum number of paths for equal cost routing and not limit the long AS path that causes the noted log entry. I used the following in a production network to work around the issue:
VyOS version 1.1.7 works very well with vmware and with network card vmxnet3, but for high performance on that platform you need do some system tunning.
Have you got any plan to add that performance tunning to default vmware image?
Latest version of OpenVPN is 2.4.4 and has multiple new features.
Tue, Oct 17
I tried to get this working on a good known OpenVPN TAP configuration. I can confirm that it's flaky and will require additional debugging.
Mon, Oct 16
- set protocols bgp 262766 maximum-paths ebgp 75
Thanks, I'm looking at it now.
I've just sent a pull-request related for this topic.
Please check them when you have time.
Sun, Oct 15
Moving this to 1.2 branch
lets implement changes proposed earlier
i still confuse how to patch it, please explain more. thanks
Sat, Oct 14
No, I got the patch for this patch, how should I proceed? I have some sessions with this problem.
Fri, Oct 13
This is definitely very important. I'm on AT&T UVerse, and I can't plausibly use VyOS for my network without support for DHCPv6-PD. I don't even need auto-configuration of RAs on the LAN ports if that would be difficult, but I at least need the support to request the prefixes in order to get them routed to my internal router.
Thu, Oct 12
Also, it doesn't seem to work because vtun0 is not coming up -- but that seems to be related to my specific config.
Well, I'd like to use bonding with round-robin load balancing over two VDSL2 uplinks to same provider with the same latency (my ISP wants a business account for MLPPP).
Run tcpdump on your WAN with filter ICMP to confirm probing goes haywire; should be pretty easy to spot as you employed four different targets.
The only remotely sensible use case I can see is active/standby bonding of L2 VPNs to provide redundant paths. But then again, the real answer to this is distributed switches such as openvswitch.
I've tried to attain this holy grail of combining VPNs to gain a faster more reliable link. Although my environment where multiple consumer WAN links with different specs. Yours seem to be more uniform/easier to handle so you might get away easier.
BGP configuration is definitely loaded after VTI configuration is loaded.
Thanks for transfering this.
it looks like good candidate
@dmbaturin already looked at it last year, but it seems it was without pd support than
Now, however, it looks like they added support for it and we maybe should consider it as main candidate
Looks like it works! I've added a static route for 188.8.131.52 to the OVH gateway (that's being routed to the bond0 interface with interface-route) and I can ping it :^)
I've copied it and I can set bond-group on the OpenVPN interface. I'll check if it actually works in a minute.
This also happens with the DHCP server configuration if the DHCP subnet is different than the one used on the LAN interface (when it's configured with VRRP by following the VRRP tutorial on the VyOS wiki).
@higebu already have images with it, because we phase out 1.1.x i think it should be ok
Fixed in both 1.1.8 and current.
Well spotted! Fixed the typos.
Should we add it to 1.1.8? It's a pretty big change, I'm not sure if it should be in a maintenance rather than a major release.
The commit is indeed in helium now.
That commit was in helium as well, but the real issue was in the debian install file: those paths were missing from it, so templates were generated but not included in the package.
Imported into 1.1.8
Works in nightly built but now Netflow is broken in the nightly build :(
Wed, Oct 11
@higebu can you add it for 1.1.8 (along with all required software like awscli) into 1.1.8 please
@c-po i will agree with your approach
i will ask to keep package versions output
@UnicronNL can you add
@UnicronNL or better add this to installer part
Assuming that 1.2 affected in same way,
moving it to 1.2 and suggest work on fix there
@dmbaturin now as we have bugzilla back, can you check this one ?
@dmbaturin can we update keepalived to fresh version in 1.1.x
or should we drop mark this as wontfix in 1.1.x?
Moving this to 1.2 than.
Let's fix it there
Certainly not fixed in 1.1.x - but I'll see what I can do with it. 1.2 has such completely different handling that I couldn't even guess what it does. I'll have to work out a lab to reproduce it. Might get to it at the weekend.