From: Patrick McHardy <kaber@trash.net>
To: linux@arcoscom.com
Cc: lartc@mailman.ds9a.nl,
l7-filter-developers@lists.sourceforge.net,
netfilter-devel@lists.netfilter.org
Subject: [LARTC] Re: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues
Date: Tue, 12 Dec 2006 08:34:31 +0000 [thread overview]
Message-ID: <457E6997.1050001@trash.net> (raw)
In-Reply-To: <57631.195.55.244.106.1165911878.squirrel@www.arcoscom.com>
ArcosCom Linux User wrote:
> El Lun, 11 de Diciembre de 2006, 20:44, ArcosCom Linux User escribió:
>
>>Hi, I'm having problems with this configuration:
>> iptables 1.3.7 (vanilla or repackaged for fc5)
>> kernel 2.6.19 (vanilla)
>> ROUTE 1.11 (last pom-ng)
>> layer7-filter 2.6 (last in sf.net)
>> connlimit (last pom-ng)
>>
>>When I try to use -j ROUTE in any chain in mangle table I have this error:
>>
>>[root@myhost ~]# iptables -v -t mangle -A POSTROUTING -p tcp --dport msnp
>>-j ROUTE --gw $chat_gw
>>ROUTE tcp opt -- in * out * 0.0.0.0/0 -> 0.0.0.0/0 tcp dpt:1863 ROUTE
>>gw:80.32.61.1
>>iptables: Invalid argument
>>
>>[root@myhost ~]# dmesg | grep "ROUTE"
>>ipt_ROUTE: targinfosize 0 != 40
The ROUTE target needs to set the targetsize field in struct ipt_target.
It probably needs other adjustments for 2.6.19 as well. I would just use
normal policy routing ..
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: linux@arcoscom.com
Cc: lartc@mailman.ds9a.nl,
l7-filter-developers@lists.sourceforge.net,
netfilter-devel@lists.netfilter.org
Subject: Re: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues
Date: Tue, 12 Dec 2006 09:34:31 +0100 [thread overview]
Message-ID: <457E6997.1050001@trash.net> (raw)
In-Reply-To: <57631.195.55.244.106.1165911878.squirrel@www.arcoscom.com>
ArcosCom Linux User wrote:
> El Lun, 11 de Diciembre de 2006, 20:44, ArcosCom Linux User escribió:
>
>>Hi, I'm having problems with this configuration:
>> iptables 1.3.7 (vanilla or repackaged for fc5)
>> kernel 2.6.19 (vanilla)
>> ROUTE 1.11 (last pom-ng)
>> layer7-filter 2.6 (last in sf.net)
>> connlimit (last pom-ng)
>>
>>When I try to use -j ROUTE in any chain in mangle table I have this error:
>>
>>[root@myhost ~]# iptables -v -t mangle -A POSTROUTING -p tcp --dport msnp
>>-j ROUTE --gw $chat_gw
>>ROUTE tcp opt -- in * out * 0.0.0.0/0 -> 0.0.0.0/0 tcp dpt:1863 ROUTE
>>gw:80.32.61.1
>>iptables: Invalid argument
>>
>>[root@myhost ~]# dmesg | grep "ROUTE"
>>ipt_ROUTE: targinfosize 0 != 40
The ROUTE target needs to set the targetsize field in struct ipt_target.
It probably needs other adjustments for 2.6.19 as well. I would just use
normal policy routing ..
next prev parent reply other threads:[~2006-12-12 8:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 19:44 [LARTC] iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues ArcosCom Linux User
2006-12-11 19:44 ` ArcosCom Linux User
2006-12-12 8:24 ` [LARTC] " ArcosCom Linux User
2006-12-12 8:24 ` ArcosCom Linux User
2006-12-12 8:33 ` Lutz Jaenicke
2006-12-12 8:34 ` Patrick McHardy [this message]
2006-12-12 8:34 ` Patrick McHardy
2006-12-13 8:31 ` [LARTC] " ArcosCom Linux User
2006-12-13 8:31 ` ArcosCom Linux User
2006-12-13 8:38 ` [LARTC] " Patrick McHardy
2006-12-13 8:38 ` Patrick McHardy
2006-12-13 9:12 ` [LARTC] " ArcosCom Linux User
2006-12-13 9:12 ` ArcosCom Linux User
2006-12-13 9:17 ` [LARTC] " Patrick McHardy
2006-12-13 9:17 ` Patrick McHardy
2006-12-13 11:00 ` Jan Engelhardt
2006-12-13 10:56 ` Jan Engelhardt
2006-12-28 21:10 ` Krzysztof Oledzki
2007-01-10 5:58 ` [LARTC] " Patrick McHardy
2007-01-10 5:58 ` Patrick McHardy
2007-01-10 11:53 ` Jan Engelhardt
2007-01-10 12:53 ` [LARTC] " Patrick McHardy
2007-01-10 12:53 ` Patrick McHardy
2007-01-10 13:15 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, ArcosCom Linux User
2007-01-10 13:15 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] ArcosCom Linux User
2007-01-10 14:08 ` Jan Engelhardt
2007-01-10 13:21 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, ArcosCom Linux User
2007-01-10 13:21 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] ArcosCom Linux User
2007-01-25 17:41 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-01-25 17:41 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley
2007-01-31 2:58 ` [LARTC] " Pablo Neira Ayuso
2007-02-09 13:37 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-02-09 13:37 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley
2007-02-09 16:57 ` Krzysztof Oledzki
2007-02-09 17:03 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, kernel Patrick McHardy
2007-02-09 17:03 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Patrick McHardy
2007-02-09 17:30 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-02-09 17:30 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457E6997.1050001@trash.net \
--to=kaber@trash.net \
--cc=l7-filter-developers@lists.sourceforge.net \
--cc=lartc@mailman.ds9a.nl \
--cc=linux@arcoscom.com \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.