Victor Julien

I haven't seen this before. It looks like keypad is provided by ncurses, which is on your linker line. In my own system (ubuntu) ldd shows it links against libtinfo.so.6 as well even though this is not in my ldd output. Interesting that your output shows libtinfow.so.6 (so wide version), while mine doesn't despite my ncurses being wide as well: linux-vdso.so.1 (0x00007ffed636d000) libvuurmuur.so.0 => /lib/libvuurmuur.so.0 (0x00007efd39969000) libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6...

Ah that is a nice solution. Thanks for sharing it here!

Hi Sven, it's not possible. Maybe you can use vuurmuur_script to update the interface settings on the fly, but I'm not sure how that would work with docker.

Thanks for your report. I've fixed it in the git master: https://github.com/inliniac/vuurmuur/pull/34 I'll try to figure out the akismet thing too.

I've pushed this fix: https://github.com/inliniac/vuurmuur/commit/f90ec591f634f51596892ef299f399192320db0d

It seems these are defined on my system in "/usr/include/linux/netfilter/nf_conntrack_tcp.h". On my Ubuntu 18.04 this is part of the linux-libc-dev:amd64 package. Maybe slackware has something similar? I will create a workaround/fix to make sure we don't depend on these.

I can see how it would be useful to have maybe a 3rd object type within a network that holds netblocks that fit within the network space. No plans for that currently though. Maybe a feature ticket would be useful. Tickets live at https://www.vuurmuur.org/trac/report What issues did you have on Arch?

To get the rule list with vuurmuur_script, this is the somewhat cryptic command:...