When I do
# shorewall show capabilities
it hangs and there's nothing to grep
# ipset -V
ipset v6.12.1, protocol version: 6
# ipset --help | grep -P hash:ip
hash:ip,port,net
hash:ip,port,net
hash:ip,port,net
hash:ip,port,ip
hash:ip,port
hash:ip
If I use screen to run shorewall show capabilities then I can see the following
process running in top
ipset -N fooX22329 hash:ip family init
--
Meet PCI DSS 3.0 Compliance
Also shorewall show capabilities gives the same error in the log
kernel: Can't find ip_set type hash:ip
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Hi Tom !
thanks for your reply to my message, I'll do some tests with your
suggestions and if I'm in trouble again I'll send you the dump.
2014-09-30 21:43 GMT+02:00 Tom Eastep teas...@shorewall.net:
On 9/30/2014 1:32 AM, rob...@gmail.com wrote:
Hi all,
I'm new to this list so hi! and
On 10/1/2014 12:11 AM, Dik wrote:
If I use screen to run shorewall show capabilities then I can see the
following process running in top ipset -N fooX22329 hash:ip family init
Hopefully that is a typo and the command actually reads '...family inet'.
root@gateway:~# cat
Sorry, yes typo. it reads :
ipset -N fooX259244 hash:ip family inet
# cat /etc/debian_version
7.6
The command
ipset -N fooX22329 hash:ip family inet
also hangs in the terminal while showing in top
I have done a kernel update but the machine has not been rebooted to use the
new kernel. Could
On 10/1/2014 10:48 AM, Dik wrote:
Sorry, yes typo. it reads :
ipset -N fooX259244 hash:ip family inet
# cat /etc/debian_version
7.6
The command
ipset -N fooX22329 hash:ip family inet
also hangs in the terminal while showing in top
I have done a kernel update but the
So what does the error mean ?
kernel: Can't find ip_set type hash:ip
I have already connected Proxmox who say that until they developed their own
firewall they used Shorewall. However since Shorewall is not included with
Proxmox as standard they do not support it. Their newly developed
On 10/1/2014 2:18 PM, Dik wrote:
So what does the error mean ? kernel: Can't find ip_set type
hash:ip
It likely means that the ip_set_hash_ip module isn't being located for
some reason. Do you see it in the output of lsmod?
-Tom
--
Tom Eastep\ When I die, I want to go like
:~# lsmod
Module Size Used by
dm_snapshot30545 0
vzethdev8189 0
vznetdev 19264 18
pio_nfs18511 0
pio_direct 27912 0
pfmt_raw3213 0
pfmt_ploop1 6384 0
ploop
On 10/1/2014 3:22 PM, Dik wrote:
:~# lsmod
Module Size Used by
...
xhci_hcd 140845 0
A simply 'yes' or 'no' would have sufficed!
I assume that 'modprobe ip_set_hash_ip' also fails? If so, then I would
go ahead a
On October 1, 2014 11:18:32 PM Dik di...@hotmail.com wrote:
So what does the error mean ?
kernel: Can't find ip_set type hash:ip
If I can't get help here I have no idea where to go.
The above error says ipset is missing in current running kernel
~# modprobe ip_set_hash_ip
libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open
moddep file '/lib/modules/2.6.32-24--pve/modules.dep.bin'
When I do :
~# ls /lib/modules/*/modules.dep.bin
I can only see modules for the most recently installed kernel.
I have now
Hello,
Thanks for your preceeding two replies - much appreciated !
I have three questions regarding running an IPv6 configuration which
could surely benefit from your experience, since they are not directly
related to Shorewall, but happens when using the IPv6 portion.
1) When shorewall6 is
On 10/1/2014 5:01 PM, jone...@teksavvy.com wrote:
Hello,
Thanks for your preceeding two replies - much appreciated !
I have three questions regarding running an IPv6 configuration which
could surely benefit from your experience, since they are not directly
related to Shorewall, but
Hi,
I see that in 4.6.0 [1], USE_DEFAULT_RT was changed to Yes by default. I
couldn't find any documentation of this change in the release notes. I
can see why this change was made, however I want to use quagga for
routing, which inserts routes into the main routing table. Although it
looks like
16 matches
Mail list logo
