I spent some time tonight getting this into a better place with https://github.com/vyos/vyos.vyos/pull/354, but I don't know how to run the tests locally, so I can't verify that my test changes are good. It looks like I need someone to approve some workflows in order for me to get that CI signal.

https://github.com/vyos/vyos-1x/pull/4034

@yzguy I'm not sure about this.
But as I know, Linux Desktop will use NetworkManager with ModemManager to bring up a wwan interface.
And network-manager will check the bearer to setup the IP address.

This time it seems like the remote side initiate a new IKE_SA without properly closing the old one. This tricked strongswan to keep both, but when the old one timed out. the vti-up-down script killed the VTI.

Just to add some context. This keeps on happening regularly, but for some reason more often on our trans-atlantic VPNs. Maybe once a week( it varies).

Duplicate of T2567
Dynamic memory allocation is not implemented for ip-pools.

PR: https://github.com/vyos/vyos-1x/pull/4028

This bug should be closed since vyos has moved to use Kea and no longer uses wide-dhcpv6

@Viacheslav AFAIK this request has nothing to do with https://vyos.dev/T3771

This made it possible to commit the change
Additionally I set a pbr rule like this:

vyos@vyos# show policy route6
 route6 pbr6 {
     interface bond0.1001
     interface bond0.1002
     interface bond0.1003
     rule 10 {
         destination {
             address 64:ff9b::/96
         }
         set {
             mark 1064
         }
     }
 }

This should only mark traffic going to the nat64 prefix.
however as far as I can see all traffic is still going through/to jool and the "match mark" is ignored.
Where would I be able to verify if it has been set in the backend configs?

@n.fort I like the interface log sub command, gives us a nice way to take on additional logging things later, but for now log link-status seems good to me.

The script exists, under the same name, iff configured:
https://github.com/vyos/vyos-1x/blob/current/python/vyos/config_mgmt.py#L52-L53
https://github.com/vyos/vyos-1x/blob/current/src/conf_mode/system_config-management.py#L52-L64

Try to delete whole nat64 config and re-configure again (not change)
Also I do not see the translation address.
The comment says that changing an instance fails https://github.com/vyos/vyos-1x/blob/c78c5bd7e65b19e0e50ef6944dc74fb33660ff71/src/conf_mode/nat64.py#L71-L74

Can you please include the VyOS config?

Just upgrade from 1.3 LTS to 1.5-rolling-202408300023 on XCP-ng 8.2 with latest patches.
The sg offload setting seems fixed the drop packet issue.

set interfaces ethernet eth0 offload sg
set interfaces ethernet eth1 offload sg
...

@pratik.g can you please retest with 1.4.0 or a more recent 1.5-rolling release?

https://vyos.io currently works from Sweden when I tested it at about 2024-08-31 11:30 local time.

Hello everyone,