RF is more my forte, but I encountered something like that and dealt with it by using netmap and 1:1 mapping in MT. I'm not sure what they have changed.
NetEqs response is: You simply need to put your Radio's in Bridging mode and set your router at your head end to do DHCP and NAT (instead of doing DHCP and NAT at your AP's). Mike At 10:36 PM 10/6/2009, you wrote: >Mike- >Thanks - I have a feeling something is still wrong, the connection >count is just too low - there are 10's of 1,000s of connections on >our network and this thing is only showing 120 or so at a >time. Investigating this closer, I see (even when refreshing and >taking into consideration this is a "snapshot") that the only >connections are from nodes within the device's management IP subnet >- does that seem right to you? It's on a very tight subnet which >95+% of our customers are not a part of. > >I thought the bridge IP was transparent, perhaps not? Was this >fixed or remedied in later firmware revisions? > >Thanks, >`S > >-----Original Message----- >From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] >On Behalf Of Mike >Sent: Tuesday, October 06, 2009 8:27 PM >To: WISPA General List >Subject: Re: [WISPA] NetEqualizer Question > >Current connections is a snapshot. You'd have to keep hitting >refresh to see connections, some of which happen and are over in a >fraction of a second. The penalty kicks in when the pipe begins to >get full. Then it looks at IPs with multiple connections, and >persistent connections. The only setting you really HAVE to do is >set your trunk up and trunk down. It is a nice device and will keep >you from having to buy more bandwidth. It just makes everybody play >fair in an agnostic sort of way. > >Mike > > >At 09:53 PM 10/6/2009, you wrote: > >Anyone running a NetEqualizer? I set one up on our network but > >noticed the "Active Connections" list is very low - although the > >configuration is set to monitor up to 3000 connections, less than > >200 are ever recognized by the system. Anyone have input on that? > > > >My understanding is from this connection list the system will > >interject latency when the upstream pipe is reaching saturation - > >with only 200 connections available that doesn't seem like a > >sufficient amount to gracefully throttle much of anything. > > > >BTW, running v2.40a 1u > > > >Thanks, > >`S > > > > > >------------------------------------------------------------------- > ------------- > >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/ > > > > >-------------------------------------------------------------------------------- >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/ > > > > >-------------------------------------------------------------------------------- >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/ -------------------------------------------------------------------------------- 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/
