DNS forwarding was last changed back in August by commit https://github.com/vyos/vyos-1x/commit/fdae741be5ffaa3719ce889d0342c3091ad3c92c
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Dec 8 2019
I can not reproduce this issue. I just upgraded to the specified version.
vyos@vyos:~$ show version Version: VyOS 1.2-rolling-201912080217 Built by: autobuild@vyos.net Built on: Sun 08 Dec 2019 02:17 UTC Build UUID: b998c0a6-ccf9-47ca-a8f8-7cc561bc5528 Build Commit ID: 7b47b452ce86a9
Please share commands to reproduce this. We do kot hve a 1.2.3 rolling version.
Dec 7 2019
@zsdc It looks like after boot the DHCP DNS and search does indeed disappear, it just appears to take a minute, so I guess this can be closed (though it seems odd it would get added at all, but I guess that's alright).
Dec 6 2019
Trying to apply the fix manually:
Built a fresh rolling. It failed with:
FRR will serve RAs in the future.
https://downloads.vyos.io/rolling/current/amd64/vyos-1.2-rolling-201912061907-amd64.iso and later include the fix
SNMP community should stay. If it should be removed it can be handled via dedicates task
backported 20822ca3 to crux
Works as expected in VyOS 1.2-rolling and 1.3-rolling.
Hello @primoz , seems you right. left|rightnexthop deprecated in strongswan.
This parameter is usually not needed any more because the NETKEY IPsec stack does not require explicit routing entries for the traffic to be tunneled. If left|sourceip is used with IKEv1 then left|rightnexthop must still be set in order for the source routes to work properly.
And in CLI rolling l2tp implementation we need replace outside-nexthop to gw-ip-address.
I pick this up as I did the rewrite of this whole stuff
@Viacheslav thank you for testing!
I have tried multiple times to reproduce this with 1.2-rolling-201912060217 with no luck. It would be great if together with logs you will provide a detailed description of the environment. Because, possible that even CPU cores count or memory size can lead to some condition, in which dhclient-script cannot get proper values from config and add unwanted servers to the resolv.conf.
@zsdc Maybe Incorrect file location. "ddclient.pid"
Okay, so this problem just got a LOT more bizarre.
Dec 5 2019
The runtime errors are fixed by the above commit.
@kroy I can't really reproduce it if I disable the peer first when multiple peers are defined on the same wg interface.
Can you please do a touch /tmp/vyos.ifconfig.debug and then run your commands and post it here?
It will show you the commands execute for each step like:
vyos@wg01# set interfaces wireguard wg0 peer wg02 disable [edit] vyos@wg01# commit [ interfaces wireguard wg0 ] DEBUG/wg0 write '1420' > '/sys/class/net/wg0/mtu' DEBUG/wg0 write 'wg0' > '/sys/class/net/wg0/ifalias' DEBUG/wg0 cmd 'wg set wg0 peer G1aA2KkyFyC8xsCUeENvuIW8HC5yDxwi902nR20592Y= remove' DEBUG/wg0 cmd 'wg set wg0 listen-port 12345 fwmark 0 private-key /config/auth/wireguard/default/private.key peer hbwJSCu6SGUKIReNhWxlDIFRNCl5L7PaUSYOo2BF+Rg= preshared-key /dev/null allowed-ips 10.100.100.3/32 endpoint 10.1.1.203:12345 persistent-keepalive 0' DEBUG/wg0 cmd 'ip link set dev wg0 up'