Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Vinod Chandran <vinod_chandran@multitech.co.in>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with Routing and Masquerading
Date: Wed, 31 May 2006 12:38:31 +0000	[thread overview]
Message-ID: <447D8B77.3060609@multitech.co.in> (raw)
In-Reply-To: <447C5773.3000608@multitech.co.in>

Hi,

Thanks Jason for the solution. With CONNMARK, I was able to route the 
packets properly.

Yeah, the problem was seen only for SSH sessions, I didnot see the 
problem with the Telnet and Ping sessions. TOS could be the answer to that.

The only change I had to do as far the CONNMARK solution was that in the 
PREROUTING chain, I had to add the rule with "-i eth0" where eth0 is my 
LAN, otherwise the return packets were not reaching the box in LAN.

Thanks and Regards,
Vinod C


Raj Mathur wrote:

>>>>>>"Jason" = Jason Boxman <jasonb@edseek.com> writes:
>>>>>>            
>>>>>>
>
>    Jason> Luciano Ruete wrote: <snip>
>    >> Besides that, you need to solve the problems that multipath
>    >> will arise, like TOS situation described above or route cache
>    >> expiration, that could made long term conns to be routed over a
>    >> new iface.  The solutions i know are CONNMARK(kernel>=2.6.12)
>    >> and julian's patches[1].  Personally i prefer CONNMARK.
>
>    Jason> Could you elaborate a little more on the CONNMARK method?
>
>I second that motion -- not too clear on the interaction between SNAT,
>multiple interfaces, multiple default routes and CONNMARK </aol
>mode="metoo">.  If someone could take out the time to make a complete
>example with (say) 2 outgoing interfaces, I promise a small GPL script
>in exchange which would automate the whole process.
>
>Actually the script's already made, but it doesn't use CONNMARK and
>suffers from the problems Jason describes and as documented in:
>
>  http://mailman.ds9a.nl/pipermail/lartc/2006q1/018220.html
>
>Regards,
>
>-- Raju
>  
>

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-05-31 12:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 14:44 [LARTC] Problems with Routing and Masquerading Vinod Chandran
2006-05-30 15:01 ` Erik Slagter
2006-05-30 15:13 ` Vinod Chandran
2006-05-30 16:13 ` Andrew Lyon
2006-05-30 16:15 ` Luciano Ruete
2006-05-30 16:18 ` Andrew Lyon
2006-05-30 16:23 ` Jason Boxman
2006-05-30 17:10 ` Luciano Ruete
2006-05-31  2:15 ` Raj Mathur
2006-05-31 12:38 ` Vinod Chandran [this message]
2006-05-31 15:52 ` Jason Boxman
2006-06-01  9:40 ` Vinod Chandran

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=447D8B77.3060609@multitech.co.in \
    --to=vinod_chandran@multitech.co.in \
    --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