Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Aseem Rastogi <aseem@india.tejasnetworks.com>
To: Marc Haber <mh+netfilter@zugschlus.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: Iptables and vlan interfaces
Date: Mon, 03 Oct 2005 14:25:11 +0530	[thread overview]
Message-ID: <4340F1EF.3010000@india.tejasnetworks.com> (raw)
In-Reply-To: 20051003074444.GA27873@torres.l21.ma.zugschlus.de

i understand vlans. but how is a vlan network interface different from a 
normal eth interface as far as higher layer protocols are concerned? or 
for that matter of fact how is this different from even l2 perspective. 
only difference is the broadcast domain. right ?

also, if somebody can give me an example of ifconfig output for vlan 
interface, that will be helpful.

thanks.

Marc Haber wrote:

>On Mon, Oct 03, 2005 at 12:18:11PM +0530, Aseem Rastogi wrote:
>
>>i have been following this post rather keenly. it now seems to have died 
>>down. but still i am not able to understand what is a vlan interface. 
>>can somebody please give me some pointer where i can read about this. 
>>vlan i thought is a l2 concept and should have nothing to do with l3.
>>
>
>http://en.wikipedia.org/wiki/Vlan might be a good start.
>
>While VLANs are basically a layer 2 concept, you somehow need to reach
>them from upper layers. This is accomplished by having "virtual
>interfaces" which are "connected" to the VLAN and feel just like a
>physical interface on a physical LAN from the software side.
>
>Greetings
>Marc
>


-- 
The end is always good. If it's not good, it's not the end.





  reply	other threads:[~2005-10-03  8:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 11:21 Iptables and vlan interfaces sebastian.ionita
2005-09-30 11:34 ` Sascha Reissner
2005-09-30 11:37   ` Marc Haber
2005-09-30 11:56   ` Marcin Giedz
2005-09-30 12:44 ` Henrik Nordstrom
2005-09-30 12:54   ` sebastian.ionita
2005-09-30 13:39     ` /dev/rob0
2005-09-30 13:41       ` Marc Haber
2005-09-30 13:55         ` /dev/rob0
2005-09-30 14:14           ` Marc Haber
2005-09-30 15:21       ` Henrik Nordstrom
2005-10-03  6:48         ` Aseem Rastogi
2005-10-03  7:44           ` Marc Haber
2005-10-03  8:55             ` Aseem Rastogi [this message]
2005-10-03  8:59               ` Marc Haber
2005-10-03  9:16           ` Henrik Nordstrom
2005-10-03  9:24             ` Marc Haber
2005-10-03 12:46               ` Henrik Nordstrom
2005-10-03  9:27             ` Aseem Rastogi
2005-10-03 10:05             ` Aseem Rastogi
2005-10-03 10:02               ` Marc Haber
2005-10-03 12:18               ` Henrik Nordstrom
  -- strict thread matches above, loose matches on Subject: below --
2005-09-30 12:04 Baake, Matthias
2005-09-30 12:53 Baake, Matthias

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=4340F1EF.3010000@india.tejasnetworks.com \
    --to=aseem@india.tejasnetworks.com \
    --cc=mh+netfilter@zugschlus.de \
    --cc=netfilter@lists.netfilter.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