From: Roman <maillists@gmx.ch>
To: netfilter@lists.netfilter.org
Subject: Re: Re: Firewall with only one eth0 device: possible?
Date: Wed, 01 Jun 2005 17:13:25 +0200 [thread overview]
Message-ID: <429DD095.6020108@gmx.ch> (raw)
Thanks for the hint, Grant
I found some documentation on that in the datasheet of realtek 8309
switch controller and on a support page of zyxel.
The realtek datasheet says that there are 4 tag/untag modes in that chip
but does not tell you when the tagging or untagging is done (ingress or
egress?)
On zyxel support page was stated that tagging will be done on ingress an
untagging on egress if any tag changing is done at all. The zyxel
approach sound good to me.
I hope all switch conntroller manufacturer implemented the IEEE 802.1q
standard the same way. I do not know how much freedom there is the
interpret 802.1q in different ways.
Do you or someone know what happens if tagged ethernet frames leave the
switch ports A (VLAN1) and C (VLAN2, port B was the path to the uClinux
eth0.1 /eth0.2) and VLAN unaware clients are hooked to this network
segment? Will they cope with the VLAN frames and understand them? Or
will they confuse the unaware devices and get dropped?
Thanks for any further advice
Roman
next reply other threads:[~2005-06-01 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 15:13 Roman [this message]
2005-06-01 15:28 ` Firewall with only one eth0 device: possible? Taylor, Grant
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=429DD095.6020108@gmx.ch \
--to=maillists@gmx.ch \
--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 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.