Hi,
I've got wrt54g (v2.2/v3), had read many doc but got confused. Maybe due to intermix used of the terms: 802.1q|tagged|trunk|mac-based with port-based|static vlan. ie '802.1q' is used where 'vlan' is referred.
Please correct me for my current understanding as follows:
(no referrence to ATM/protocal-based vlan)
1) wrt54g (v2.2/v3) only got port-based vlan
- although bcm5325ekqm datasheet mentioned tagged vlan, it is only tagged for transfer __in__ the __only__ internal trunk (between port 5 of the switch and eth0 of the SoC).
----> Tagged when frames enter phy ports, transfer to SoC, tag removed and map to virtual ports (eth0.1, eth0.2 etc as seen by sw side, ie what we seen from openwrt). Tagged when frames leaves SoC (openwrt), transfer to switch, tag removed in switch and send to respective port(s) of the tagged vlan#.
----> ie all tagging is only within the 'hardware' section of the device; no tag is seen (other than the driver) on openwrt port or phy port.
2) due to internal tagging (only):
- no 802.1q tag is seen outside the phy device (ie effectively no 802.1q vlan tag from phy port nor on sw side of openwrt). ie effectively can treat wrt54g (v2.2/v3) as port-based __only__ device.
- therefore used of 'u'ntagged and 't'agged hint (even for port 5) when setting nvram is of no effect on wrt54g (v2.2/v3) or similar port-based device.
- ports of vlan# other then the default vlan will be auto/always tagged internally, irrespective of stating 'u' or 't' in nvram setting.
3) due to (2) -> no 802.1q tagging
- mac flooding/arp attack etc has no effect on such port-based __only__ device.
Please kindly direct me if there is any table/doc/database that has such list of vlan type (ie only port-based/susceptable to vlan attack etc) for each device. Many of the howto/doc just mentioned their steps on openwrt w/o referring to the device (version) that got me confused.
Thanks in advances for reading my post, hope to hear from your response soon.