Gonna keep the task open for a week or 2 to see if there are still any other issues.

It should work, at least it does for me. ether-resume is my script, it just makes sure that dhcp is called when it was configured, if not is just call the interface up and reapplies the IP address. Routes should be in frr anyway and with the interface up again, these would become active again as well. Netplugd calls scripts on event, up and down and doesn't call anything within open-vm-tools.

https://vyos.readthedocs.io/en/latest/services/pppoe-server.html#bandwidth-shaping

https://github.com/vyos/vyos-1x/commit/d4556b31e920197e1c58febb8d87a1765bfea81f for RADIUS

local-users implementation: https://github.com/vyos/vyos-1x/commit/c1dc93391b9ec1785ab648fa7685521c85774d28
radius based shaper settings in progress, which is then the last item.

op-mode has been implemented and will be available in the next rolling release. (https://github.com/vyos/vyos-1x/commit/d748e526ca50f3acb98ec511fab977c4b044aea8)
Conf mode commands are in progress.

I haven't planned to extend anything for it.

@dmbaturin I don't have access to push it, please review and apply/reject PR.

ok. @UnicronNL please reject my PR then. thx.

@yun it's only that single line.

@syncer The only thing I can do it monitoring upstream, which hasn't released a patch for over a year to address that issue.

https://github.com/vyos/vyos-replace/pull/1 awaiting review, I have no commit privs.

• checks now for the existence of variables instead of overwriting the predefined defaults (https://github.com/vyos/vyos-1x/commit/99b2bfc74f30987d00384e384e8caa4fad28528b#diff-393bdd2f2828daf4f3a67bc8b46fcce9)

https://vyos.readthedocs.io/en/latest/system/systemusers.html?highlight=login

I think vyos is the default, so I'll weave it into host_name.py as a default if not present in the default config.boot. Not sure why there is that difference, but on the other hand the script should and can handle missing variables.

I agree, however (https://blog.vyos.io/the-operator-level-is-proved-insecure-and-will-be-removed-in-the-next-releases) :
[...]
in the next releases that feature will be removed and operator level users will be converted to admin
[...]

Looks like the option level can be removed entirely.

Migration script will be in the next rolling release (vyos-1x). Since level admin is the only level, I think it can be removed from the options tree entirely and set automatically in the config.

if host-name is not set and an IP is given to an interface script causes a an exception - maybe a default hostname could be set if the option is not in config.boot. Happens if you wipe config.boot and reboot. The default one won't have host-name configured and assigning IPs to interface still work but produce that nasty exception.

@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:

That option is no native rp-pppoe option, SuSE provided a patch for that feature in 2014 as far as I found out. I'm still looking for an option avoiding importing it into our repo and solve the issue with a script.

@trae32566 Please test with http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-cfg-system/vyatta-cfg-system_0.20.44+vyos2+current22_amd64.deb or the rolling release March26++

@zsdc Can you please test your use case? thx.

Working on interface-route. I think the best way is to stip that off as well, so basically interface-route has it's own script, set proto static route, route-map, table and so on too. Less likely to break when something needs top be changed, better code maintenance (at least that's what I hope for) and can be easily extended. Well, will test it out, so far there is a good performance benefit already.

Ok, so I found it. host_name.py is being called when dhcp had been configured and the system rebooted. vyatta-cfg-system didn't call host_name.py when an interface is configured via dhcp, so when you configure dhcp for the first time and don't reboot /etc/resolv.conf stayed empty.
I need to test it in crux, but i think there is the same issue, therefore you would need 2 commit in crux, host_name.py and the one from the address node in vyatta-cfg-system.

There is still an issue with it, when the system is rebooted all is working as expected, but when you configure dhcp on the fly, hostname.py is still doing something weird and leaves resolv.conf broken.

arp - https://vyos.readthedocs.io/en/latest/routing.html#arp

cherry-picked (https://github.com/vyos/vyos-1x/commit/361a4419e0042369fae7eddf67f06a658372db93)

cherry-picked. (https://github.com/vyos/vyos-1x/commit/d0d044918ae10b2a5db1a4f218adef4187ca7e22)

Fixed in: http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-cfg-quagga/vyatta-cfg-quagga_0.19.1+vyos2+current9_all.deb or next rolling release.

Issue verified, new bug ticket or shall we use this one to resolve the issue. Looks like it's been broken for a while.

set protocols static route 10.100.100.0/24 next-hop 10.1.1.1 next-hop-interface eth1

@syncer @zsdc tested the rolling from tonight, works as far as i can tell, however it looks like 'delete protocols static ip' doesn't work. Not sure if it was always broken or not, I have a look into it asap.

@syncer The requested feature wasn't working as it should, already removed it. The current implementation is and was working as expected.

@zsdc it's in http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-cfg-quagga/vyatta-cfg-quagga_0.19.1+vyos2+current8_all.deb, but you better wait until the rolling release is working again, there were some frr dependencies added, which makes the packge not backward compatible. If you need it urgently, I can compile you a working one which works on the older releases (it's really only a dependency issue). So far I have it only implemented for IPv4 routes, let me know if you need it for route6 as well. I planned to start with the backend rewrite for frr asap.

@zsdc would the below help you?

https://vyos.readthedocs.io/en/latest/vpn.html#pptp-server

Sorry I can't replicate your issue, tested it with VyOS 1.2.0-rolling+201903110337.

http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.3.0-14_all.deb or tonights rolling. systelog will still run and will log journalctl messages.

journalctl needs systlsog since it's supposed to it's messages there, so the above commands won't stop rsyslog, but I'll fix the error for the cli.