From: snpe <snpe@snpe.co.yu>
To: Wilmer van der Gaast <lintux@lintux.cx>,
Patrick McHardy <kaber@trash.net>
Cc: linux-kernel@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: 2.4.23 masquerading broken?
Date: Tue, 2 Dec 2003 20:18:03 +0000 [thread overview]
Message-ID: <200312022018.03078.snpe@snpe.co.yu> (raw)
In-Reply-To: <20031202173358.GK615@gaast.net>
It work for me
(2.4.23 with linux abi, gcc 3.2 from RedHat 8.0 - netfilter like modules)
regards
Haris Peco
On Tuesday 02 December 2003 05:33 pm, Wilmer van der Gaast wrote:
> Patrick McHardy (kaber@trash.net) wrote:
> > Can you check the ringbuffer for error messages ? What happens
> > to the packets when masquerading fails ?
>
> Hmm. Damn, forgot about the syslogs completely. :-(
>
> Dec 2 16:42:30 tosca kernel: MASQUERADE: Route sent us somewhere else.
> Dec 2 16:42:44 tosca last message repeated 11 times
> Dec 2 16:42:47 tosca kernel: NET: 1 messages suppressed.
> Dec 2 16:42:47 tosca kernel: MASQUERADE: Route sent us somewhere else.
> Dec 2 16:42:51 tosca kernel: NET: 5 messages suppressed.
> Dec 2 16:42:51 tosca kernel: MASQUERADE: Route sent us somewhere else.
> Dec 2 16:42:57 tosca kernel: NET: 4 messages suppressed.
> Dec 2 16:42:57 tosca kernel: MASQUERADE: Route sent us somewhere else.
>
> And, well, it goes on like that. dmesg is full of messages like this.
>
> The packages seem to get lost completely. At least I don't see them
> going out on eth1 (where they should go to).
>
>
> Wilmer van der Gaast.
next prev parent reply other threads:[~2003-12-02 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 16:56 2.4.23 masquerading broken? Wilmer van der Gaast
2003-12-02 17:25 ` Patrick McHardy
2003-12-02 17:33 ` Wilmer van der Gaast
2003-12-02 20:18 ` snpe [this message]
2003-12-02 23:32 ` Patrick McHardy
2003-12-03 0:45 ` Wilmer van der Gaast
2004-01-10 21:59 ` Harald Welte
2004-01-11 10:40 ` Patrick McHardy
2004-01-11 12:08 ` Patrick McHardy
2003-12-03 10:30 ` 2.4.23 masquerading broken? key.oif = 0; perhaps in bad position ? Zoran Davidovac
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=200312022018.03078.snpe@snpe.co.yu \
--to=snpe@snpe.co.yu \
--cc=kaber@trash.net \
--cc=lintux@lintux.cx \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox