this use to happen distinctly with woody unstable
it was a pain to see this message coming up every now and then
Suraj had warned me about this....
R Deepak wrote:
Is this even possible under normal circumstances? I've never ever seen
a system which did not have lo up and running.
I came across this problem in my Debian Woody box two years ago. The
reason was that 'lo' was not up. See some pointers below.
http://www.uwsg.iu.edu/hypermail/linux/kernel/0001.2/0255.html
http://lists.debian.org/debian-user/2000/06/msg00175.html
http://lists.netfilter.org/pipermail/netfilter/2000-October/005519.html
But, I've seen this error a lot when there is heavy portscan traffic
on the network.
I don't deny that there may be other problems that causes this one. Some
more pointers.
http://www.linuxgazette.com/node/view/509
http://cert.uni-stuttgart.de/archive/suse/security/2003/08/msg00226.html
(look into the follow-ups as well)
--
Bangles hang loose, shoulders have faded from bridal
beauty, exposing his soulless cruelty in deserting me
(withering of beauty - 5), Thirukkural
http://puggy.symonds.net/~praveen
_______________________________________________
To unsubscribe, email ilugc-request@xxxxxxxxxxxxx with
"unsubscribe <password> address"
in the subject or body of the message.
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc