https://netmaker.org logo
#client
Title
# client
f

flat-evening-50211

05/29/2022, 2:12 PM
Hey, would like to ask a question about the client. I got a fresh install of Ubuntu 20.04.4 LTS, completely clean, only packages installed extra were OpenSSH. I installed the client, and joined a network. It looks like it did so successfully. root@gateway:~# netclient join -t [netclient] 2022-05-29 14:04:37 joining Network-1 at api.netmaker.mydomain.com:443 [netclient] 2022-05-29 14:04:37 starting wireguard [netclient] 2022-05-29 14:04:39 certificates/key saved [netclient] 2022-05-29 14:04:40 sent a node update to server for node gateway ,
After this, I ran "ip a" to verify the connections, and it seems as though the wireguard connection was not successful. root@gateway:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff inet 10.0.90.12/23 brd 10.0.91.255 scope global dynamic ens3 valid_lft 2788sec preferred_lft 2788sec inet6 fe80::2a0:98ff:fe45:477/64 scope link valid_lft forever preferred_lft forever 4: nm-Network-1: mtu 1280 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.0.110.1/32 scope global nm-Network-1 valid_lft forever preferred_lft forever
wg show shows the following: root@gateway:~# wg show interface: nm-Network-1 public key: private key: (hidden) listening port: 51821 peer: endpoint: :51823 allowed ips: 10.0.110.0/32 latest handshake: 11 seconds ago transfer: 92 B received, 180 B sent persistent keepalive: every 20 seconds
Scratch this last one, I figured I was missing -n on the leave command.
b

bored-island-21407

05/29/2022, 2:16 PM
what is the question
f

flat-evening-50211

05/29/2022, 2:20 PM
Well, I assume that the wireguard interface showing "state UNKNOWN" is a signal of Wireguard failing silently. Assuming the client set itself up appropriately: 1. Am I missing any steps I should've taken? (Wireguard keys or other config setups?) 2. Are there any additional steps I should be looking at from an installation standpoint? 3. Is there a recommendation for a small footprint gateway? Using version 0.9.x earlier in the year, when the netclient was installed via script, this problem had never surfaced, and I am still learning the ropes around Wireguard, so I am definitely fighting against my own lack of capability in further debugging this.
b

bored-island-21407

05/29/2022, 2:22 PM
The only thing I see is the allowedips for the peer is not correct. Should be 10.0.110.1/32 or 10.0.110.0/24. Maybe not if the peers wg IP address is 10.0.110.0 but that is unusual
You are getting a handshake on wg show so what is the issue
f

flat-evening-50211

05/29/2022, 2:26 PM
Uh. Give me a second, let me look back at the documentation. I believe this is a problem of the way I may have introduced the range when creating the network.
I'll review and report back, but I think I noticed the mistake.
Alright. This one is fixed. Now I need to review the egress gateway, as that is definitely not forwarding.
Thank you for your answers @bored-island-21407. It seems as though when the network was first created, the IP for the range didn't set itself well, so it used .0, and it was stopping the conn. Now I need to figure out why Egress isn't working, even after the range and the interface name have been defined (supposedly accurately).
j

jolly-london-20127

06/03/2022, 1:49 PM
WireGuard failing silently after successful client install on Ubuntu 20.04
3 Views