Skip to contentSkip to conversation

Untagged Frames

DISCUSSION Jonathan Tripathy 2 participants 3 messages Jun 17, 2011 – Jun 18, 2011 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi Everyone,

Does ebtables have the facility to make sure that any frames entering a bridge must be untagged (i.e. have no 802.1q tag)?

Thanks

#1 lore raw

Hello,

Quoted 3 lines · Jonathan Tripathy

Does ebtables have the facility to make sure that any frames entering a bridge must be untagged (i.e. have no 802.1q tag)?

I guess that it can be done by matching the 802.1q ethertype 0x8100.

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 6 lines · Jonathan Tripathy
Quoted 3 lines

Does ebtables have the facility to make sure that any frames entering a bridge must be untagged (i.e. have no 802.1q tag)?

I guess that it can be done by matching the 802.1q ethertype 0x8100.

Quoted 7 lines

------------------------------------------------------------------------------

So I'm guessing if I only wanted to allow untagged frames going into my bridge, I could do:

ebtables -I FORWARD -p ! 0x8100 -i <IF of port connected to bridge> -j ACCEPT

FORWARD = frames going through the bridge, not all frames entering it.

Quoted 2 lines

Is that correct? I don't need to use physdev (like I do in iptables) or anything, do I?

-i in ebtables is the same as --physdev-in in iptables : both are used to match the bridge port (physical interface). If you want to match the logical bridge interface, use --logical-in in ebtables or -i in iptables.

PS : You should avoid sending HTML to the mailing list.