and other problem the node B ping the host beihind the node A but the host behind node A don't ping the host behind the node B

very very strange I test ith debian

ubuntu

port_forwarding enable ....

but nothing to work, and the same configuration (egress, network) work perfectly on 0.14

😦

I mean I have had it working but with a different node configured as egress and that were using 0.20.0

However then I did a complete reinstall and spun up a brand new node to work as egress, which did not work

Personally I never managed to make it work in 0.20, however the nodes could well have access to the equipment behind the node egress

yes very strange

Very strange indeed

Yes for this reason I test now netbird

to view if is the same problem or not 😦

on the same network

Do fare I have figured out so fare is that I can see that packets received on my NetMaker network are being masqueraded before being set out

i tested netmaker

this is simply to verify

use packet capture

tshark or tcpdump

on interface LAN

Haven't tried using those before actually

and you view this ip source is used on forwarding

Woaw yeah I can see that when I ping another device with the ip:

192.168.12.20

which is on my private subnet that there is actually message sent from the interface

So my egress node actually forwards the packets

so it is receiving packets, but they are not returning?

Okay new update, I have tracked the messages through the following: External client pings

192.168.12.20

-> Linode Node(

10.120.0.2

) farwards packets to -> Proxmox node(

10.120.0.1

- Netmaker Interface) and masqueraded and and sents packet to -> Host on private subnet

192.168.12.20

which sends response to -> Proxmox node(

192.168.12.55

- ens18 Interface) <----------- This is as fare as the packet goes When doing a tcpdump looking for packets with the target host from the private subnet nothing comes up. So it seems like the egress not never sents back the responds packets. Used the following command to test that:

tcpdump -i netmaker 'dst net 10.120.0.0/24'

Yeah the egress node sends the packets just fine, and the correct destination and source ip is set. However nothing is returned to the netmaker network

If anyone is interested: the solution to this was a fresh install and disabling proxy on the CGNAT node.

hey can someone help me I'm trying to set netmaker up so that I can connect back to my local home network when outside, currently I have a linode VPS with netmaker installed on it and I have created a network and added the netmaker VPS as a local node and is a default node. I have also configured it as an ingress node for my devices to connect to the network. I have another node inside the local home network that has been added as a node to the netmaker network as an egress node and i've put the local subnet in for external routes. I can ping the local IP of the connected node but no other devices on the local network