The VLAN GUI now checks for VLAN capability/support by looking for a specific flag...
commite0e595bc9fefc8d79bb6aea456e4ccb404abef81
authorAugusto Bott <augusto@bott.com.br>
Wed, 29 Jun 2011 11:15:19 +0000 (29 08:15 -0300)
committerAugusto Bott <augusto@bott.com.br>
Wed, 29 Jun 2011 11:15:19 +0000 (29 08:15 -0300)
tree5febb014597dbd8776400cf3e173e9f4c69cd775
parent6bb7153eb8e4617010021ae82ce9a0aad564040a
The VLAN GUI now checks for VLAN capability/support by looking for a specific flag set on NVRAM variable/bitmap boardflags (BFL_ENETVLAN, 0x0100) and should detect properly a wider range of routers (previous versions checked for known boardtype values). Trunk-based VLAN support (802.1q) is still checked against known values for boardtype (currently: '0x0467' - WRT54GL 1.x, WRT54GS 3.x/4.x, '0x048e' - WL-520GU, WL-500G Premium v2, '0x04ef' - WRT320N/E2000, '0x04cf' - WRT610Nv2/E3000, RT-N16) . Still, the GUI allows the latter to be overriden, so the user can try/experiment with this feature (and eventually, report back about other boardtypes that could be included on the list above, 'known to support' 802.1q VLAN tagging). New on this version: initial/experimental handling of physical port ordering on selected models (tested only with WRT54GL v1.x and WRT54G v2).
release/src/router/httpd/tomato.c
release/src/router/www/about.asp
release/src/router/www/advanced-vlan.asp