Stephan Hachinger wrote (on 25 Feb 2002 at 17:36): > machine I want to configure as router is 192.168.90.95 (stephan). > Stephan has a second network card inside (192.168.37.95) and > connects to the internet over this card and dsl (pppoE). Now, > this is what I've tried: > > -Modifying the route table on pentiumdioxid (see attached route > output)-Installing dnrd, a dns forwarder, on stephan (dns > resulution seems to work without problems now)-setting ip_forward > to "yes" in /etc/network/options on stephan > > I've also attached hosts.allow and hosts.deny.
Been up for over four hours and no answers yet? Well then: I don't see anything in the above about any NAT, which you need if those private-IP hosts are going to talk to the Internet. You didn't say what kernel version you're running, so read the documentation on either ipchains or iptables--or go straight to the IP-masquerading Howto. > The problem is, when I try to ping www.debian.org from > pentiumdioxid, pentiumdioxid gets the ip adress of debian.org > (198.186.203.20) but it doesn't get any packages back. Well, you have a name server on your gateway machine, so that's where you're getting the IP address from. The internal computer apparently made no contact with the Internet at all. > P.S.: Into which file can I put the routing table modifications > so that the modified routing table is automatically loadad at > startup? If there's an /etc/init.d/ppp*, that might be an appropriate place. If not, there's always /etc/init.d/networking, or copy that to a new name, edit it a lot, and read man update-rc.d about the order of execution of the init scripts and see how to set your routes after the interfaces are up. T. -- -- Tony Crawford -- [EMAIL PROTECTED] -- +49-3341-30 99 99 --
