From: Seth David Schoen <schoen@loyalty.org>
To: John Gilmore <gnu@toad.com>
Cc: Florian Weimer <fw@deneb.enyo.de>, linux-man@vger.kernel.org
Subject: Re: [PATCH 1/1] ip.7: Add "special and reserved addresses" section
Date: Fri, 26 Mar 2021 17:22:02 -0700 [thread overview]
Message-ID: <20210327002202.GC10062@frotz.zork.net> (raw)
In-Reply-To: <23508.1616802338@hop.toad.com>
John Gilmore writes:
> > > > Are there network devices that are neither point-to-point, nor do they
> > > > have broadcast support?
>
> It seems to me that cellular radio systems are neither point-to-point,
> nor do they support broadcast. And they keep moving further and further
> toward being IP-based (e.g. phone calls on your LTE phone use SIP over
> UDP over IP over cellular!). But given the proprietary nature of most
> cellphone radio chips and their firmware, it's possible that Linux has
> never built a fully capable network interface to talk to them. I don't
> think we should attempt to rule it out, though.
I found in include/uapi/linux/if_link.h the following classification
about this:
IFF_LOOPBACK, IFF_BROADCAST and IFF_POINTOPOINT are
more not changeable by user. They describe link media
characteristics and set by device driver.
Comments:
- Combination IFF_BROADCAST|IFF_POINTOPOINT is invalid
- If neither of these three flags are set;
the interface is NBMA.
https://en.wikipedia.org/wiki/Non-broadcast_multiple-access_network
The likeliest example there in terms of running IP directly over such a
network would presumably be ATM, which had a whole series of RFCs about
how to make this work, and which is supported by the Linux kernel (e.g.
net/atm/clip.c, for "Classical IP over ATM" following RFC 1577). That
includes, for example, a non-broadcast-based ARP mechanism!
I'll try to figure out what a Linux ATM interface does about IP broadcasts.
It seems like the RFC 1577 instruction is to still allow IP broadcasts
but accept that they won't be mapped onto link-layer broadcasts:
ATM does not support broadcast addressing, therefore there are no
mappings available from IP broadcast addresses to ATM broadcast
services. Note: this lack of mapping does not restrict members from
transmitting or receiving IP datagrams specifying any of the four
standard IP broadcast address forms as described in [8]. Members,
upon receiving an IP broadcast or IP subnet broadcast for their LIS,
MUST process the packet as if addressed to that station.
In other IP-over-ATM methods it appears that broadcasting is emulated by
a lower layer.
https://www.cse.wustl.edu/~jain/cis788-97/ftp/ip_over_atm/index.html#3
next prev parent reply other threads:[~2021-03-27 0:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 0:20 [PATCH 1/1] ip.7: Add "special and reserved addresses" section Seth David Schoen
2021-03-20 19:49 ` Florian Weimer
2021-03-22 17:58 ` Seth David Schoen
2021-03-22 21:29 ` Seth David Schoen
2021-03-24 7:07 ` John Gilmore
2021-03-24 8:26 ` Florian Weimer
2021-03-24 19:18 ` Seth David Schoen
2021-03-26 22:53 ` Seth David Schoen
2021-03-26 23:45 ` John Gilmore
2021-03-27 0:22 ` Seth David Schoen [this message]
2021-03-30 3:21 ` [PATCH v2] " Seth David Schoen
2021-05-06 2:37 ` [RESEND PATCH " Seth David Schoen
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=20210327002202.GC10062@frotz.zork.net \
--to=schoen@loyalty.org \
--cc=fw@deneb.enyo.de \
--cc=gnu@toad.com \
--cc=linux-man@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox