search for: brendlerjg

...viously, that''s the simple work-around (explicitly enable logmartians where needed), but this seems to be contrary to the (new) behavior described in the man page for shorewall-interfaces and the release notes. Information required per web site: # shorewall version 4.0.9 # ip addr show brendlerjg@typhoon ~ $ sudo ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether...

...negative Product: ipset Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P1 Component: default AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy: brendlerjg at gmail.com I have been using ipsets for years, but am attempting to implement a setlist for the first time, using version 4.2. I have created a setlist, including three ipsets (all of type nethash). I am trying to validate that it works before incorporating into my firewall. When I use '...

I have been using shorewall for years with ipsets. I have encountered a problem after upgrading from 4.2.11 to 4.4.10. When I run ''shorewall-check'' or ''shorewall start'', it halts with the error: ---------------------------------------------------------------------- ERROR: ipset names in Shorewall configuration files require Ipset Match in your kernel and