Bernd Eckenfels wrote: > > In article <39F2CF2F.F71BE884@danbbs.dk> you wrote: > > Another thing is funny: ipchains -L takes a l-o-n-g time to finish > > showing up masqueraded nets in the forward chain; they get through one > > by one, 10-20 secs apart. Definitely seems related. > > it is a nameserver issue, use -L -n Not sure. The setup at my customer doesn't differ that much from my own, except for two things: Here I am running a caching nameserver, and have dhcp on only one netsegment, so I never used dhcrelay. I just tried starting dhcrelay to listen on that segment, and immediately I had the same nameresolution situation as with my customer. A kill -9 `pidof dhcrelay` didn't make my nameresolution work again; had to restart various networkservices. What's weird is that a second attempt at using dhcrelay _didn't_ have that effect; nameresolution continued to work. I also tried combinations of stopping dhcpd, then starting dhcrelay, then dhcpd; or starting dhcpd first, then dhcrelay. I would like to be able to reproduce the malfunction I had when I first tried dhcrelay, but... I'll be going to my customer in about an hour, trying out various ways of manually starting those services. Pls. do reply if you have anu pointers. -- Regards, Mogens Valentin Networking - Security - Programming Linux configuration and troubleshooting http://www.danbbs.dk/~monz - monz@danbbs.dk - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
