All of lore.kernel.org
 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: Tue, 30 May 2006 15:13:20 +0000	[thread overview]
Message-ID: <447C5E40.1080008@multitech.co.in> (raw)
In-Reply-To: <447C5773.3000608@multitech.co.in>

Hi Erik,

Ip route get returns
192.168.26.73 via 192.168.19.76 dev eth1  src 192.168.19.29
    cache  mtu 1500 advmss 1460

Here too it gives me WAN1s IP address which is the same as the 
masqueraded one, but the packets are seen going out through WAN2.

Thanks and Regards,
Vinod C


Erik Slagter wrote:

>On Tue, 2006-05-30 at 20:02 +0530, Vinod Chandran wrote:
>  
>
>>It seems to me that the root of the problem is the creation of the two 
>>cache entries. Any idea why this happens, and how it can be avoided.
>>    
>>
>
>What does "ip route get" say? I think this tool will be the key to the
>solution, look at the "src address".
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>  
>

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

  parent reply	other threads:[~2006-05-30 15:13 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 [this message]
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
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=447C5E40.1080008@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 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.