Hi all,
I've got the following setup working nicely, with my linux laptop working as a brilliant wireless bridge while keeping my subnetwork with its own dhcp and dns separate from the rest of the network:
Code:
+----------------+
| Internet |
| |
+----------------+
|
+--+--------+--------------------+
| | router |---[other devices] |
| +--------+ |
| | 192.168.1.0/24 |
| | |
| |[wifi] +-------------+--------------------+
| +------------| laptop | 192.168.0.1/24 |
+------------------+-------------+ |
| | +-----------------+ |
| +----| ethernet switch | |
| +-----------------+ |
| | | |
| +-------------+ +--------+ |
| | Debian | | Gaming | |
| | Server | | PC | |
| +-------------+ +--------+ |
+----------------------------------+
The laptop is routing using iptables. Each side, given a routing table entry to the other subnet via the laptop, can see the other subnet no worries. Now, thanks to my control over dhcp on the .0.0 side via my server, I can pass the laptop's IP as the default gateway to everything in my (the 192.168.0.0) subnet and all these routes are configured automatically. Shabang, internet ahoy! The problem comes from when someone on the 192.168.1.0 subnet (i.e. any wifi clients) wants to access the ...0.0 side. If a route to 192.168.0.0 via the laptop is added, it works fine - however this is a pain in the arse. I have friends with macbooks where it's tedious at best, and at worst my symbian wifi phone doesn't even ALLOW me to configure the routing table, leaving it isolated from all my servery goodness.
Scoping around the internets, I came across
http://en.wikipedia.org/wiki/ICMP_Ro...overy_Protocol which seems to do what I've wanted - however I can't get it to work. I'm using icmpush on the laptop to create packets for prototyping my configuration, but nothing seems to actually change how e.g. my symbian phone can absolutely not see 192.168.0.0.
One thing I am looking at with interest is how routers (e.g. my laptop) are meant to add themselves to the 240.0.0.2 multicast group - do I need to configure this before things will start to route through it automatically?
Other than that I'm out of ideas, so alternate plans for automatic routes from 192.168.1.0 to 192.168.0.0 are welcome.
I should also mention that I have no access to the wifi router so I can't add static routes there.
The above setup is at the limits of my ability at the moment - obviously expanding these limits is OK but just keep in mind I'm no network engineer.
Thanks kindly,
Jarrad