[Bug 12385] lo0 loopback device not activated by default

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=12385
Ubuntu | ifupdown





------- Additional Comments From tpotato at gmail.com  2006-01-11 15:49 UTC -------
(In reply to comment #3)
> This bug caught my eye because I maintain a firewall app and until I made very
> sure to allow all traffic on lo, I got this complaint a lot.  "Gnome doesn't
> work when I use your firewall."  Gnome for some reason generates tcp traffic on
> lo in an invalid way, and if your firewall drops packets with an invalid state
> or with an invalid combination of tcp flags, this issue will occur.  I have no
> idea how to determine what part of gnome this problem exists in, but I have seen
> the exact same problem with gkrellm (I don't use gnome) so gtk might be a
> reasonable place to start looking.  Over the past couple of years (this problem
> has been around a long time) I've brought it up in various gnome development
> forums but not found anyone interested enough in it to reply to me.

Well this same problem I was complaining about occurred with kde on breezy also.
The problem was created by the installer BTW. I didn't go back and change 
the file. So they really do need to fix it. Also IMHO 
a firewall should definitely block any traffic coming in FROM THE NETWORK to or
from localhost. That's what I was complaining about because the other machine 
crashed apparently due to receiving this traffic via eth0. I know enough 
about the internal design of these network devices to know what is really going 
on there.


-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.