Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Gordan Bobic <lartc@bobich.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multihomed Masquerading, routing and iptables
Date: Mon, 05 Jan 2004 21:43:03 +0000	[thread overview]
Message-ID: <200401052143.03941.lartc@bobich.net> (raw)
In-Reply-To: <200312311649.36278.lartc@bobich.net>

On Monday 05 Jan 2004 8:32 pm, andybr wrote:
> Hi all,
>
> I dont understando what the problem is, can you explain
> so i can help you out.

2 interfaces, eth2 and eth3. ip rules ip route are set up correctly. 
Yet, for some reason, there are packets coming out of eth2 with the IP 
address of eth3 and vice versa. This seems to be related mainly to 
forwarded/NATed connections (which tend to break quite quickly). It is 
almost as if the connection tracking code in the kernel is broken.

I am not pretty certain it is a kernel bug in the shipping RH9 kernel. 
There was an update released today by RH, but I'm not holding much hope 
it will behave any differently. But it doesn't matter, as I have a 
fresh patched kernel that will hopefully work to try in a bit.

Thanks for the help.

Gordan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-01-05 21:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 16:49 [LARTC] Multihomed Masquerading, routing and iptables Gordan Bobic
2004-01-05  2:04 ` Rio Martin
2004-01-05  2:55 ` Rio Martin
2004-01-05 11:17 ` Gordan Bobic
2004-01-05 11:28 ` Artūras Šlajus
2004-01-05 11:54 ` Gordan Bobic
2004-01-05 12:06 ` Gordan Bobic
2004-01-05 20:32 ` andybr
2004-01-05 21:43 ` Gordan Bobic [this message]
2004-01-06  1:49 ` Rio Martin
2004-01-06  9:25 ` Gordan Bobic
2004-01-06 16:57 ` R. Steve McKown

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=200401052143.03941.lartc@bobich.net \
    --to=lartc@bobich.net \
    --cc=lartc@vger.kernel.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