Re: Command not working in latest version

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2003-02-17 at 00:54, Paulo J. Matos wrote:

> Hi Khanh,
> 
> I've compiled the kernel specifically like they said in your reference
> except those new options of 2.4.20 but still I get 'Invalid Arguments' from
> iptables 1.2.7a. What's Full NAT in kernel config, is that useful for
> iptables?
> 
> I've run the line:
> # iptables -v -t nat -A POSTROUTING -o eth1 -j SNAT --to 217.129.146.56
> SNAT all opt -- in * out eth1 0.0.0.0/0 -> 0.0.0.0/0 to:217.129.146.56
> iptables: Invalid Argument
> 
> This is indeed strange. Do you have any idea of what could I do now?
> 
> Is there any other iptables command line with the same outcome?

I just have to put an end to this thread :)

The solution is simple, recompile userspace iptables against your new
kernel.
A major NAT patch was included in 2.4.20 that breaks compability so you
have to recompile userspace iptables against the new kernelheaders to
get NAT working again (same for the owner match).

-- 
/Martin

Never argue with an idiot. They drag you down to their level, then beat you with experience.


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux