From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Vlan classify
Date: Sun, 04 May 2003 19:03:08 +0000 [thread overview]
Message-ID: <marc-lartc-105207518420440@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105206146211403@msgid-missing>
Lars,
: I was wondering about splitting my Ethernet in different Vlan. But is
: there any functionality in iptables, or any other tools, witch I can
: use to match a specific Vlan? I was thinking about marking this packet
: and then classify it to a appropriate queue.
Lars--I haven't done much with VLANs under linux, however, my
understanding is that each VLAN appears as a separate interface. For
example, let's say device eth2 is connected to a VLAN capable switch, and
is reading two different VLAN tags, 4 and 7.
The interfaces available in this configuration with the vconfig tool would
be eth2.4 and eth2.7. Now, you should be able to use the names eth2.4 and
eth2.7 in your "tc filter" classification commands.
Again, I have not done this, so there may be oddities, but I would
recommend trawling the linux-vlan archives.
http://ns1.wanfear.com/pipermail/vlan/
According to Ben Greear, the VLAN code works fine with bridging, so I
can't imagine that it would have a problem with traffic control....so try
it out and let the list know.
: Another question is:
: How many packages can a ordinary pfifo queue hold??
: Say, packets that are used are full Ethernet frame.
The pfifo_fast qdisc has a txqueuelen (qlen) of 100 by default on all
systems I have checked. Your system may vary. You may alter the queue
length with either the "ifconfig" command or the "ip link" command.
# ip link show dev eth2
4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:ba:a4:4a:15 brd ff:ff:ff:ff:ff:ff
# ip link set dev eth2 qlen 50
# ip link show dev eth2
4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 50
link/ether 00:50:ba:a4:4a:15 brd ff:ff:ff:ff:ff:ff
# ifconfig eth2 txqueuelen 80
# ip link show dev eth2
4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 80
link/ether 00:50:ba:a4:4a:15 brd ff:ff:ff:ff:ff:ff
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-04 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 15:06 [LARTC] Vlan classify Lars Landmark
2003-05-04 19:03 ` Martin A. Brown [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=marc-lartc-105207518420440@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@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.