Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

iptables help. Error iptables v1.4.7: can't initialize iptables table `nat'

CamCam Patron Provider, Veteran
edited July 2017 in Help

Hello,

I am getting an error whenever I am trying to add any iptable rules. For example if I runiptables -t nat -L
I get response,
iptables v1.4.7: can't initialize iptables table nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.

I have a fresh install of CentOS 6.8 with SolusVM successfully installed and booted into the OpenVZ kernel 2.6.32-042stab123.8.

lsmod gives,
https://pastebin.com/YeTbGReK

I have tried grep -R "options nf_conntrack ip_conntrack_disable_ve0=0" /etc/modprobe.d/ still without any luck of it working.

Thanks,
Cam

Comments

  • cubedatacubedata Member, Patron Provider
    edited July 2017

    you scare us if you cannot even google something like this since it isn't that hard and usually with you being a "provider" with the provider tag and running a web hosting business you are at least expected to have some knowledge at least on how to fix issues like this which leads us to this meme instead lol:

    you also have already asked this already before it appears:
    https://lowendtalk.com/discussion/102444/ip-tables-and-kernel-help#latest

    Thanked by 1rm_
  • CamCam Patron Provider, Veteran

    @cubedata said:
    you scare us if you cannot even google something like this since it isn't that hard and usually with you being a "provider" with the provider tag and running a web hosting business you are at least expected to have some knowledge at least on how to fix issues like this which leads us to this meme instead lol:

    Thank you for showing how kind you are to LET. I am reaching out on here because I have looked up and down trying many things to resolve this. I am not the type of person who usually reaches out for help on issues like this but this is something that is actually giving me a tough time.

    Don't tell me that I didn't try to google this. Because you really don't know.

    Thanks,
    Cam

  • dragonballz2kdragonballz2k Member
    edited July 2017

    @cam246 said:
    Hello,

    I am getting an error whenever I am trying to add any iptable rules. For example if I runiptables -t nat -L
    I get response,
    iptables v1.4.7: can't initialize iptables table nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.

    I have a fresh install of CentOS 6.8 with SolusVM successfully installed and booted into the OpenVZ kernel 2.6.32-042stab123.8.

    lsmod gives,
    https://pastebin.com/YeTbGReK

    I have tried grep -R "options nf_conntrack ip_conntrack_disable_ve0=0" /etc/modprobe.d/ still without any luck of it working.

    Thanks,
    Cam

    this webpage could help https://serverfault.com/questions/593263/iptables-nat-does-not-exist, and shouldn't you update to CentOS 6.9

  • CamCam Patron Provider, Veteran

    @dragonballz2k said:

    this webpage could help https://serverfault.com/questions/593263/iptables-nat-does-not-exist, and shouldn't you update to CentOS 6.9

    Hello,

    Thanks for that. I did look at that page and tried the answer with no luck.

    I run grep -R "options nf_conntrack ip_conntrack_disable_ve0=0" /etc/modprobe.d/ and reboot and still get the same error when adding a rule.

    Typo on my part, it is 6.9.

    Thanks,
    Cam

  • Which kernal version?

  • CamCam Patron Provider, Veteran

    @PieNotEvenEaten said:
    Which kernal version?

    2.6.32-042stab123.8

  • FalzoFalzo Veteran

    cam246 said: I run grep -R "options nf_conntrack ip_conntrack_disable_ve0=0" /etc/modprobe.d/ and reboot and still get the same error when adding a rule.

    you also did the part of changing that setting to 1 in the file you hopefully found and just omitted that part here? just so to say... grepping for a file won't change anything after all ;-)

    Thanked by 2netomx Cam
  • Grep nf_conntrack /boot/config*

  • UnixfyUnixfy Member

    You need to set iptable_nat in vz.conf on the host node. https://forum.openvz.org/index.php?t=msg&goto=42693&;

  • CamCam Patron Provider, Veteran

    @Falzo said:

    cam246 said: I run grep -R "options nf_conntrack ip_conntrack_disable_ve0=0" /etc/modprobe.d/ and reboot and still get the same error when adding a rule.

    you also did the part of changing that setting to 1 in the file you hopefully found and just omitted that part here? just so to say... grepping for a file won't change anything after all ;-)

    FACEPALM! Thankyou I cannot believe that haha. You made my day! Send me a PM if you want me to hook you up with some hosting =D

    Thanks,
    Cam

    Thanked by 1Falzo
  • CamCam Patron Provider, Veteran

    @PieNotEvenEaten said:
    Grep nf_conntrack /boot/config*

    @karatekidmonkey said:
    You need to set iptable_nat in vz.conf on the host node. https://forum.openvz.org/index.php?t=msg&goto=42693&;

    Thanks guys for the help.

  • agentmishraagentmishra Member, Host Rep

    i tried every thing, but still getting the same error

    my old machines are working fine, new virtualizor install gives this error

    what shall i do?

  • bapbap Member

    Provider tag! Should I panic now??

    Thanked by 2AnthonySmith Rhys
  • rm_rm_ IPv6 Advocate, Veteran

    Yeah "I ran grep and rebooted", this is golden.

    Thanked by 1Janevski
  • @bap said:
    Provider tag! Should I panic now??

    For?

  • mfsmfs Barred

    bap said: Should I panic now??

    On the Internet, you can never guess who's who. Could be worse

    Thanked by 1perryoo11
  • You should hire someone with knowledge to protect your clients... Copy&Paste from Google is dangerous

  • CamCam Patron Provider, Veteran

    You guys should look at the dates... this is from July......

This discussion has been closed.