From: Vinod Chandran <vinod_chandran@multitech.co.in>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems with Routing and Masquerading
Date: Tue, 30 May 2006 14:44:19 +0000 [thread overview]
Message-ID: <447C5773.3000608@multitech.co.in> (raw)
Hi,
I have a linux box which balances load between two interfaces ( say WAN1
and WAN2). I have masquerading on for any request coming from LAN to the
outside world.
The setup is in such a way that WAN1 drops packets with source ip
belonging to WAN2's network and viceversa.
For some strange reason, I find that packet coming out from the WAN
interface has source address of WAN2 and thereby getting dropped.
When I check the route cache , I find that for the same source and
destination, I have two route cache entries
192.168.52.66 192.168.26.73 192.168.19.76 0 0 0 eth1
192.168.52.66 192.168.26.73 192.168.20.25 i 0 0 23 eth2
Here 192.168.19.76 is the WAN1 gateway and 192.168.20.25 is WAN2
gateway, as we see the packets are going out through WAN2 , but the
masquerading has happened to the WAN1 IP address.
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.
Thanks and Regards,
Vinod C
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-05-30 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 14:44 Vinod Chandran [this message]
2006-05-30 15:01 ` [LARTC] Problems with Routing and Masquerading 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
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=447C5773.3000608@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.