From: Rick Jones <rick.jones2@hp.com>
To: Greg Wilson-Lindberg <gwilson@spacex.com>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Multiple interfaces with the same IP address
Date: Wed, 07 Oct 2009 15:42:09 -0700 [thread overview]
Message-ID: <4ACD1941.8000805@hp.com> (raw)
In-Reply-To: <4ACD0ED9.10601@spacex.com>
Greg Wilson-Lindberg wrote:
> Ok, I can use route to add the various IP addresses that are on each
> HDLC channel to the routing tables. There are a lot of machines, but
> because the addresses are well known/formatted, generating the scripts
> automatically won't be to bad. But how do I handle broadcast addresses
> such as 172.16.255.255, 172.16.128.255, or 172.16.129.15 that need to go
> out all of the HDLC channels?
How are those going to appear on the gateway's 10net interface in the first
place? I thought stuff like "directed broadcast" was verboten these days and
essentially unsupported by any stack. That is why I was asking if these were to
be broadcasts or perhaps IP multicasts - where IP multicasts *can* and do get
routed.
Please don't take this the wrong way, but on the surface, the setup you've
described sounds terribly kludged and so very brittle, and given the domain of
your email and a bit of reader imagination that is, well, troubling :)
rick jones
>
> Oskar Berggren wrote:
>
>> 2009/10/7 Rick Jones <rick.jones2@hp.com>:
>>
>>> Greg Wilson-Lindberg wrote:
>>>
>>>> Rick Jones wrote:
>>>> ...
>>>>
>>
>>> I have not fully parsed the manpage for the ip command, but it does have
>>> tidbits which suggest being able to specify interfaces by name when
>>> manipulating routing tables. If that is correct you should be able
>>> to add
>>> specific host routes pointing-out specific interface names if you are
>>> indeed
>>> forced to put assign the same IP address to each of the HCLC
>>> interfaces on
>>> the "gateway."
>>>
>>
>> Yes,
>>
>> ip route add x.x.x.x/x dev eth1
>>
>> or similar works fine.
>>
>> If you like, you can also use ip addr add x.x.x.x/32 dev eth1 to set
>> an ip-address without having the kernel automatically install a subnet
>> route. Then manage the routing tables complete by yourself.
>>
>> /Oskar
>> --
>> To unsubscribe from this list: send the line "unsubscribe netfilter" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-07 22:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 19:36 Multiple interfaces with the same IP address Greg Wilson-Lindberg
2009-10-07 20:02 ` 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 [this message]
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=4ACD1941.8000805@hp.com \
--to=rick.jones2@hp.com \
--cc=gwilson@spacex.com \
--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.