I'm currently puzzling over the same thing. I'm wondering if firestarter is perhaps reading the logs and deciding a long-gone connection whose opening was recorded in them has never closed? I had this problem on gutsy, now I'm having it on hardy.
I have no idea where firestarter is getting its information. It's still not impossible that it knows something we don't! I did look in /proc/net/tcp, you just need to convert the port number to hex (run bc, set obase=16, then type the port number and bc will spit it out in hex) before you can look for it in the proper column (*_address) and I didn't find my connection there. As far as I know, /proc "knows" everything that the kernel knows about connections. Erk, as I write this I am trying more things. In /proc/net/ip_conntrack I find my connection: tcp 6 201847 ESTABLISHED src=192.168.1.23 dst=98.204.109.154 sport=37835 dport=30541 packets=1 bytes=164 [UNREPLIED] src=98.204.109.154 dst=192.168.1.23 sport=30541 dport=37835 packets=0 bytes=0 mark=0 secmark=0 use=1 tcp 6 201858 ESTABLISHED src=192.168.1.23 dst=98.204.109.154 sport=37853 dport=30541 packets=1 bytes=136 [UNREPLIED] src=98.204.109.154 dst=192.168.1.23 sport=30541 dport=37853 packets=0 bytes=0 mark=0 secmark=0 use=1 I have no idea what this is or where it came from. There's also matching (?) entries in /proc/net/nf_conntrack. No program is listed by firestarter, so it seems like this is a phantom connection... I'd very much like to know where it came from, though. -- Closed connections shown in "Active connections" https://bugs.launchpad.net/bugs/112334 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
