From: Greg Wilson-Lindberg <gregw@spacex.net>
To: netfilter@vger.kernel.org
Subject: Multiple interfaces with the same IP address
Date: Wed, 7 Oct 2009 12:36:58 -0700 [thread overview]
Message-ID: <4ACCEDDA.9020508@spacex.net> (raw)
At this point I'm just asking for a direction to go to get the information that I need. While I've
been writing low level networking software for many years, I've never had to get into routing.
Here's my problem, we have an environment where we have a machine with one ethernet connection to
the wider network and a number of HDLC cards that connect to other embedded systems that we NAT out
to the ethernet WAN.
------------------------------
| (172.16.4.9/12) hdlc2|---------\
| | |
WAN 10.0.0.0/8 ----| eth0 (10.1.32.x/8) | |
| | |
| (172.16.4.9/12) hdlc1|------\ |
| | | |
| (172.16.4.9/12) hdlc0|---\ | |
------------------------------ | | |
| | |
| | |
machine1a-------------------| | |
(172.24.127.249) | | |
(172.16.129.9) | | |
| | |
machine2a-------------------| | |
(172.24.0.37) | | |
(172.16.129.17) | | |
| | |
machine3a-------------------| | |
(172.24.0.41) | | |
(172.16.129.25) ... | |
| |
machine1b----------------------| |
(172.24.127.250) | |
(172.16.129.9) | |
| |
machine2b----------------------| |
(172.24.0.38) | |
(172.16.129.18) | |
| |
machine3b----------------------| |
(172.24.0.42) | |
(172.16.129.26) ... |
|
machine1c-------------------------|
(172.24.127.251) |
(172.16.129.11) |
|
machine2c-------------------------|
(172.24.0.39) |
(172.16.129.19) |
|
machine3c-------------------------|
(172.24.0.43) |
(172.16.129.27) |
...
As can be seen from the above diagram, the addresses on the HDLC channels are not on separate
subnets. We also have some broadcast addresses that the machines on the HDLC nets will need to
receive. We do know all of the addresses for all of the machines on the HDLC nets, but we could end
up with as many as 30-50 on each net. Most of the packets coming from the ethernet WAN will go to
just one of the HDLC nets, but the broadcast packets will need to go to all of them. Also, the HDLC
nets do not need to be able to communicate between themselves.
Can anybody at least point me in the proper direction on how I need to attack this problem?
Thanks in advance,
Greg Wilson-Lindberg
next reply other threads:[~2009-10-07 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 19:36 Greg Wilson-Lindberg [this message]
2009-10-07 20:02 ` Multiple interfaces with the same IP address Rick Jones
2009-10-07 20:52 ` Greg Wilson-Lindberg
2009-10-07 21:15 ` Rick Jones
2009-10-07 21:21 ` Oskar Berggren
2009-10-07 21:57 ` Greg Wilson-Lindberg
2009-10-07 22:42 ` Rick Jones
2009-10-07 23:00 ` Greg Wilson-Lindberg
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=4ACCEDDA.9020508@spacex.net \
--to=gregw@spacex.net \
--cc=netfilter@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.