In response to:
=============================================== This is still a problem as of 18-August-2015: http://vuurmuur-users.narkive.com/1W0jUSnb/existing-ssh-session-being-killed-during-rule-application I loaded nf_conntrack_ipv4 ahead of time, even logged out and back in, then did the vuurmuur startup and it killed my ssh connection. This makes the vuurmuur package unusable. If there is no remedy soon we'll have to remove this package from our embedded distro. # vuurmuur -V Vuurmuur 0.8rc1 (using libvuurmuur 0.8rc1) Again, its such a disagreeable behaviour that it makes the package unusable. Dick =============================================== I have found the same. The funny thing is that I currently only experience it by doing Log View -> Traffic Log -> m (manage) -> block source. And only when I do it on one IP address that targetted 8080, which was dropped. I have used the same multiple times to block someone brute forcing ssh, (or doing some dictionary attack on root user (which can't even be logged in lol) and without issue. Whenever, it was consistent and repeatable, whenever I blocked that single IP that targetted 8080, my SSH connection would be dropped but also when I used Screen to troubleshoot it, my SSH connection would obviously still be dropped but upon reconnecting to the screen, there was no other output such as the 100%/100% updating/applying configuration thing. Meaning (obviously, probably?) it did not even proceed to do anything useful after killing my SSH. I haven't experienced this in any other way yet. Regards, Bart. ------------------------------------------------------------------------------ _______________________________________________ Vuurmuur-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vuurmuur-users
