@jjakob detect_if_systemipv6_is_disabled just an idea, but looking to interfaces-openvpn.py, it's easy:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Apr 23 2020
Disabling IPv6 on the system is something not mainlined in VyOS - there are open PRs on GitHub which needs to be approved by @dmbaturin. As Disabling IPv6 would also require the CLI to disable all IPv6 inputs dynamically which is something not possible at the moment.
Looks good. Is detect_if_systemipv6_is_disabled() already a
system function? If so, It can be incorporated (by you if you wish, or by
me). The last line is missing += by the way.
This code doesnt break if ipv6 is disabled by system wide:
Apr 22 2020
Yup that did it. Thanks!
The form will be made consistent with other commands, using an explicit 'op' (show|generate) and 'path' as list of strings. For example:
First, I thought you had merged the patch, as you did not, there is no duplication ATM.
This may possibly be the cause of some bugs?
If the interface exists, it is perfectly harmless: it was the previous behaviour. The example where it can cause issue when a interface name is used and does not exists as it will create it. So really op_mode commands.
There are places in the code where operational commands are still ran without create=False, for example:
https://github.com/vyos/vyos-1x/blob/675f400bacb03ae93be928e7270f89205d1036b9/src/conf_mode/interfaces-bonding.py#L242
Fixed in the latest rolling.
Fixed.
Fixed in the latest rolling
sever@r11:~$ show vrrp VRRP is not running sever@r11:~$ show vrrp detail VRRP is not running sever@r11:~$ show vrrp statistics VRRP is not running sever@r11:~$
I prefer the first one as it is proven to work since VyOS 1.2.x
Works for me
Apr 21 2020
The above PR is tested to fix this issue and T2345.
https://github.com/vyos/vyos-1x/pull/372 will now not display tunnel (but gre-bridge) as options for bridge. Still not preventing them to be used.
works if run as root (or sudo) but not as it.
Make sense, because IPIP this is L3, the bridge is L2.
In this case, we should not show L3 as an allowed interface for bridge.
/sys/class/ieee80211 does not exist on VirtualBox perhaps the interface configuration should fail it is missing ?
So the commands were not on crux under the tunnel section and trying to use either ip link or brctl is failing:
crux has another syntax, but interface tunnels not bridgeable in crux
For all the bridge issues, I wanted to see what was happening on crux, taking T2356 as reference:
With this patch, all works as expected. Thanks @thomas-mangin
Related with https://phabricator.vyos.net/T2223
Ah, I figured it out - the contents of vyos.log.debug are used as the path to the logfile, if empty (but present) the default /tmp/developer-log will be used, otherwise no logfile will be written. But I think I've hit a bug - if multiple 'flag' are set (other than 'log') the system hangs during boot.
Fixed in latest rolling
sever@r11-ansible# set interfaces ethernet eth3 description test [edit] sever@r11-ansible# commit [ interfaces ethernet eth3 ] Interface ethernet eth3 does not exist