PR for equuleus https://github.com/vyos/vyos-1x/pull/1494
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 24 2022
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.
I prefer to get this option configurable if it is possible
For IPv6 and VRFs - nice to have.
As it is used in BGP, I see something like set protocols bgp parameters next-hop-track resolve-via-default
Or, as it was mentioned in T3500
set routing-options next-hop-track resolve-via-default but it will be an additional node with only one option, needs to think
@Viacheslav Do you just want this option added to the zebra config, or you it also be possible to enable/disable this via the conf mode?
PR https://github.com/vyos/vyos-1x/pull/1489
vyos@r14:~$ show conntrack statistics CPU Found Invalid Insert Insert fail Drop Early drop Errors Search restart ----- ------- --------- -------- --------------- ------ ------------ -------- ----------------- cpu=0 found=0 invalid=0 insert=0 insert_failed=0 drop=0 early_drop=0 error=0 search_restart=0 cpu=1 found=0 invalid=0 insert=0 insert_failed=0 drop=0 early_drop=0 error=0 search_restart=0 cpu=2 found=0 invalid=0 insert=0 insert_failed=0 drop=0 early_drop=0 error=0 search_restart=0 cpu=3 found=0 invalid=0 insert=0 insert_failed=0 drop=0 early_drop=0 error=0 search_restart=48 vyos@r14:~$
Check NGINX address/port before applying/committing service https
PR https://github.com/vyos/vyos-1x/pull/1488
@daniil, could you check/test this PR https://github.com/vyos/vyos-1x/pull/1487 (only for IPv4)
Aug 22 2022
I have confirmed that this issue is now resolved when building from equuleus. I've attached a screenshot showing the table for the dynamic interface has a default route after the interface get's an IP. I used the following commands to build the ISO.
I've create a PR which does the retry part. It retries 10 time every 0.5 seconds until it succeeds or it's out of retries.
Tested via:
This is what I did (forgot to write it here) with the difference that my sleep timer is 60s as my config has many lines.
Would be good to have this fixed properly.
I think I found the "problematic" commit.
https://github.com/vyos/vyos-1x/commit/41477cc85208507be55f8db4e412ad78eae764eb#diff-8e6f3b9122c8406707eb59334978290d083995acf7de0323111d4eed1656693dL311
The problem here seems to be that keepalived is started before the complete commit is finished. So conf.get_config_dict() fails to get the config.
With an older version:
vagrant@s1:~$ sudo bridge vlan
port vlan-id
eth1 1000 PVID Egress Untagged
eth2 1001 PVID Egress Untagged
br0 1 PVID Egress Untagged
1000
1001
vagrant@s1:~$ show versionI guess it the task T4632
Can confirm.
Created PR for this https://github.com/vyos/vyos-build/pull/256
Hi, I've created https://github.com/vyos/vyos-1x/pull/1483 for this one.