Hello I've been hunting around forums trying to find a solution to this problem. I have a server running Ubuntu 8 connected to a cable modem, serving files and running a few services that make outbound connections. I have a second Cable modem connected to a Linksys WRT router running Tomato which acts as the gateway/router for my LAN.

I would like to get the server connected to the LAN without having it use the LANs gateway for Internet traffic. Rather only allow connections to LAN IPs so I can finally stop using ridiculous methods like memory sticks or going out through the Internet.

I've found a few guides on how to do this with multiple Internet connections on the same machines, but none with multiple gateways and multiple connections on physically different devices. I've tried simply connecting eth1(eth0 is modem) to the LAN and firing up samba. It worked initially and then stopped. Not sure why but could speculate.

Sorry if this is a trivial question, I'm still new to Linux and have a lot to learn. Thank you in advance for any help.

Regards,
Rovon

From what you've described you haven't got multiple gateways at all. Looking at those tags you've added, you don't want to bridge anything, you don't want to share anything... you have a normal network in the majority of ways, and don't want to do anything deviant where there are changes.

From the LAN, this server would just be another node on the LAN. you need no special measures to take in any way. just give it a lan conection on a nic, and off you go.

Okay well I'll try that again tonight.

I'm still not clear on what would stop the Ubuntu server from making requests through eth1 to the linksys router rather than the modem on it's eth0. It would have two gateways as it would have the cable modems gateway and the 192.168.0.1 gateway which is the router. Is there some kind of innate preference that would have it use the modem instead of the LANs gateway?

well would WOULD it route through an alternative router? How do you expect it to know that it even exists? if you don't explicitly tell it that 0.0.0.0/0 exists via two routes, it's not going to know two routes exist. DHCP *could* cloud the issue, but you should not be using DHCP on a server interface in the first place.

Okay I think I understand. I'll give it a shot tonight and see how it works. I'll post tonight/tomorrow on how it went.