I'm browsing the Logview, I press M and choose a connection:
DROP 500->500(udp) 62.149.229.193 -> 84.222.xx.yy (me)
that I want to block since it's several days that it's insisting to connect every few seconds.
I press ENTER and choose "Add Source to Blocklist", but I get this error:
Error: command '/usr/sbin/conntrack -D -s 84.222.xx.yy -d 210.206.16.94 -p udp --orig-port-src 38742 --orig-port-dst 42771' failed.
Please note that this wasn't the connection that I was viewing.. It's a P2P connection that was vanished. And this is always reproducible. I pick up a connection, try to block it and I get an error regarding another connection..
What happened?
10x!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, it isn't. It reports that several connections can't be killed.
I thought that it suffers of this problem only with lots of vanishing connection (p2p is the case) because I successfully used it before, but however by lowering the connections number and trying to block an IP using the same method I got:
"Warning: all connections already gone, none killed."
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm browsing the Logview, I press M and choose a connection:
DROP 500->500(udp) 62.149.229.193 -> 84.222.xx.yy (me)
that I want to block since it's several days that it's insisting to connect every few seconds.
I press ENTER and choose "Add Source to Blocklist", but I get this error:
Error: command '/usr/sbin/conntrack -D -s 84.222.xx.yy -d 210.206.16.94 -p udp --orig-port-src 38742 --orig-port-dst 42771' failed.
Please note that this wasn't the connection that I was viewing.. It's a P2P connection that was vanished. And this is always reproducible. I pick up a connection, try to block it and I get an error regarding another connection..
What happened?
10x!
Sounds like a bug to me, I've added a ticket for it: http://www.vuurmuur.org/trac/ticket/96
Is the right ip address added to blocklist?
No, it isn't. It reports that several connections can't be killed.
I thought that it suffers of this problem only with lots of vanishing connection (p2p is the case) because I successfully used it before, but however by lowering the connections number and trying to block an IP using the same method I got:
"Warning: all connections already gone, none killed."