I heard with modprobe ip_tables can start iptables, but after using this command:
Modprobe: ERROR:../libkmod libkmod. C: 514 lookup_builtin_file () could not open builtin file '/lib/modules/2.6.32-042 stab116. 1/modules. Builtin. Bin'
Modprobe: FATAL: Module iptables not found in the directory/lib/modules/2.6.32-042 stab116. 1

Confused now, what would be the iptables mistakes or modprobe error? How to solve?
There are other problems, such as: how to start the iptables, how to stop the iptables?
Tried the following command: service iptables start
Then an error, said there was no iptables this service, I clearly put
The iptables -l

Chain INPUT (policy ACCEPT)
Target prot opt source destination
ACCEPT the TCP - anywhere anywhere TCP DPT: SSH

Chain FORWARD policy (ACCEPT)
Target prot opt source destination

Chain the OUTPUT (the policy ACCEPT)
Target prot opt source destination

Enthusiasts helps small,,,,

CodePudding user response:

You can refer to http://blog.csdn.net/renwotao2009/article/details/51225359

CodePudding user response:

reference 1st floor renwotao2009 response:

can refer to http://blog.csdn.net/renwotao2009/article/details/51225359

Seen as point like gobbledygook, have at the moment, I just want to confirm the iptables start,
I tried the service iptables start
Results: Failed to start the iptables. Service: Unit iptables. Service not found
I've tried:/etc/init. D/iptables start
Results: bash:/etc/init. D/iptables: No to the file or directory

CodePudding user response:

refer to the second floor Porsion response:

Quote: refer to 1st floor renwotao2009 response:

You can refer to http://blog.csdn.net/renwotao2009/article/details/51225359

Seen as point like gobbledygook, have at the moment, I just want to confirm the iptables start,
I tried the service iptables start
Results: Failed to start the iptables. Service: Unit iptables. Service not found
I've tried:/etc/init. D/iptables start
Results: bash:/etc/init. D/iptables: No to the file or directory

did you install the iptables?

CodePudding user response:

reference renwotao2009 reply: 3/f

Quote: refer to the second floor Porsion response:

Quote: refer to 1st floor renwotao2009 response:

You can refer to http://blog.csdn.net/renwotao2009/article/details/51225359

Seen as point like gobbledygook, have at the moment, I just want to confirm the iptables start,
I tried the service iptables start
Results: Failed to start the iptables. Service: Unit iptables. Service not found
I've tried:/etc/init. D/iptables start
Results: bash:/etc/init. D/iptables: No to the file or directory

did you install the iptables?

Must be installed, Ann didn't install I still know,
Recently in the VPN server to use iptables do NAT forwarding, the result no matter what to do, can't ah, on the network warrior if have experience in this field still hope glad!!
Thank you for the

CodePudding user response:

In addition, this is my current set of rules:
Root @ localhost:/home/sam# iptables -t NAT - nL
Chain PREROUTING (policy ACCEPT)
Target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
Target prot opt source destination
SNAT all - 192.168.1.0/24 0.0.0.0/0:23.83.225.181

Chain the OUTPUT (the policy ACCEPT)
Target prot opt source destination
Root @ localhost:/home/sam#

CodePudding user response:

Please help!
The yao people for help, beginners, bad English,,,,

CodePudding user response:

Looks like the building to install the iptables command line, and from the point of the output of the iptables - L, also have different kernel modules, should be able to work properly,

In addition, serverice iptabels below (service) is just a pile of packaging services/scripts, have no relation, (mainly affects open automatically start)

PS, if talking about "start"/" stop "iptables, mostly refers to the iptables service, also is the service or the init. D control script directory,

CodePudding user response:

For an example (right), a bit like installed apache but no HTTPD service status,
Does not start automatically boot, but it doesn't interfere with the manual start,

CodePudding user response:

http://askubuntu.com/questions/687369/could-not-open-builtin-file-modules-builtin-bin
Looks like you have a mismatch between which the kernel version modprobe is & for 2.6.32-042 stab104. 1 vs the version you have installed (re) 3.19.0-30 - generic.
Use uname -r to dump your running kernel. It looks like you have some custom kernel installed - check your bootloader (probably grub) to see if It is hardcoded to some ancient home kernel the lastest installed kernel.
2.6.32 is old (ancient) enough that it probably doesn 't use modules. The builtin. Bin - so you have a mismatch in the your the modutils version vs your kernel

https://lists.debian.org/debian-boot/2014/09/msg00880.html
The kernel modules. Builtin is generated at build time and can 't be regenerated from the installed kernel or modules.

CodePudding user response:

nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull