From: Patrick McHardy <kaber@trash.net>
To: Gil Beniamini <gil.beniamini@gmail.com>
Cc: Brent Cook <bcook@bpointsys.com>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: SOCK_RAW does not receive broadcast (with VLAN unless PROMISC)
Date: Wed, 10 Jun 2009 17:00:10 +0200 [thread overview]
Message-ID: <4A2FCA7A.60707@trash.net> (raw)
In-Reply-To: <91ac27070906100748p1b2cb6bax56ecc230e556ae96@mail.gmail.com>
Gil Beniamini wrote:
> Dear Patrick,
> Below is my try to add vlan-id 24 on eth1, followed by "ip -d link list":
> root@StudentsHPA:/home/hpa# vconfig add eth1 24
> ERROR: trying to add VLAN #24 to IF -:eth1:- error: File exists
>
> 5: vlan24@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue state UP
You're apparently using the "VLAN_NAME_TYPE_PLUS_VID_NO_PAD" naming
policy, which causes name clashes when you create two VLANs with the
same ID.
I'd suggest to use iproute to create the devices, which allows you to
specify the desired name manually. Alternatively you can use vconfig
and a different naming policy.
next prev parent reply other threads:[~2009-06-10 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91ac27070906081105x30171bedra10d244d382a6934@mail.gmail.com>
2009-06-08 21:34 ` SOCK_RAW does not receive broadcast (with VLAN unless PROMISC) David Miller
2009-06-09 10:59 ` Patrick McHardy
2009-06-09 11:27 ` Gil Beniamini
2009-06-09 11:40 ` Patrick McHardy
2009-06-09 13:08 ` Gil Beniamini
2009-06-09 13:14 ` Patrick McHardy
2009-06-09 19:30 ` Brent Cook
2009-06-10 14:24 ` Gil Beniamini
2009-06-10 14:32 ` Patrick McHardy
2009-06-10 14:48 ` Gil Beniamini
2009-06-10 15:00 ` Patrick McHardy [this message]
[not found] ` <20090610170108.7710c64b@tux.DEF.witbe.net>
2009-06-10 15:29 ` Gil Beniamini
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=4A2FCA7A.60707@trash.net \
--to=kaber@trash.net \
--cc=bcook@bpointsys.com \
--cc=davem@davemloft.net \
--cc=gil.beniamini@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).