Routing issues with muliple NICs

[OzDog]

OK, here's the deal,

I have a 3Com 3C905 installed as Eth0, and an Aironet Wireless as eth1. The wireless is hooked up to my corporate LAN.

I am currently not using Eth0, (although it is up & running, nothing plugged into it) and am connecting to the corporate LAN to access Citrix servers. This is working fine.

The problem I am having, is that I can't route externally beyond the coprorate LAN (ie the Net) from my PC when Linux is loaded, and I am too much of a Linux newbie to know why. I understand IP very well, have checked the route tables and tracert and they are all using the right interfaces. Beyond that I am at a loss. When booted to Win2K all works fine, so I know that it's not a hardware issue, nor any problems with the switches etc.

I'm not sure where to look, and would appreciate any help. Cheers,
Sam

Please let members know if you found their posts helpful.

 

[RiezalR]

You are trying to access the Internet via eth0 or eth1?

 

[OzDog]

Eth1 - via work. Cheers,
Sam

Please let members know if you found their posts helpful.

 

[RiezalR]

Well the only thing i can think of would be a routing problem. Since you say you understand IP very well, then there is no point me trying to explain routing. Another thing might be the IP's of the NIC itself. I presume that you have already set different IP's for eth0 and eth1. Is there any firewall restrictions or IP Masq setting running on your LAN server? Since Win2K runs fine with the current setting, but not linux, then i can't think of any ways to troubleshoot your problem.

To my knowledge, setting up a wireless link and a normal wired network link is quite similiar. It involves assinging the right IPs, setting the routers and gateways. If you say that the gateways and IPs currently assigned to eth1 can work while in Win2K but not on Linux, then I myself am puzzled. Sorry that i can't be of much help.

 

[OzDog]

That's pretty much why I'm stumped cod3x. I have set the NICs up with the same IPs, masks and gateways as in Win2k (the wireless obviously won't work otherwise).

My internal is just a Class C private network (192.168.0.0/24) with card at 0.1, and another machine connected to it at 0.2. They can communicate fine, and the .2 can ping through to the work wireless network.

The work WAN is a separate Class A network with a variable subnet. It appears to be working fine from home to work but not beyond that to the web.

I guess that it's more of an issue of not knowing where to look than anything else. The Wireless interface is working fine, so it's just another NIC interface now...

Thanks anyway, I'll just keep plugging away... I guess Cheers,
Sam

Please let members know if you found their posts helpful.