With 10.04 LTS I found, that there is workaround - just to fix wrong
file reference in the firestarter sysctl-tuning - last paragraph has to
be like this:
# Doubling current limit for ip_conntrack
if [ -e /proc/sys/net/ipv4/ip_conntrack_max ]; then
echo 16384 > /proc/sys/net/ipv4/netfilter/ip_c
** Changed in: firestarter (Ubuntu)
Status: New => Invalid
--
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
ubu
If you are really worried about this reporting error, it's a state timeout
issue with ip_conntrack and isn't going to be addresses since they don't
consider it to be a problem.
If you want to flush the list and get it recreated do: 'apt-get install
conntrack' and then 'conntrack -F' as root. Thi
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 inf
I just installed Firestarter on a 7.04 system at home and have started
to see this problem.
This morning, several "active connections", originating on my home
system and going to weird high-numbered ports on a target system I had
never heard of before, were being reported by Firestarter. "netstat
I think I can confirm this bug. I had an attacker try an ssh dictionary
attack, so I blocked ssh traffic from his network. Iptables confirms
that the subnet has been blocked and netstat and ps confirm that there
are no connections from that address. To be extra sure, I attached a
clean computer to
