Networking hassles

[Curufir]

I figure you folks must know at least something about this, or can point me in the right direction. I'm a complete networking newbie so I really don't have a clue.

Scenario is this:

There is one computer running XP that is hooked up to the net via adsl and sharing it's connection doing the Windows ICS thing.

This computer and 2 others, one XP and one 2k pro, are linked via wireless NICs.

They occupy the ip range 192.168.0.1->3

They all work fine, no problems accessing the net from any of them.

Now comes my problem.

The 2k pro computer also has another NIC (8159 based) which connects it to a computer running linux.

These two occupy the ip range 192.168.1.1->2

I can get all the computers on the wireless network to ping each other, and I can get 2 on the wired network to ping each other, but I can't get the linux computer (Which is the only one that's just on the wired network) to ping anything beyond the one it is attached to.

I know the problem is down to the 2k pro computer that has two NICs in it, but I've got no idea how to solve it (Kinda out of my depth ). Google hasn't been a heck of a lot of help, so if anyone has some ideas I'd love to hear 'em.

[chrisa128]

Basically you've got 2 networks within your one network. You basically need to set up routing on your 2k machine so the two seperate networks can see each other.

Before i explain how, why are you using two different ranges for your IP's?

[Curufir]

Before i explain how, why are you using two different ranges for your IP's?

It's the only way I could get the Linux and Win2k comps (The ones directly connected) to see each other.

[BI lazy]

hmmm ... setting up routing on a linux box is waaaay easier than on a windows box. Just enter some lines with the route command.

Basically, you need to tell the w2k box where to put the packets, when they arrive at one of the two nics.

Say: eth0 = 192.168.0.1 --> w2k box/wireless net
eth1 = 192.168.1.1 --> w2k box-linux box

so we tell the router (the w2k box):
route add 192.168.1.0 192.168.1.1
(at least that's the command on a cisco box IIRC)

this basically says: network 192.168.1.0 is reachable via the nic bound to the adress 192.168.1.1 (assuming you use c-range ip adresses *gg*)

if the default route is 192.168.0.0 192.168.0.1, you don't need to do anything for the wireless net side.

I don't know where the routing tools are on a windows box (don't you need the server for this kind of stuff?)

BUT - you can do it an other way too, just need to change your network topology a bit:

provide the network with a switch. Hook the wireless accesspoint to it. Hook the wired computers to it. Have them use the same network (192.168.0.0) et voila...

[BI lazy]

how's the going with the networking? does it work?

[Curufir]

Things have improves...slightly.

I can now ping the comp with two NICs using either 192.168.0.2 or 192.168.1.1 from the Linux comp. However I can't ping any other comp on the wireless network.

Router table on the win2k comp:
[pre]
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 1
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 1
192.168.1.0 255.255.255.0 192.168.1.1 192.168.1.1 1
192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1 1
224.0.0.0 224.0.0.0 192.168.0.2 192.168.0.2 1
224.0.0.0 224.0.0.0 192.168.1.1 192.168.1.1 1
255.255.255.255 255.255.255.255 192.168.1.1 192.168.1.1 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None
[/pre]

I know what you mean about Linux. Once I get the atheros chipset drivers working I think what I'll do is transfer the wireless NIC into the Linux computer and just make a bridge, letting everything run on the 192.168.0.x range of addresses.

[Therx]

If you have XP Pro of the "link" computer I think that you can setup routing as simply as a few clicks. There are lots of tutorials for this around the web

Pete

[Curufir]

Yeah, I'm thinking the real problem is that it's Win2k and the OS really isn't setup to handle these kinds of things without having the server edition.

[Therx]

what version of XP do you have. Couldn't you install that on it. Either that or make the Windows 2000 pc run off the linux one instead of the other way. As has already been said ruoting in Linux is at least possible

Pete

[Curufir]

Fixed, oh yeah baby, fixed!!!! ;D

I had everything setup ok, problem was that I hadn't actually given the other Windows comps a route to the 192.168.1.x network. Popped a quick 'route ADD' onto those comps and now my Linux machine can see both them and the outside world. Woohoo!!!

All credit must go to Mr Crapper and his amazing porcelain thinking aid .