Well, I fixed it. Man is this embarassing.... I changed my MCPU from 686 to 586 and re-emerged it.
I guess a K6-2 isn't a 686... Thanx for your help. Mike Diehl. On Monday 10 March 2003 2:10 pm, Jesse Jacobs wrote: > Thinking again ..... > This only applies if serving ip's to windows boxes. > Also check UDP port 67 - in and 68 - out of the interface. > HTH again, > J. > > Jesse Jacobs said: > > Hello Ian, > > > > just type as is > > route add --host 255.255.255.255 dev eth0 > > this allows the routing decision to believe that the 255.255.255.255 is > > the local host which passes the request to local processes(i.e. dhcpd) > > > > HTH, > > J. > > > > Ian Tindale said: > >> On Monday 10 March 2003 8:22 pm, you wrote: > >>> Hello Ian, > >>> Did you add the broadcast host to your routing? > >>> > >>> route add --host 255.255.255.255 dev eth0 > >> > >> That's a good point - I daren't change the routing right now, as it > >> took me two weeks to arrive at the way it is now, during which I > >> couldn't connect to the internet at all. I'll investigate your > >> suggestion when things are safe to do so. What's the '--host' part - > >> does that get typed in just as is? > >> > >> > >> > >> -- > >> Ian Tindale > > > > ----------------------------------------- > > Jesse Jacobs, R.H.C.T. > > Ajax, ON Canada > > > > > > > > -- > > [EMAIL PROTECTED] mailing list > > ----------------------------------------- > Jesse Jacobs, R.H.C.T. > Ajax, ON Canada > > > > -- > [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
