internet sharing on an existing network
 

Hi,

I'm trying to add a new subnet to my network and enable internet sharing for that subnet.
I read a lot of guides and now it works halfway. I can send packets to the outside world, but I cannot receive anything back because my subnet isn't known in my primary router.

I think it has something to do with nat. But I haven't been able to find the correct guide to enable it.

My network topology:
It seems that dns is working, but I think that's because I installed dnsmasq on the linux pc.

Now why ping doesn't work:

You can see that the ip address 192.168.0.5 is being used towards the primary router. When the primary router wants to respond, I think it causes an address unreachable because 192.168.0.5 is not in the subnet 10.0.0.0/24.

If I do a ping from my linux pc:
I get the following reply:
I'm not able to add routing tables on my speedtouch router.

You are adding another network rather than a subnet. The easiest way would be to subnet the 10.0.0.0 address space. If you did that, then you could use forwarding alone to share the internet. You could have one subnet at 10.0.0.0 and another ( for pc3 ) at 10.0.1.0 for example. Another option is to use NAT on linux pc 2 to translate pc3's address.

I think you are right in that, because the router is in NAT mode rather than in routing mode, and this constrains you to use 10.x.x.x for the lan. The router has no way of knowing whether to forward 192.168.0.X traffic to pc1 or pc2.

One thing to double check is whether the "nf_conntrack" module is loaded. I once subnetted my 192.168.0.X home network to use my laptop to forward traffic between my desktop and my wireless router. I used two subnets: 192.168.1.0/25 and 192.168.1.128/25. This didn't work until I modprobed the ip_conntrack module. ( Note, that this was what this module was called in the kernel I had at the time. ) I though that this module was just used for masquerading, but I guess not.

You really don't want to have anything with a "192.168.x.x" address on a network that's "10.x.x.x" unless that second ethernet-adapter points to an entirely separate network ... causing this computer to be, in effect, a bridge between the two.

Each ethernet adapter has its own routing table which specifies how packets are to move from their source to their destination. Your "eth1" adapter faces to 10.x.x.x and therefore is the target for any traffic bound there. Your "eth2" adapter faces "192.168.x.x" and is the target only for traffic bound to that subnet. Finally, your "gateway" to the outside world is at "10.0.0.138," which means that it is your only gateway; "eth2" should not have a gateway address because it cannot reach the outside. Packets destined for Antarctica won't go anywhere from here if they go out through that pipe, and you don't want to give your computer the mistaken impression that it can choose between two routes.

Other computers, on the subnet to which your "eth2" adapter is facing, would use the "192.168.0.1" address of that adapter as their gateway, since as far as they are concerned that's what it is. Your computer will then reflect those packets back out through its "eth1" on its way to the hardware-router and thence the Internet.