Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Is IP Forwarding enabled on the gateway ? You can check it with : sysctl net.ipv4.ip_forward. If it show 0 then you have to enable it with sysctl -w net.ipv4.ip_forward=1 or echo 1 > /proc/sys/net/ipv4/ip_forward. To make these changes permanent : write net.ipv4.ip_forward = 1 in /etc/sysctl.conf, then sysctl -p /etc/sysctl.conf. You may need to restart the network. Commented Aug 1, 2019 at 9:37
  • Yes sorry I forgot to mention that, let me update the question Commented Aug 1, 2019 at 9:38
  • did you consider the fact that everything from 192.168.128.1 to 192.168.255.254 is considered to be on the local net and not subject to Routing due to the /17 netmask? which addresses did you use to test for outside Connection? Commented Aug 1, 2019 at 9:45
  • I did test many public IPs like the one given by: nslookup google.es (216.58.201.163). What sounds interesting is the fact you mention about the internal network, I don't really know which rules should I use to achieve the goal of having this machine A as a router for the other machines but I guess that is possible no ? Commented Aug 1, 2019 at 9:48
  • Sure. Any IP outside the range i mentioned will do. Try to use 'tcpdump -v -s0 -X -e eth0' on the router machine, and check source- and destination addresses of the outgoing packets. Also check if the Gateway set as Default (propably 172.105..) on the router can be reached from there. Commented Aug 1, 2019 at 11:19