For many people, running routed is not necessary. Many times, all one needs is a static default route. For example, 192.168.1.0/24 is via eth1 and everything else on the planet is via eth0. In any case, you might want to get things working with static routes before debugging routed.
Ensure both network interfaces are working. Can you ping a host connected to each interface? What does 'netstat -nr' show? Does it show a route to the network you are trying to reach? cheers, Mike On Tuesday 09 July 2002 03:00 pm, Adrian Hunt wrote: > Hi all, > > I've read a few TFM's ;-) but can't seem to figure it > out on my own. I have a very simple routing need, for > the time being, and yet I can't seem to figure it out. > > Without even addressing the firewall aspect at this > point, I'm simply trying to take one machine with 2 > network interfaces (192.168.1.1 and 192.168.2.1) and > convince it to route IP traffice such that 192.168.2.X > can ping, telnet to, print to, etc. 192.168.1.X. > > I've echo'd 1 > /proc/sys/net/ipv4/ip_forward, and > hoping for a miracle I installed 'routed' and started > it to no avail. All the firewall tables are > completely flushed. All machines have 192.168.x.1 set > as their default route, x being whichever subnet > they're attached to and configured properly on. The > routing box can see/ping all the desktops on both > networks, and vice-versa. I simply can't get traffic > from one desktop to another. > > Any help is appreciated! > > TIA! > > Adrian. > > __________________________________________________ > Do You Yahoo!? > Sign up for SBC Yahoo! Dial - First Month Free > http://sbc.yahoo.com > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
