0

I'm having no success setting up routes and I suspect I have a misconception about what's needed.

On a multihomed machine (Master) with 2 networks (N1 wired, N2 wireless HotSpot), Master can ping every IP on both networks. Great!

Another machine on N1, for example, can ping both of Master's IPs, but can't ping any of the other machines on N2. A machine on N2, can ping both of Master's IPs, but can't ping any of the other machines on N1. I want to correct this by setting up routes.

Am I correct that to allow N1 machines to ping N2 machines, what's needed is a route on Master's N1 network stating that any N2 destination is handled by Master's N2 IP (next hop) and a similar route has to be set up on Master's N2 network stating that any N1 destination is handled by Master's N1 IP (next hop)?

I've tried doing this but it hasn't worked and I think it has to do with the difference between a regular network and the HotSpot. Can anyone shed some light on this?

Blindspots
  • 3,472
Bill Gradwohl
  • 101

1 Answers1

0

The hosts (and other routers besides Master) on N1 need a route pointing traffic for the N2 subnet at Master's N1 address as the gateway. The hosts (and other routers besides Master) on N2 need a route pointing the N1 subnet at Master's N2 address.

Master needs to be told to do IP forwarding. On most Unix-like OSes this is usually done via setting a kernel variable via sysctl. But the exact path to the variable is different in different OSes, so check your OS documentation for things like "net.ipv4.ip_forward" or "net.inet.ip.forward".

Spiff
  • 110,156