From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "Štefan Sakalík" <rabbit6440@gmail.com>, netdev@vger.kernel.org
Subject: Re: Devices with colon in name (iproute2 bug)
Date: Thu, 18 Nov 2010 15:09:41 +0100 [thread overview]
Message-ID: <1290089381.2781.139.camel@edumazet-laptop> (raw)
In-Reply-To: <1290086705.3818.63.camel@localhost>
Le jeudi 18 novembre 2010 à 13:25 +0000, Ben Hutchings a écrit :
> Linux originally only supported one address per address-family per
> interface. Additional addresses had to be assigned to 'alias
> interfaces' which were named <base-interface>:<index>. For backward
> compatibility, colons in interface names are reserved for this purpose.
> If you can create regular interfaces with colons in their names, this
> seems to be a kernel bug.
Yes
Speaking of kernel bug, many devices dont set operstate, while they
really are UP
-> UNKNOWN
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:21:70:b0:e4:89 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:23:4e:1a:49:2d brd ff:ff:ff:ff:ff:ff
4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 3e:42:f7:21:de:e2 brd ff:ff:ff:ff:ff:ff
6: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
7: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 3
link/ppp
prev parent reply other threads:[~2010-11-18 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 12:14 Devices with colon in name (iproute2 bug) Štefan Sakalík
2010-11-18 13:25 ` Ben Hutchings
2010-11-18 14:09 ` Eric Dumazet [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=1290089381.2781.139.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=rabbit6440@gmail.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