>>> Any radio worth its salt that does true bridging would also have a >>> bridging table that is accessible via SNMP or HTML screen scraping. One >>> of our in-house programs polls all the AP's (we're a Canopy outfit, but >>> same principles apply to most Ethernet-based gear) and saves the MAC >>> addresses to a database, where I match the MACs to the subscriber's >>> radio and back to their account. >>> >> So what happens when the customer plugs the radio into the switch and >> is broadcasting his local DHCP info to everybody? That would really >> mess up the network. >> > Nothing, you can block that at most bridge CPEs (alvarion for sure). > And can also block them at the tower side (only let the DHCP requests go > to your equipment not back to the customers on the tower).
Which is what we do with Canopy. The SM can block various things such as SMB, DHCP (server and/or client), and multicast. The DHCP through the bridging radio problem is there whether or not you use public vs. private addresses assigned statically or dynamically. -- Bryan -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
