From: Vimal <j.vimal@gmail.com>
To: netfilter@vger.kernel.org
Subject: Behaving like a switch
Date: Fri, 12 Sep 2008 15:29:31 +0530 [thread overview]
Message-ID: <ff71fbf20809120259w49dd28b5xc0912893f7f7e8d9@mail.gmail.com> (raw)
Hello,
I am running Mac OS X Leopard. I would like to perform some
experiments by behaving like a switch. This is the current setup:
[My Laptop] <-----> [Switch] <===(part of a vlan)===>
The switch port to which I am connected to is on a particular vlan.
However, if trunking is enabled on my port, I can see all vlan
traffic.
I would like to configure my laptop so that the default ethernet
device (en0) would be connected to a switch via a trunk line, and all
packets that leave my computer via en0 of a specific type (say, only
ipv6 packets) should be tagged with another vlan-id. The setup should
be such that bidirectional communication is possible.
I have seen that one can setup a vlan virtual device using ifconfig.
But I am unable to setup the policy by which packets are appropriately
forwarded.
Thanks,
--
Vimal
next reply other threads:[~2008-09-12 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 9:59 Vimal [this message]
2008-09-12 15:15 ` Behaving like a switch Grant Taylor
2008-09-12 15:54 ` Vimal
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=ff71fbf20809120259w49dd28b5xc0912893f7f7e8d9@mail.gmail.com \
--to=j.vimal@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox