2

I have two servers, using one for prod and one for dev. They are with different providers, and one is running Xen and the other OpenVZ (both running Ubuntu but 8.04 and 10.10 respectively). I've been having an issue with the OpenVZ server setting up my iptables because apparently its missing some kernel modules. When I run lsmod | grep ip I get these results:

Xen-

$ lsmod | grep ip
ipt_LOG                 8192  1 
nf_conntrack_ipv4      21904  2 
nf_conntrack           79344  2 nf_conntrack_ipv4,xt_state
ipt_REJECT              6528  3 
iptable_filter          4608  1 
ip_tables              24232  1 iptable_filter
x_tables               23432  6 ipt_LOG,xt_limit,xt_tcpudp,xt_state,ipt_REJECT,ip_tables
ipv6                  313384  18 
multipath              11008  0 
md_mod                 89500  6 raid10,raid456,raid1,raid0,multipath,linear

OpenVZ-

BLANK, there is nothing returned...

So my questions are, 1) Why am I getting nothing returned for the OpenVZ server, and 2) How do I load the necessary modules?

UPDATE:

This is the result of trying modprobe

$ modprobe nf_conntrack
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
FATAL: Module nf_conntrack not found.
GiH
  • 121

1 Answers1

0

It turns out that I am unable to load kernel modules to a container, since all containers on OpenVZ platforms use the same kernel (unlike Xen). What I needed to do was get in touch with my provider and have them enable iptables for me. After that all rules worked.

Funny thing is I still don't have any output by typing lsmod | grep ip and there still doesn't seem to be any kernel folder in my /lib/modules/$(uname -r) folder. I guess this is not accessible from within a container.

GiH
  • 121