- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 26 2022
Aug 25 2022
PR for 1.3 https://github.com/vyos/vyos-build/pull/258
We have to replace it in migration scripts if it is already not done
The latest version of the demo can be found here:
PR https://github.com/vyos/vyos-1x/pull/1497
vyos@r14:~$ show nat source statistics Rule Packets Bytes Interface ------ --------- ------- ----------- 100 1279 107896 eth0 120 1 60 eth1 vyos@r14:~$
The easiest way it add vyatta-nat-translations.pl scripts to the op-mode script directory or rewrite it to the python.
Also discussed this configuration:
set service dhcp-relay <tag> interface eth0 upstream set service dhcp-relay <tag> interface eth1 downstream set service dhcp-relay <tag> server <x.x.x.x> set service dhcp-relay <tag> relay-options hop-count 1 set service dhcp-relay <tag> relay-options upsteam-port 547
PR https://github.com/vyos/vyos-1x/pull/1496
vyos@r14# commit [ vpn sstp ] "tcp" port "443" is used by another service
Aug 24 2022
PR for equuleus https://github.com/vyos/vyos-1x/pull/1494
PR https://github.com/vyos/vyos-1x/pull/1491
set nat66 destination rule 100 destination address '2001:1111:1111:1111::10' set nat66 destination rule 100 inbound-interface 'eth0' set nat66 destination rule 100 translation address 'fd00:1111:1111:1111::10' set nat66 source rule 100 destination prefix '!fd00:2222:2222:2222::/64' set nat66 source rule 100 outbound-interface 'eth0' set nat66 source rule 100 source prefix 'fd00:1111:1111:1111::/64' set nat66 source rule 100 translation address '2001:1111:1111:1111::10' set nat66 source rule 120 destination prefix '2001:db8:2222::/64' set nat66 source rule 120 outbound-interface 'eth0' set nat66 source rule 120 source prefix '2001:db8:1111::/64' set nat66 source rule 120 translation address 'masquerade' set nat66 source rule 130 destination prefix '2001:db8:2222::/64' set nat66 source rule 130 outbound-interface 'eth0' set nat66 source rule 130 source prefix '2001:db8:2244::/64' set nat66 source rule 130 translation address 'masquerade'
show
vyos@r14:~$ show nat66 source rules
Rule Source Destination Proto Out-Int Translation
------ ------------------------ ------------------------- ------- --------- -----------------------
100 fd00:1111:1111:1111::/64 !fd00:2222:2222:2222::/64 IP6 eth0 2001:1111:1111:1111::10
sport any dport any
120 2001:db8:1111::/64 2001:db8:2222::/64 IP6 eth0 masquerade
sport any dport any
130 2001:db8:2244::/64 2001:db8:2222::/64 IP6 eth0 masquerade
sport any dport any
vyos@r14:~$
vyos@r14:~$
vyos@r14:~$ show nat66 destination rules
Rule Source Destination Proto In-Int Translation
------ --------- ----------------------- ------- -------- -----------------------
100 ::/0 2001:1111:1111:1111::10 any eth0 fd00:1111:1111:1111::10
sport any dport any
vyos@r14:~$I am more +1 on set system ip(v6) nht because what happens if out of random another protocol will support this? Also it's a zebra option as you described, not a bgpd option.
Aug 23 2022
While reading the FRR docs I see it is only used in BGP and nowhere else. That would make something like set protocols bgp parameters next-hop-track resolve-via-default logical.