That is a funny thing.
So I for ease, I move on a linux computer (debian).
I tried again, to connect nym vpn on openwrt.
- I am connected via ssh on the openwrt.
- I try to ping from the laptop the router, with only nym on the router (ping 192.168.1.1)
user@workstation ~ [1]> ping -c 2 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
ā 192.168.1.1 ping statistics ā
2 packets transmitted, 0 received, 100% packet loss, time 1023ms
I can t ping the router from the computer
But I stay connected on SSH, and I can access the WEBGUI.
Here is the log :
āāā
INFO nym_vpnd: nym-vpnd 1.21.0-beta (VERGEN_IDEMPOTENT_OUTPUT)
INFO nym_vpnd: OS information: Linux (OpenWrt 24.10.1) (x86_64), kernel: 6.6.86
INFO nym_vpnd::environment: Setting up environment by discovering the network: mainnet
INFO nym_vpnd::command_interface: Starting socket listener on: /var/run/nym-vpn.sock
INFO nym_vpn_account_controller::controller: Initializing account controller: data_dir: /var/lib/nym-vpnd/mainnet
INFO nym_vpn_account_controller::controller: Initial account controller state: Syncing
INFO nym_vpn_account_controller::controller: Account id: n1rdwm5mygue87x2pnja60t4fh3g340pse3u2szc
INFO nym_vpn_account_controller::controller: Device id: n1aitL21mbPT5gtnopEfE9vx58jqSYAr8i3GLXyXCaC
INFO nym_http_api_client::dns: building new configured resolver
INFO nym_vpnd::service::config::config_manager: Read service config version v4 from /etc/nym/mainnet/nym-vpnd.json
INFO nym_vpnd::service::config::config_manager: Using config: VpnServiceConfig { entry_point: Country { two_letter_iso_country_code: āFRā }, exit_point: Country { two_letter_iso_country_code: āFRā }, allow_lan: true, disable_ipv6: true, enable_two_hop: true, enable_bridges: false, netstack: false, disable_poisson_rate: false, disable_background_cover_traffic: false, min_mixnode_performance: None, min_gateway_mixnet_performance: None, min_gateway_vpn_performance: None, residential_exit: false, enable_custom_dns: false, custom_dns: , network_stats: NetworkStatisticsConfig { enabled: true, allow_disconnected: false } }
INFO nym_firewall: Resetting firewall policy
INFO nym_vpn_account_controller::controller: New AccountController state: Requesting zk-nyms
INFO nym_vpn_account_controller::controller: New AccountController state: Ready to connect
INFO nym_vpnd::service::config::config_manager: Using config: VpnServiceConfig { entry_point: Country { two_letter_iso_country_code: āFRā }, exit_point: Country { two_letter_iso_country_code: āFRā }, allow_lan: true, disable_ipv6: true, enable_two_hop: true, enable_bridges: false, netstack: false, disable_poisson_rate: false, disable_background_cover_traffic: false, min_mixnode_performance: None, min_gateway_mixnet_performance: None, min_gateway_vpn_performance: None, residential_exit: false, enable_custom_dns: false, custom_dns: , network_stats: NetworkStatisticsConfig { enabled: true, allow_disconnected: false } }
INFO nym_vpnd::service::config::config_manager: Using config: VpnServiceConfig { entry_point: Country { two_letter_iso_country_code: āFRā }, exit_point: Country { two_letter_iso_country_code: āFRā }, allow_lan: true, disable_ipv6: true, enable_two_hop: true, enable_bridges: false, netstack: false, disable_poisson_rate: false, disable_background_cover_traffic: false, min_mixnode_performance: None, min_gateway_mixnet_performance: None, min_gateway_vpn_performance: None, residential_exit: false, enable_custom_dns: false, custom_dns: , network_stats: NetworkStatisticsConfig { enabled: true, allow_disconnected: false } }
INFO nym_firewall: Applying firewall policy: Connecting to peers: none, Allowing LAN, interface: none. Allowing endpoints: none. Allowing non-tunnel DNS: 9.9.9.9,149.112.112.112,1.1.1.1,1.0.0.1
INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connecting wg, resolving api addresses, try #0
INFO nym_vpn_lib::tunnel_state_machine::states::connecting_state: Resolved gateway config: ResolvedConfig { nyxd_socket_addrs: [91.92.200.116:443, [2a04:c46:e00:6f28:4b3:68ff:fe00:460]:443], nym_api_resolver_overrides: ResolverOverrides { overrides: {āvalidator.nymtech.netā: {212.71.233.232:443}} }, nym_vpn_api_resolver_overrides: ResolverOverrides { overrides: {āyelp.global.ssl.fastly.netā: {151.101.1.194:443}, ānymvpn-frontdoor.global.ssl.fastly.netā: {151.101.1.194:443}, āvercel.appā: {64.29.17.131:443}, ānymvpn.comā: {76.76.21.21:443}, āvercel.comā: {198.169.2.193:443}} } }
INFO nym_firewall: Applying firewall policy: Connecting to peers: none, Allowing LAN, interface: none. Allowing endpoints: 91.92.200.116:443/TCP,212.71.233.232:443/TCP,151.101.1.194:443/TCP,151.101.1.194:443/TCP,64.29.17.131:443/TCP,76.76.21.21:443/TCP,198.169.2.193:443/TCP. Allowing non-tunnel DNS: 9.9.9.9,149.112.112.112,1.1.1.1,1.0.0.1
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for yelp.global.ssl.fastly.net: 151.101.1.194:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for yelp.global.ssl.fastly.net: 151.101.1.194:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for nymvpn-frontdoor.global.ssl.fastly.net: 151.101.1.194:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for nymvpn-frontdoor.global.ssl.fastly.net: 151.101.1.194:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for vercel.app: 64.29.17.131:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for vercel.app: 64.29.17.131:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for nymvpn.com: 76.76.21.21:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for nymvpn.com: 76.76.21.21:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for vercel.com: 198.169.2.193:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for vercel.com: 198.169.2.193:443
INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connecting wg, awaiting account readiness, try #0
INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connecting wg, refreshing gateways, try #0
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for validator.nymtech.net: 212.71.233.232:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for yelp.global.ssl.fastly.net: 151.101.1.194:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for nymvpn-frontdoor.global.ssl.fastly.net: 151.101.1.194:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for vercel.app: 64.29.17.131:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for nymvpn.com: 76.76.21.21:443
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for vercel.com: 198.169.2.193:443
INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connecting wg, selecting gateways, try #0
INFO nym_vpn_lib::tunnel_state_machine::tunnel::gateway_selector: Found 394 entry gateways
INFO nym_vpn_lib::tunnel_state_machine::tunnel::gateway_selector: Found 394 exit gateways
INFO nym_vpn_lib::tunnel_state_machine::tunnel::gateway_selector: Using entry gateway: 7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw, location: FR, performance: 99%
INFO nym_vpn_lib::tunnel_state_machine::tunnel::gateway_selector: Using exit gateway: BayDqFCz1h7aShk54ewbKg4w8cT9ddqW9PDTMrvcRGgK, location: FR, performance: 99%
INFO nym_vpn_lib::tunnel_state_machine::tunnel::gateway_selector: Using exit router address 34MrW5kNPq7B8HMB3k9cwSSs41BDugjW8UVtTZsc9kWe.8bWutpgha1w4tREibXyyyvDHtqiDLir9gPPqw2Xypp3j@BayDqFCz1h7aShk54ewbKg4w8cT9ddqW9PDTMrvcRGgK
INFO nym_firewall: Applying firewall policy: Connecting to peers: 92.112.192.97:9000/TCP,92.112.192.97:9001/TCP, Allowing LAN, interface: none. Allowing endpoints: 91.92.200.116:443/TCP,212.71.233.232:443/TCP,151.101.1.194:443/TCP,151.101.1.194:443/TCP,64.29.17.131:443/TCP,76.76.21.21:443/TCP,198.169.2.193:443/TCP. Allowing non-tunnel DNS: 9.9.9.9,149.112.112.112,1.1.1.1,1.0.0.1
INFO nym_vpn_api_client::fronted_http_client: Enabling Resolver override for validator.nymtech.net: 212.71.233.232:443
INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connecting wg, registering with gateways, try #0
INFO nym_registration_client::builder::config: mixnet client poisson rate limiting: disabled
INFO nym_registration_client::builder::config: mixnet client background loop cover traffic stream: disabled
INFO nym_registration_client::builder::config: mixnet client minimum mixnode performance: 50
INFO nym_registration_client::builder::config: mixnet client minimum gateway performance: 50
INFO nym_client_core::client::base_client::non_wasm_helpers: Loading existing surb database
INFO nym_client_core_surb_storage::backend::fs_backend::manager: Database migration finished!
INFO nym_registration_client::builder::config: mixnet client poisson rate limiting: disabled
INFO nym_registration_client::builder::config: mixnet client background loop cover traffic stream: disabled
INFO nym_registration_client::builder::config: mixnet client minimum mixnode performance: 50
INFO nym_registration_client::builder::config: mixnet client minimum gateway performance: 50
WARN perform_initial_authentication: nym_gateway_client::client: this gateway is on an old version that doesnāt support upgrade mode gateway=7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw gateway_address=ws://92.112.192.97:9000/
INFO perform_initial_authentication: nym_gateway_requests::registration:
:client: the gateway insists on protocol version different from the one we suggested. it wants 3 whilst we wanted 5, however, we can support it gateway=7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw gateway_address=ws://92.112.192.97:9000/
INFO perform_initial_authentication: nym_gateway_client::client: close time.busy=1.88ms time.idle=75.4ms gateway=7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw gateway_address=ws://92.112.192.97:9000/
INFO nym_client_core::client::base_client: Starting nym client
INFO nym_client_core::client::base_client: Building nym-api client from provided URLs (with domain fronting support): 1 URLs
WARN nym_http_api_client::fronted: fronting is enabled, but none of the supplied urls have configured fronting domains
INFO nym_client_core::client::base_client: Starting statistics controlā¦
INFO nym_client_core::client::base_client: Obtaining initial network topology
INFO nym_client_core::client::base_client: Starting topology refresherā¦
WARN perform_initial_authentication: nym_gateway_client::client: this gateway is on an old version that doesnāt support upgrade mode gateway=7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw gateway_address=ws://92.112.192.97:9000/
INFO perform_initial_authentication: nym_gateway_client::bandwidth: remaining bandwidth: 0.00 B. in āupgrade modeā: false gateway=7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw gateway_address=ws://92.112.192.97:9000/
INFO perform_initial_authentication: nym_gateway_client::client: close time.busy=1.24ms time.idle=15.7ms gateway=7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw gateway_address=ws://92.112.192.97:9000/
INFO nym_gateway_client::client: Claiming more bandwidth with existing credentials. Stop the process now if you donāt want that to happen.
WARN nym_gateway_client::client: Not enough bandwidth. Trying to get more bandwidth, this might take a while
INFO nym_gateway_client::client: managed to claim ecash bandwidth
INFO nym_client_core::client::base_client: Starting received messages buffer controllerā¦
INFO nym_client_core::client::base_client: Starting mix traffic controllerā¦
INFO nym_client_core::client::base_client: Starting real traffic streamā¦
INFO nym_client_core::client::real_messages_control::message_handler: using BiwuzeAbaL4U8fTcfbhAmH for all anonymous messages sent to H2mt9MrHdhUshE8KGj1wPq3c7E2fbyzw1euA9JPedXSs.AVtxZb7RwWPWgBr6kaSFvQQkr2r3CZ5MaZPbbGYanGzU@7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw
INFO nym_client_core::client::real_messages_control::message_handler: using DAks9aMfNYrScZj5AKjTVH for all anonymous messages sent to 8orKcyGzHaBqRqSJZMeRn1m5V87iPusFhTKmAJWDYxkD.4teSREZmEBt4c2GNXs9odiwmMmZMno35nK5ZLrUKcwAf@BayDqFCz1h7aShk54ewbKg4w8cT9ddqW9PDTMrvcRGgK
INFO nym_firewall: Applying firewall policy: Connecting to peers: 92.112.192.97:9000/TCP,92.112.192.97:9001/TCP,92.112.192.97:51822/UDP, Allowing LAN, interface: none. Allowing endpoints: 91.92.200.116:443/TCP,212.71.233.232:443/TCP,151.101.1.194:443/TCP,151.101.1.194:443/TCP,64.29.17.131:443/TCP,76.76.21.21:443/TCP,198.169.2.193:443/TCP. Allowing non-tunnel DNS: 9.9.9.9,149.112.112.112,1.1.1.1,1.0.0.1
INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connecting wg to 92.112.192.97:51822 [7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw] ā 185.235.240.66:51822 [BayDqFCz1h7aShk54ewbKg4w8cT9ddqW9PDTMrvcRGgK], connecting tunnel, try #0
INFO nym_vpn_lib::tunnel_state_machine::tunnel_monitor: Using kernel WireGuard for entry: nym-entry
INFO nym_vpn_lib::tunnel_state_machine::tunnel_monitor: Using kernel WireGuard for exit: nym-exit
INFO nym_vpn_lib::tunnel_state_machine::tunnel::wireguard::wg_backend: Starting kernel WireGuard tunnel: nym-entry
INFO nym_vpn_lib::tunnel_state_machine::tunnel::wireguard::wg_backend: Starting kernel WireGuard tunnel: nym-exit
INFO nym_firewall: Applying firewall policy: Connecting to peers: 92.112.192.97:9000/TCP,92.112.192.97:9001/TCP,92.112.192.97:51822/UDP over entry interface: nym-entry, ips: 10.1.135.224, v4 gw: None, v6 gw: None, exit interface: nym-exit, ips: 10.1.71.129, v4 gw: Some(10.1.135.224), v6 gw: None, allowed entry in-tunnel traffic: All, allowed exit in-tunnel traffic: All), Allowing LAN. Allowing endpoints: 91.92.200.116:443/TCP,212.71.233.232:443/TCP,151.101.1.194:443/TCP,151.101.1.194:443/TCP,64.29.17.131:443/TCP,76.76.21.21:443/TCP,198.169.2.193:443/TCP. Allowing non-tunnel DNS: 9.9.9.9,149.112.112.112,1.1.1.1,1.0.0.1
INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connecting wg to 92.112.192.97:51822 [7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw] ā 185.235.240.66:51822 [BayDqFCz1h7aShk54ewbKg4w8cT9ddqW9PDTMrvcRGgK], connecting tunnel, try #0
ERROR nym_connection_monitor::connection_monitor: Error: failed to send icmp packet
: Request timeout for icmp_seq 0
INFO nym_vpn_lib::tunnel_state_machine::tunnel_monitor: Tunnel connection is failing (retry: 1)
INFO nym_vpn_lib::tunnel_state_machine::tunnel_monitor: Tunnel connection is viable
INFO nym_firewall: Applying firewall policy: Connected to peers: 92.112.192.97:9000/TCP,92.112.192.97:9001/TCP,92.112.192.97:51822/UDP over entry interface: nym-entry, ips: 10.1.135.224, v4 gw: None, v6 gw: None, exit interface: nym-exit, ips: 10.1.71.129, v4 gw: Some(10.1.135.224), v6 gw: None, Allowing LAN. Allowing non-tunnel DNS: none
INFO nym_dns: Setting DNS servers: Tunnel DNS: {9.9.9.9, 149.112.112.112, 1.1.1.1, 1.0.0.1} Non-tunnel DNS: {}
INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connected wg to 92.112.192.97:51822 [7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw] ā 185.235.240.66:51822 [BayDqFCz1h7aShk54ewbKg4w8cT9ddqW9PDTMrvcRGgK]
WARN nym_vpn_lib::bandwidth_controller: gateway 7Z6BJang9EW3KraJh6M8tNZXeSRR2D4y8UT2jfVjj3dw is outdated and does not support upgrade mode queries
WARN nym_vpn_lib::bandwidth_controller: gateway BayDqFCz1h7aShk54ewbKg4w8cT9ddqW9PDTMrvcRGgK is outdated and does not support upgrade mode queries
ERROR nym_connection_monitor::connection_monitor: Error: failed to send icmp packet
: Request timeout for icmp_seq 3
INFO nym_vpn_lib::tunnel_state_machine::tunnel_monitor: Tunnel connection is failing (retry: 1)
INFO nym_vpn_lib::tunnel_state_machine::tunnel_monitor: Tunnel connection is viable
INFO nym_vpn_account_controller::controller: New AccountController state: Syncing
INFO nym_vpn_account_controller::controller: New AccountController state: Requesting zk-nyms
INFO nym_vpn_account_controller::controller: New AccountController state: Ready to connect
āāā
