All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gáspár Lajos" <swifty@freemail.hu>
To: Michael Robinson <mike@robinsonhome.org>
Cc: netfilter@vger.kernel.org
Subject: Re: Removing VLAN tag from outgoing broadcasts
Date: Wed, 19 Oct 2011 16:15:18 +0200	[thread overview]
Message-ID: <4E9EDB76.6080006@freemail.hu> (raw)
In-Reply-To: <CA+JOZmOF5ydmaAYSBcuU7ZQ8ZijCEV6bSL8uvaJFbmn9DP3=tA@mail.gmail.com>

Hi Mike,

> Thanks for the reply.  There is a native (untagged) VLAN on the trunk.
>   It's the eth2 interface.  So if I understand you correctly, I need to
> redirect the classified packets to the eth2 interface...is that
> correct?  How is that specified in a rule?  Note, that I'm just
> getting familiar with ebtables/iptables.
>

I think I was not clear enough... :D

So, if you send out the packets without any VLAN tags then they will not 
be seen on your tagged VLANs...

Imagine the whole VLAN thing as the following:
- You can slice up your real LAN to smaller VLANs.. :D
- You can connect to these networks with only ONE cable... (From the 
switch's pov: this is a port.)
- On the port there may be many tagged VLANs...
- And there may be AN untagged VLAN... (Forget about "General ports" !!!)
- If the port is "Access port" then it can only send/receive to one 
untagged VLAN (The tagging is managed internally by the switch.)
- If the port is "Trunk port" then you can do the tagging magic... One 
untagged and many tagged VLANs on this port...

So far this is what you have...
Now if you want to remove the tags then let the switch do the job for you...
(AFAIK the switch will remove/insert the specific VLAN id of the packets 
if the port is an Access port...)

I would do this:
port 1 (you) : Trunk port, VLAN 1 untagged, VLAN 2049 tagged, VLAN 2050 
tagged
port 2 (network 2049) : Access port, VLAN 2049 untagged
port 3 (network 2050) : Access port, VLAN 2050 untagged


Maybe you can find more info in the 4th message in this topic:
http://homecommunity.cisco.com/t5/Switches/access-general-or-trunk-Tagged-or-not-Getting-desperate/td-p/161352

Swifty

  reply	other threads:[~2011-10-19 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 19:16 Removing VLAN tag from outgoing broadcasts Michael Robinson
2011-10-19 13:20 ` Gáspár Lajos
2011-10-19 13:29   ` Michael Robinson
2011-10-19 14:15     ` Gáspár Lajos [this message]
2011-10-19 14:46       ` Michael Robinson
2011-10-19 15:23         ` Gáspár Lajos
2011-10-19 15:34           ` Michael Robinson

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=4E9EDB76.6080006@freemail.hu \
    --to=swifty@freemail.hu \
    --cc=mike@robinsonhome.org \
    --cc=netfilter@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 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.