On Sat, Apr 15, 2000 at 12:06:01AM +0000, Jim Breton wrote: > On Fri, Apr 14, 2000 at 06:31:02PM -0600, David Karlin wrote: > > Hello, > > I have a slink box which has been running great. It was up for over > > 45 days without a hitch. > > > > The box does ipmasq-ing (among other tasks) for my lan, but when it > > is booted, it won't respond to a ping, telnet, ftp, or http request > > until I make a network connection _from_ that box (eg. ping another > > box on the lan, or make a PPP connection to my ISP). > > > > Anyone else had this happen? > > > I've never had that happen... but I wonder if it might be a module that > is being loaded on-demand by the box, in which case the box can't know > that it's needed until one of the local processes needs that module. > > When you boot the machine, run lsmod and take a look at what modules are > loaded before the networking starts to work. Then perform some network > operations and run lsmod again. Are the lists different?
I ran lsmod before and after. No change. :-/ -- David Karlin [EMAIL PROTECTED] Powered by Debian GNU/Linux