|
From: Stefan E. <ste...@av...> - 2007-09-02 21:54:04
|
Hi, the problem is located in the pptp-conntrack-nat support code. Somewhere on the mailing list are some other mails regarding this problem. Until a new version of this patch can be found it is going to break nat support. If you don't need pptp-conntrack-nat support then go to built/scripts/config and edit the file patch-o-matic.exclude. Locate a line with #extra/pptp-conntrack-nat in it and remove the leading '#' to tell the patch-o-matic build script to ignore pptp-conntrack-nat support during build. At least this fixed the nat support for me ;-) Regards, Stefan Jasper Siepkes wrote: > Hi everybody, > > I'm new to Devil Linux; I checkout and compiled a fresh 1.2 release. The > only thing I modified was adding the new MPT fusion drivers, otherwise > none of the SAS controllers in HP Proliants work. > > After that I installed devil linux on a USB stick and booted it. It > works like a charm, except for iptables. When I try a simple NAT command > like: 'iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/24 -j > MASQUERADE' I get the dreaded 'iptables: Invalid argument' error. Which > suggests the module is out of sync with the userland utils. However, > since I compiled the whole thing from scrath, I dont see how this is > possible. > > The iptable_nat module is loaded and other iptable rules work, for as > far as I can tell its only the NAT table that misbehaves. > > Can anybody confirm this behavior ? Or am I just royally screwing > up ? :-) > > Kind regards, > > Jasper |