inova
join:2006-05-03
Macnutt, SK | reply to gmcintire
Re: Subnets
Thanks, I'll give it a go... |
|
gmcintire
Graham
Premium
join:2005-08-09
Blue Ridge, TX
| reply to inova
said by inova  :Ok, so that's what that means. Would using this feature be problematic if both sides of the radio were on public or 192.168.xxx.xxx schemes? It shouldn't matter what IP space each interface your AP has because the isolation is done at layer 2, while routing is layer 3. |
|
inova
join:2006-05-03
Macnutt, SK | reply to gmcintire
Ok, so that's what that means. Would using this feature be problematic if both sides of the radio were on public or 192.168.xxx.xxx schemes? |
|
gmcintire
Graham
Premium
join:2005-08-09
Blue Ridge, TX
| reply to inova
said by inova :Hmmm, netbios garbage... I have thought about that but don't have the first clue how to deal with it. How would I filter it at the CPE? Given the Delib 23xx radios I have been using. The DLB-23xx support Layer 2 client isolation, just enable "Block WLAN Relay."
Directly from the manual:
The device supports isolation function. If you are building a public Wireless Network, enable this function can provide better security. The device will block packets between wireless clients (relay). All the wireless clients connected to the device can’t see each other.
|
|
inova
join:2006-05-03
Macnutt, SK | reply to joshg409
Hmmm, netbios garbage... I have thought about that but don't have the first clue how to deal with it. How would I filter it at the CPE? Given the Delib 23xx radios I have been using. |
|
joshg409
join:2005-05-03
Ottumwa, IA
| reply to inova
If you are only talking a few customers at each hop plus backhauls you can bridge it with little problems. Implement the addressing scheme as trc120 states. You can interchange the pc for your internet facing router and add secondary IP's to the interface. Backhauls, Infra, and management pc's on one subnet and the CPE on another. Make sure you filter netbios etc at the CPE or put routers at the customer site to prevent browsing. Remember Windows workgroup garbage is not routeable (netbios) so if you bridge that garbage will come all the way back to the router. |
|
inova
join:2006-05-03
Macnutt, SK
| reply to joshg409
joshg409, I am thinking that routing or switching won't help me much. My scenario is the first AP(only one AP, 90* sector) at the noc is associated with several clients and a couple of repeaters. Each of those repeaters get a couple more clients and another repeater. My mission is to cover lots of miles of sparsely populated rural area. All the traffic inevitably flows to the noc and switches or routers won't isolate anything. If there were two APs at one point it would be different. Does this make any sense? I think my description may be lacking somehow... |
|
joshg409
join:2005-05-03
Ottumwa, IA
| reply to inova
Think of how many users you will support, a /24 or 255.255.255.0 can only support a max of 253 devices or IP's. You will have more problems running bridged than routed and more problems with collisions on bridged than routed. You can negate some of that by connecting the AP's to switches but the size of your IP address block won't matter. We have a client that runs over 2000 machines we backhaul the data, they have crazy subnets on their side of the network. When you get to that many devices your problem will be bandwidth! Download a free subnet calculator from solarwinds.net.
We run mikrotiks and each interface is routed and has a /24 per AP. Way to many IP's but it keeps it clean and easy to remember where devices are connected. |
|
