Fix pushed to current:
rVYOSONEXf8522f323ec2
and updated on test server.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Mar 27 2023
Looks good on 1.4-rolling-202303271007:
The site-to-site mode shows that tunnel not configured
Config:
set interfaces openvpn vtun52 description 'Site-to-Site' set interfaces openvpn vtun52 local-address xxx.xxx.0.1 set interfaces openvpn vtun52 local-port '1152' set interfaces openvpn vtun52 mode 'site-to-site' set interfaces openvpn vtun52 persistent-tunnel set interfaces openvpn vtun52 protocol 'udp' set interfaces openvpn vtun52 remote-address 'xxx.xxx.0.2' set interfaces openvpn vtun52 remote-host 'xxx.xxx.41.117' set interfaces openvpn vtun52 remote-port '1152' set interfaces openvpn vtun52 shared-secret-key 's2s'
interface:
vyos@vyos:~$ show int openvpn Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down Interface IP Address S/L Description --------- ---------- --- ----------- vtun52 10.52.0.1/32 u/u Site-to-Site
Output show openvpn
vyos@vyos:~$ show openvpn site-to-site No OpenVPN interfaces configured vyos@vyos:~$
Most of the match rules results in:
Mar 26 2023
Mar 25 2023
Mar 24 2023
This sort of config should absolutely persist across both reboots and upgrades!.
it will be option b) it will be persistent accross reboots but not accross upgrades as only files in /config will be migrated to the new image version.
We could also alter the path to /config/user-data/ or make /etc/keepalived/conf.d/ a symlink to /config/user-data/ so that those files will be migrated during an upgrade.
PR for 1.4:
https://github.com/vyos/vyos-1x/pull/1911
PR for 1.3:
https://github.com/vyos/vyos-1x/pull/1912
Mar 23 2023
Mar 22 2023
Added initial implementation here:
Mar 21 2023
All 3 original issues are still present on 1.4-rolling-202303170317.
Looks good on 1.4-rolling-202303170317:
PR https://github.com/vyos/vyos-1x/pull/1901
set service ipoe-server authentication mode 'noauth' set service ipoe-server client-ip-pool name first-pool gateway-address '192.0.2.1' set service ipoe-server client-ip-pool name first-pool next-pool 'second-pool' set service ipoe-server client-ip-pool name first-pool subnet '192.0.2.0/25' set service ipoe-server client-ip-pool name second-pool gateway-address '203.0.113.1' set service ipoe-server client-ip-pool name second-pool next-pool 'third-pool' set service ipoe-server client-ip-pool name second-pool subnet '203.0.113.0/25' set service ipoe-server client-ip-pool name third-pool gateway-address '198.51.100.1' set service ipoe-server client-ip-pool name third-pool subnet '198.51.100.0/24' set service ipoe-server interface eth1
Mar 20 2023
I have certain doubts about it.
Netfilter documentation is not always perfect, and many times you may find out some different options.
Workaround: put these lines to /config/scripts/vyos-postconfig-bootup.script
Mar 19 2023
@n.fort
My judgement may have been too hasty. The commands are accepted by VyOS configure, but it looks like the meta pkttype host is being ignored by my new nftables rules. That is, all IP addresses are matching, not just actual VyOS host router IP addresses.