From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] multiple gateway problem
Date: Tue, 04 Dec 2001 21:31:26 +0000 [thread overview]
Message-ID: <marc-lartc-100750154715281@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100740321228322@msgid-missing>
Ross,
The diagram really helps. My guess is what you need to do is put a second
address on eth0, and then differentiate your packets according to which
address they have arrived at on the Linux box - for example, 10.4.44.11 or
10.4.44.12.
And yeah, there should be a way to do it by MAC address, but this should be
simpler.
Whit
On Tue, Dec 04, 2001 at 02:11:37PM -0800, Ross Simpson wrote:
> First off, here's a diagram:
>
>
> I N T E R N E T
> / \
> ------------- -------------
> | 10.4.44.1 | | 10.4.44.2 |
> | lucent | | speed |
> ------------- -------------
> port-fw 80 port-fw 80
> \ /
> \ /
> \ /
> -----------
> | hub |
> -----------
> |
> |
> |
> |
> eth0
> --------------
> | 10.4.44.11 |
> | linux |
> --------------
>
> I have a default gateway as specified in /etc/sysconfig/network:
> GATEWAYDEV=eth0
> GATEWAY\x10.4.44.1
>
> I ran the below commands to use multiple default gateways.
>
> So here's what I would _like_ to see:
> Traffic coming to the box from the internal network uses the default route
> from /etc/sysconfig/network.
> Traffic coming from the internet (from the 10.4.44.1 router, then
> port-forwarded 10.4.44.11) should use 10.4.44.1 as the gateway to return the
> packets to the client.
> 10.4.44.2 should work identically to 10.4.44.1.
>
> Right now, traffic coming from the system default gateway works great.
> Traffic coming from 10.4.44.2 gets to the system, however I would guess that
> it's being sent back to 10.4.44.1 as it is the default gateway.
>
> As I'm watching a tcpdump, I see that packets are coming in with their
> original (external) IP addresses, instead of the address of the router (I
> was thinking that port forwarding temporarily changed the source IP of the
> packet; apparently not). So the setup is not working because external IPs
> don't match 10.4.44.1 or 10.4.44.2, and the system's default gateway is
> used.
>
> So, I guess my question becomes: is there any way for linux to tell which
> router the packet came from? Could it tell maybe by mac address?
>
> Thanks for the help!
> Ross
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-12-04 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 18:13 [LARTC] multiple gateway problem Ross Simpson
2001-12-04 14:48 ` Jorge Castellet
2001-12-04 17:54 ` Whit Blauvelt
2001-12-04 21:09 ` Ross Simpson
2001-12-04 21:31 ` Whit Blauvelt [this message]
2001-12-05 7:14 ` Kristian Hoffmann
2001-12-06 17:13 ` Ross Simpson
2001-12-06 17:44 ` Whit Blauvelt
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=marc-lartc-100750154715281@msgid-missing \
--to=whit@transpect.com \
--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.