- Change Summary
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 15 2023
Jan 13 2023
We should backport it to 1.3
Jan 12 2023
Jan 11 2023
@jestabro I've created the backport PR just now.
@roedie , thanks.
Will push the backport for 1.3 as well.
So there are 2 options
- Live it as it is, it works as before (but maybe it is a legacy way)
- Return the strongswan.service and use it in all required places (conf-mode, op-mode, dmvpn scripts, etc). So old ipsec/starter must not be overlapped with strongswan.service restarts
Jan 10 2023
I found that if IPSEC lifetime is large(28800) then this problem occurs.
If lifetime eq 1800 sec, everything works.
After return strongswan.starer https://github.com/vyos/vyos-1x/commit/f5f43c6639957f95177bb77d2b569e16d4dab9dc
all looks good now, service can be restored without issues
The similar task T3008
Jan 9 2023
I have tested this bug.
After boot everything woks fine without any problems.
But after restart vpn command all these issues began.
- Error message
vyos charon[2079]: 04[NET] no socket implementation registered, sending failed
- Swanctl shows unnormal info. IPSEC phase is down.
- Traffic passes through the tunnel.
- New process appears
Fixed in T3810
Jan 8 2023
I don't think this is a bug in FRR, but rather a configuration issue. I'm not really familiar with FRR, but as far as I can tell, sending RAs is an intended feature of it that can be disabled per interface: https://docs.frrouting.org/en/latest/ipv6.html#clicmd-ipv6-nd-suppress-ra
Not sure why it's enabled by default, since I couldn't find anything in the generated /etc/frr/frr.conf that would enable it.
Could you open an issue for FRR?
https://github.com/FRRouting/frr/issues
Jan 7 2023
Jan 6 2023
The error is in the respective XML op-mode-definitions; arg '--intf-type' should be passed to 'show_interfaces.py' (1.3); 'interfaces.py' (1.4) so that tag node is correctly filtered.
I have checked this config on VyOS 1.4-rolling-202212310809 (Strongswan 5.9.8). The problem is the same.
Jan 5 2023
I just edited the file /opt/vyatta/sbin/install-image in a running system to try testing this, and it works as expected at least for the primary minisign key. I didn't test GPG or 2nd minisign key, but I see no reason why there would be an issue there. I did touch those parts, though, so it's probably worth at least having another set of eyes look at it all.
er wait hold up i made a mistake saving/pushing my changes
edit: fixed
I created a PR, but I'm not certain how to compile this part of VyOS to test this, and I'm hoping someone could help me do so -- a quick glance makes it look to me like this is compiled into a .deb that's then installed by https://github.com/vyos/vyos-build/blob/current/scripts/build-vyos-image ?
In T1237#140040, @Viacheslav wrote:will be fixed in the next rolling release
The error handling on this line is basically nonexistent, but also the coding style is a little hard to follow.