client does not reconnect #15

fkooman commented 2024年02月01日 09:43:07 +01:00

there are (at least) the following scenarios where it would be helpful if the proxyguard-client would auto-reconnect:

1. device suspends until the established TCP connection times out;
2. the proxyguard-server is restarted on the server, e.g. for an upgrade, or server reboot.

there are (at least) the following scenarios where it would be helpful if the `proxyguard-client` would auto-reconnect: 1. device suspends until the established TCP connection times out; 2. the `proxyguard-server` is restarted on the server, e.g. for an upgrade, or server reboot.

fkooman commented 2024年02月02日 11:14:27 +01:00

There is another slightly related issue, when importing NetworkManager config initially when proxyguard-client is already running, it will get stuck. One needs a specific order of command invocations in order to make WireGuard+TCP work:

#!/bin/sh
nmcli con del vpn
nmcli con import type wireguard file vpn.conf
nmcli con down vpn
nmcli con modify vpn wireguard.fwmark "$(printf %x 54321)"
nmcli con modify vpn wireguard.ip4-auto-default-route 0
nmcli con modify vpn wireguard.ip6-auto-default-route 0
nmcli con modify vpn ipv4.route-table 54321
nmcli con modify vpn ipv6.route-table 54321
nmcli con modify vpn ipv4.routing-rules "priority 1 not fwmark 54321 table 54321"
nmcli con modify vpn ipv6.routing-rules "priority 1 not fwmark 54321 table 54321"
sudo systemctl restart proxyguard-client
nmcli con up vpn

The issue here being: it should not be necessary to restart proxyguard-client...

There is another slightly related issue, when importing NetworkManager config initially when `proxyguard-client` is already running, it will get stuck. One needs a specific order of command invocations in order to make WireGuard+TCP work: ``` #!/bin/sh nmcli con del vpn nmcli con import type wireguard file vpn.conf nmcli con down vpn nmcli con modify vpn wireguard.fwmark "$(printf %x 54321)" nmcli con modify vpn wireguard.ip4-auto-default-route 0 nmcli con modify vpn wireguard.ip6-auto-default-route 0 nmcli con modify vpn ipv4.route-table 54321 nmcli con modify vpn ipv6.route-table 54321 nmcli con modify vpn ipv4.routing-rules "priority 1 not fwmark 54321 table 54321" nmcli con modify vpn ipv6.routing-rules "priority 1 not fwmark 54321 table 54321" sudo systemctl restart proxyguard-client nmcli con up vpn ``` The issue here being: it should not be necessary to restart `proxyguard-client`...

jwijenbergh commented 2024年02月13日 16:06:54 +01:00

Fixed in 0.2.0

Fixed in 0.2.0