From: Ben Hutchings <bhutchings@solarflare.com>
To: "Štefan Sakalík" <rabbit6440@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Devices with colon in name (iproute2 bug)
Date: Thu, 18 Nov 2010 13:25:05 +0000 [thread overview]
Message-ID: <1290086705.3818.63.camel@localhost> (raw)
In-Reply-To: <AANLkTimw7=zS8YNptNNP9YR0v93EwctBvsG58a4z+Y-M@mail.gmail.com>
On Thu, 2010-11-18 at 13:14 +0100, Štefan Sakalík wrote:
> Hi,
> When I add a device with colon via ip (from git 3f5c1a01):
> ip link add dev 'a:b' type dummy
> then ip link show dev 'a:b' returns
> 12: a:b: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN
> ioctl(SIOCGIFXQLEN) failed: No such device
>
> link/ether 9e:44:b4:ec:77:f1 brd ff:ff:ff:ff:ff:ff
>
> Also ifconfig from net-tools returns
> a: error fetching interface information: Device not found
> but I guess it's obsolete.
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.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-11-18 13:25 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 [this message]
2010-11-18 14:09 ` Eric Dumazet
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=1290086705.3818.63.camel@localhost \
--to=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 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.