search

gravitl / netmaker

Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
https://netmaker.io
Other
9.5k stars 552 forks source link

netclient not receiving traffic via egress gateway #384

Closed SiM22 closed 3 years ago

SiM22 commented 3 years ago

I am not sure if i am doing this right but ill post this just incase.

I have 3 instances.

Netmaker is on a public cloud instance Netclient is running on an Ubuntu instance at home Wireguard running on iOS.

I have the Public Cloud instance as an ingress I have the Ubuntu instance running as an egress gateway for 192.168.1.1/24 I then add the QR code for the external client to my iOS device.

When i connect the iOS device with wireguard and try to hit a local IP in the 192.168.1.1/24 range, it just times out. Not sure what i need to configure. Any help would be awesome.

afeiszli commented 3 years ago

Hi @SiM22. Can you hit the egress range from the Netmaker (public cloud) host?

SiM22 commented 3 years ago

nope

ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4094ms
SiM22 commented 3 years ago

Cloud Instance

interface: nm-homev1
  public key: Netmaker
  private key: (hidden)
  listening port: 51821

peer: Ubuntu Instance
  endpoint: x.x.x.x:49955
  allowed ips: 10.20.30.2/32, 192.168.1.0/24
  latest handshake: 2 minutes, 3 seconds ago
  transfer: 335.54 KiB received, 1.53 MiB sent
  persistent keepalive: every 20 seconds

peer: iOS device
  endpoint: x.x.x.x:14437
  allowed ips: 10.20.30.3/32
  latest handshake: 2 days, 1 hour, 46 minutes, 55 seconds ago
  transfer: 59.62 KiB received, 4.93 MiB sent
  persistent keepalive: every 20 seconds
SiM22 commented 3 years ago

clicked the close button by accident

SiM22 commented 3 years ago

this is now fixed. i had the egress set to 192.168.1.1/24 and it would fail when adding the route on the netmaker instance.

etmaker       | 2021/10/27 15:53:01 error running command: /sbin/ip -4 route add 192.168.1.1/24 dev nm-homev1
netmaker       | 2021/10/27 15:53:01 ip: RTNETLINK answers: Invalid argument

Changed the egress route to 192.168.1.0/24 and working. thanks @afeiszli