weird, the code is actually there:

That should actually not be possible with the verify() step - looks like a bug in the code

Sure, go ahead. Thanks!

Pull request: https://github.com/vyos/vyos-1x/pull/303

I could not tell you why it was decided to be this way.

As indicated, I could not test this patch.

https://github.com/vyos/vyos-1x/pull/300

Pull request: https://github.com/vyos/vyos-1x/pull/301

This work is now completed.

@kroy could you please confirm that we can close this issue :-)

duplicate of T149 ?

I can try to tackle this if noone else is working on it.

This is the logic from my old wireless-hostapd.pl file:

https://github.com/vyos/vyos-1x/pull/299

https://github.com/vyos/vyos-1x/pull/298

1.3 rolling does not affect.
PR for CRUX https://github.com/vyos/vyatta-cfg-system/pull/122

This is the logic from my old wireless-hostapd.pl file:

Here is the logic from my old wireless-hostapd.pl file:

Aye, from what I see in my old wireless-hostap.pl, logic should go like this. Every "print" is output to the wlanX.cfg which serves as config input for hostapd.

PR https://github.com/vyos/vyos-1x/pull/297

Sorry, this is actually invalid as this patch is used in upstream Debian PPP

Hi @alainlamar how should the generated configuration look like?

Can highly recommend: http://repo.saltstack.com/2019.2.html#debian (includes Jessie)

@jjakob thank you for the detail. I will work on it.

Currently none of the offloading (gro, gso, sg, tso, ufo) settings are checked either at src/conf_mode/interfaces-ethernet.py verify() or in the module python/vyos/ifconfig/ethernet.py. Setting one of these when the driver doesn't support it will result in an unhandled exception. This may not be so disastrous when setting the options in config mode, as the commit will fail due to the exception, but will have more disastrous results when a config which has these options set is loaded into a system with NICs that don't support it - this will cause boot time commit to fail. As per T2158 and PR#272 none of these calls should result in an exception, but rather just print a warning and continue.

To track similar https://github.com/FRRouting/frr/issues/4471

My main question is why is this message displayed and do we need to worry.

I have had the maximum-paths setting for years since Vyos 1.1.x and I have a lot of routes ipv4 and ipv6 installed in the routing table with 2 or 3 routes even if they are not the same. I am not specifically using ecmp I just have multiple routes for fast failover.

For the ECMP it's necessary that as-path length, weight, localpref, med, etc were the same.
Only, in that case, more than one eq route will be installed in the routing table.

Fix in https://github.com/vyos/vyos-documentation/pull/234