From: John Haxby <john.haxby@oracle.com>
To: Jonathan Tripathy <jonnyt@abpni.co.uk>
Cc: netfilter@vger.kernel.org
Subject: Re: VLANs
Date: Tue, 11 Jan 2011 12:48:19 +0000 [thread overview]
Message-ID: <4D2C5193.6010703@oracle.com> (raw)
In-Reply-To: <4D2C4C13.3020107@abpni.co.uk>
On 11/01/11 12:24, Jonathan Tripathy wrote:
>
> For seeing what I mean about VLAN hopping:
>
> http://en.wikipedia.org/wiki/VLAN_hopping
Ahh. That's interesting, but not nearly so interesting (or useful) as
the Cisco document that it cites:
http://www.cisco.com/en/US/products/hw/switches/ps708/products_white_paper09186a008013159f.shtml#wp39054
Basically the hopping only works if the trunk has the same native vlan
as the attacker. This, the cisco article goes on to say, is considered
to be a misconfiguration. You can read it yourself, but there are two
ways of avoiding this.
It's still not clear to me how you would get a reply from the attack --
you'd need something on the receiving end that can also do the double
tagging (which is not 802.1ad, it's a second 802.1a tag, to be clear).
jch
next prev parent reply other threads:[~2011-01-11 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 17:42 VLANs Jonathan Tripathy
2011-01-10 21:33 ` VLANs John Haxby
2011-01-10 22:15 ` VLANs Jonathan Tripathy
2011-01-11 8:19 ` VLANs Thomas Berg
2011-01-11 10:26 ` VLANs Jonathan Tripathy
2011-01-11 10:42 ` VLANs John Haxby
2011-01-11 10:57 ` VLANs Jonathan Tripathy
[not found] ` <4D2C47DB.10702@oracle.com>
2011-01-11 12:24 ` VLANs Jonathan Tripathy
2011-01-11 12:48 ` John Haxby [this message]
2011-01-11 12:52 ` VLANs Jonathan Tripathy
2011-01-11 17:12 ` VLANs John Haxby
2011-01-11 17:15 ` VLANs Jonathan Tripathy
2011-01-11 17:21 ` VLANs John Haxby
-- strict thread matches above, loose matches on Subject: below --
2011-01-05 12:12 VLANs Jonathan Tripathy
2011-01-06 7:32 ` VLANs John Haxby
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=4D2C5193.6010703@oracle.com \
--to=john.haxby@oracle.com \
--cc=jonnyt@abpni.co.uk \
--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.