sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE -v
iptables v1.6.0: can't initialize iptables table `nat': Table does not
exist (do you need to insmod?) Perhaps iptables or your kernel needs to
ls -l /lib/modules
drwxr-xr-x 3 root root 4096 May 24 03:32 4.14.34+
drwxr-xr-x 3 root root 4096 May 24 03:32 4.14.34-v7+
I think I understand that /lib/modules will need to have an entry for
4.9.80+ but doesn't.
I've run sudo apt upgrade so I don't think that's a problem .But I
don't see how to proceed. Anyone?
> I want to configure nat and I get this:
> sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE -v
> iptables v1.6.0: can't initialize iptables table `nat': Table does not
> exist (do you need to insmod?) Perhaps iptables or your kernel needs
> to be upgraded.
> uname -r
> ls -l /lib/modules
> total 8
> drwxr-xr-x 3 root root 4096 May 24 03:32 4.14.34+
> drwxr-xr-x 3 root root 4096 May 24 03:32 4.14.34-v7+
> I think I understand that /lib/modules will need to have an entry for
> 4.9.80+ but doesn't.
> I've run sudo apt upgrade so I don't think that's a problem .But I
> don't see how to proceed. Anyone?
Did you perhaps remove the package for the 4.9.80+ kernel and didn't
reboot afterwards? Maybe you should mention which *Ubuntu version you
Those Raspberry Pi techies are seemingly missing basic Linux
troubleshooting skills, perhaps they should consider to start with an
averaged Linux computer first, instead of using a Raspberry Pi.
Since the OP is booted to 4.9.80 and the modules are for 4.14.34, it's
most likely the issue mentioned by Nils. A kernel was updated and
perhaps the older running kernel was removed, but it was not rebooted.
Instead of posting a lot of irrelevant output, it might be worth to run
Am Donnerstag, den 24.05.2018, 11:43 +0200 schrieb Ralf Mardorf:
> On Thu, 24 May 2018 10:35:33 +0200, Oliver Grawert wrote:
> > this is not an ubuntu kernel, where did you get it from ?
> This seems to be a kernel for a Raspberry Pi, see
well, my point was not to criticize whoever created this kernel :)
but it is a fact that the ubuntu kernels have a certain set of config
otions enabled (namespaces, cgroups, certain options systemd uses,
options that lxd containers rely on, options that snap packages rely on
and last but not least firewall options like iptables) ...
ubuntu userspace apps expect certain kernel defaults to be there to
operate as expected/tested.
if you use a third party kernel that you did not build yourself with an
ubuntu config you can easily run into more issues ...
The Raspberry Pi kernel update removes/replaces the older kernel and its
modules, unlike either the Ubuntu or RHEL/CentOS kerne updates, which
*install* the new kernel along side the old kernel. It is a "weird" thing to
do, but a reboot will likely solve the OP's problem.
> Instead of posting a lot of irrelevant output, it might be worth to run
> apt list --installed 'linux*'; lsb_release -a