So I have the netmaker server up and running with a public ip (node is also ingress), created my network and deployed a netclient (docker) over a VM I have on a different network at some other location. I set the docker netclient node as egress, but I cannot reach the IPs (ping) on the egress node network (i.e. 10.10.10.5), any clue as to why? or maybe I missed some other config.. (I am trying to ping an IP behind the egress node from an external client: cellphone with wireguard installed)

what is the ip range of your netmaker network?

isn't the one on the screenshot above correct? 10.10.10.0/24 so that means the whole range right? or do I have to specify it with 10.10.10.1-10.10.10.254 ?

that is the correct way to spec the range

no, that range is my private network (at home) network range. My netmaker network range is different: 10.21.45.0/24 So Ingress and Egress network range is: 10.21.45.0/24 My private home network range (where my egress node is): 10.10.10.0/24 From my cellphone external client I am trying to reach my internal network home like: ping 10.10.10.5 -> does not work. HOWEVER I am able to ping ONLY the egress node IP (which is 10.10.10.3 -> this IP i can ping, anyother I cannot)

phone= android or apple?

android

what do you mean by Ingress Range --- there is no ingress range

meaning where the ingress and egress nodes are. The netmaker network:

ok.

I created an access token, I used the docker commands shown there to create my node at home. After it showed up on the netmaker nodes dashboard I set it as egress. Then I proceed to create the external client and scanned it with QR. I do re-create/re-scan the ext client on every change I made to my netmaker network because I know the config changes (like allowed IP ranges or DCHP Server, etc.)

have you tried running the netclient binary as opposed to the netclient-docker for your egress node (eliminates docker networking funnies)

that's a great idea, I will try that

the only reason for netclient-docker is really for k8

gotcha yeah I figure kubernetes was the reason but then again just to mention it, Is just cleaner for me in my opinion to lunch a docker container. BUt you are aboslutely correct

if you install netclient using your package manager, upgrading is just as easy as docker updates

understood

I think some others have tried that....

I know I am not supposed to mess with my firewall but just asking if possible

does pfSEnse have systemd

ok no worries, thanks a bunch for your help. I will just install the native client instead of the docker one and let you know here if that's it

👍