Hans van den Boogert <[EMAIL PROTECTED]> wrote: > Can I safely answer "no" to those two questions and get by with amending the > /etc/resolv.conf and /etc/hosts files?
Yes. If you were installing mack and were planning on ip masqing, then 'yes' answers might save you some time, but the system looks to those files (and others) for its configuration. > /etc/resolv.conf > > domain fleamarket.nl (this being my local domain name) > search fleamarket.nl > nameserver "IP number of my ISP's nameserver" Looks like overkill; I _think_ it's not recommended to use both 'search' and 'domain'. I would first try a bare bones: nameserver "IP number of my ISP's nameserver" > /etc/hosts > 127.0.0.1 localhost loopback > 192.168.0.1 mick.fleamarket.nl > 192.168.0.2 mack.fleamarket.nl I would make that look like: 127.0.0.1 localhost 192.168.0.1 mick.fleamarket.nl mick 192.168.0.2 mack.fleamarket.nl mack > I'm afraid to get into routing trouble, where mick doesn't query the ISP's > DNS server. I had this before: the local network worked fine, but I > couldn't get mick to route to the internet for addresses other than > 192.168.01 and 192.168.02. Not sure what you mean by that last sentence, since you say you are *not* connecting mack to the internet. Off the top of my head I wonder if you had 'defaultroute' set as a ppp option? -- Bob Bernstein http://members.home.net/ruptured-duck at Esmond, Rhode Island, USA --==++*++==-- "RMS's "curmudgeon-like" griping that he didn't like the term "Open Source" looked silly to many last year; it's not looking so dumb today..." Christopher B. Browne
