https://netmaker.org logo
Join Discord
Powered by
I've been toying around with using Netmaker for th...
# client
w
I've been toying around with using Netmaker for the following use-case: Leveraging a VPS server to host NGINX Proxy Manager to expose some of my self-hosted services. In my testing I can get this working but after some time passes, it seems my network falls apart. Systems joined to the network within my home network can ping each other on the Netmaker network but they can no longer ping to remote systems on my VPS. The same can be said for Remote systems (they can ping each other but nothing in my home network). I really don't understand how this happens, and the first time I ran into this I chalked it up to issues with my VPS and redeployed the Netmaker server. That seemed to have solved my issues at that time. All that said, when the issues cropped up again today I decided to dig a bit more and after some reading of the docs, I created a Relay server in my Netmaker network that would relay traffic between a remote host and a host local to my home network. Once I did that, ping started working again between those two servers. I'm kind of at a loss for how it was working before I created a relay host and was hoping someone here could point me in the right direction to unravel this. Or if anyone is using Netmaker in a similar fashion to bridge a Remote VPS to a home network and has any tips or examples.
(Failed to make this a thread. Sorry. New to Discord)
n
it depends on both your home gateway settings as well as your home router (if they are not the same thing)
if you have any specific questions feel free to follow up
w
I suppose I'm still in the confused stage here. I have an idea of what I'm trying to do but I'm not a very skilled network admin so forming the correct questions is difficult. Right now I have my Netmaker network as a full hub and spoke...but that feels like the easy way out 😄
I've created a new network, this time I'm starting small to see if I can get it working. It is only 3 nodes Netmaker server hosted on a VPS set up as the ingress Nginx Proxy Manager hosted on a VPS A jump system internal to my home network (with port forwarding set up) set up as the egress to my home network range It all seems to be up and working. 
wg show
shows recent handshakes and I can ping both netmaker IPs and my internal home network ranges on all involved systems. However...ping seems to be the only thing working at this point. If I try to hit an internal server on one of its listening ports from my Nginx Proxy Manager server it fails with 
no route to host
even though ping works.
This issue smells of firewall to me...but I'm at a loss for where in the path it is being stomped on.
I've dropped the firewall on one of my internal systems to test this. So the test is happening on my Nginx Proxy Manager server and attempting to reach a system within my home network through the egress system. Still showing a 
No route to host
error when doing anything that isn't a 
ping
.
tcpdump
on my egress node shows that the traffic is hitting the internal node over the wireguard network, but there is no return traffic. So it seems I'm having trouble with the return path.
Oh wait a sec...this is interesting. The traffic hits my egress system but never actually hits my home network system...hmmmm
Hot damn...either I understand this and I fixed it or I just got lucky and something broke free while I was tinkering. I added 
masquerade
to the egress host's firewall for the internal interface and the traffic started flowing 2 ways!!
n
it's just silly but valid
okay, you've found the memes as well
PreviousNext
Powered by