From: Stephen Hemminger <shemminger@linux-foundation.org>
To: sunil saraff <sunil_007_xxx@yahoo.co.in>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Regarding default vlan
Date: Thu, 19 Nov 2009 21:43:23 -0800 [thread overview]
Message-ID: <20091119214323.365d5580@nehalam> (raw)
In-Reply-To: <959514.14125.qm@web8705.mail.in.yahoo.com>
On Fri, 20 Nov 2009 09:08:38 +0530 (IST)
sunil saraff <sunil_007_xxx@yahoo.co.in> wrote:
>
> Hello,
>
> I have two vlan’s configured on my switch port i.e 246 & 247. 247 is a tagged vlan and 246 is the untagged vlan(native vlan).When I create a virtual vlan interface with tagged vlan 247 using vconfig(eth0.247) it works fine. If I create a virtual vlan interface with untagged vlan 246 using vconfig(eth0.246) I see a different behaviour.
>
> My configuration
>
> Ifconfig eth0 0.0.0.0 up
> Vconfig add eth0 246
> Ifconfig eth0.246 192.168.246.3 netmask 255.255.255.0 up
> Route add default gw 192.168.246.1
>
>
> The packet that goes out from the linux box is tagged with 246 vlan but the replies are untagged(as it is the native vlan). So these untagged packets are not accepted by linux box. So, can you suggest me a way in which I can configure my linux box so that the untagged packets for default vlan are accepted?Can bridging be done on eth0(untagged interface) and eth0.246(tagged interface)?
>
> Thanks,
> Sunil
This is not a bridging question, it is a vlan question.
So post it to linux-net@vger.kernel.org
I don't see 247 anywhere in your config?
P.s: the ifconfig/vconfig/route commands are old. Use ip command instead.
prev parent reply other threads:[~2009-11-20 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 3:38 [Bridge] Regarding default vlan sunil saraff
2009-11-20 5:43 ` Stephen Hemminger [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=20091119214323.365d5580@nehalam \
--to=shemminger@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=sunil_007_xxx@yahoo.co.in \
/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