From: Robin Farine <acnrf@dial.eunet.ch>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] IP limited broadcasts problems
Date: Mon, 21 May 2001 01:45:00 -0000 [thread overview]
Message-ID: <86snhzozut.fsf@halftrack.hq.acn-group.ch> (raw)
In-Reply-To: <20010521101534.B4729@biferten.ma.tech.ascom.ch>
Andrew Lunn <andrew.lunn@ascom.ch> writes:
> On Sat, May 19, 2001 at 06:54:41PM +0200, Robin Farine wrote:
> > It seems to me that the OpenBSD IP stack does not handle correctly
> > IP limited broadcasts. Take a host with N Ethernet interfaces, each
> > with an IP address on a separate IP subnet and with the flag
> > IFF_BROADCAST set. The host sends an IP limited broadcast. I would
> > expect that an Ethernet broadcast goes out of each interface
> > (provided that a route to the interface's specific IP subnet exists
> > for each interface).
>
> > Did someone already observed & reported this problem or should I
> > rather go to sleep, and then read TCP/IP Illustrated again?
>
> Good morning Robin, Hope you slept well.
Not too bad and, after 3 pages of TCP/IP Illustrated, I fell asleep again so
...
>
> I just checked the Internet STD documents to see if this is broken according
> to the standards. Best i could find was, in std3, "Requirements for Internet
> Hosts"
>
> There has been discussion on whether a datagram addressed
> to the Limited Broadcast address ought to be sent from all
> the interfaces of a multihomed host. This specification
> takes no stand on the issue.
>
> So it seems this falls into one of those gray areas.
>
> You probably want to swap mailing lists and post to an OpenBSD
> list.
Not required, the stack clearly conforms to the grey area.
> It may also be worth looking at an OpenBSD application that uses Limited
> broadcasts. rwhod should be a simple example, or DHCP server for something
> more complex.
I bet that such services work only on host with one interface. On Linux, they
have added a feature that lets an application bind a socket to a specific
interface for this purpose. It seems that the OpenBSD stack does not include
anything like this. Bad news for our DHCP relay!
Robin
prev parent reply other threads:[~2001-05-21 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 9:54 Robin Farine
2001-05-21 1:15 ` Andrew Lunn
2001-05-21 1:45 ` Robin Farine [this message]
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=86snhzozut.fsf@halftrack.hq.acn-group.ch \
--to=acnrf@dial.eunet.ch \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-discuss@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).