[ previous ] [ next ] [ threads ]
 
 From:  "Alex M" <radiussupport at lrcommunications dot net>
 To:  "'Imran K'" <gururug at gmail dot com>, "'Mono Dev List'" <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall-dev] Available bandwidth warning system
 Date:  Fri, 27 Oct 2006 13:07:53 -0400
Putting monos and limiting DHCP scopes would somewhat do the job, small
problem is that if client will connect and will not get an IP then it not
always the case where the OS will try to reconnect to another AP, it can
reconnect to the same IP and again don't get the IP or it can reconnect to
neighboring AP but is that IP on the same mono that already run out of IP
you wont get an IP. RESULT: Client sits there w/ IP and only thing he/she
wants is to kill the sys-admin. 

 

So like I said the APs should be able to a) talk to each other b) talk to
controllers (ex: mono) and be able to move or optimize clients situation. 

I would like to get some team to focus on developing such features; I have
no chance on doing it on my own. 

 

  _____  

From: Imran K [mailto:gururug at gmail dot com] 
Sent: Thursday, October 26, 2006 9:14 PM
To: Alex M
Subject: Re: [m0n0wall-dev] Available bandwidth warning system

 

Allright, last suggestion, create an intermediate network between your
gateway and your wireless subnets.


Put two, three, four mono's on this intermediate segment and point them to a
radius server.


Split your DHCP scopes between these mono's. And point them upstream to your
perimeter gateway (will need a fair bit of beef) NOTE: This is only a
rudimentary solution, what you have suggested would be better. 


What do you think?







On 10/27/06, Alex M <radiussupport at lrcommunications dot net > wrote:

I wish to have monos as APs but mono is just not good enough as AP.

And no the problem is not in APs overload the problem is then main
controller/router is overloaded. 

 

OSPF - I don't think this is supported in mono either. 

 

 

  _____  

From: Imran K [mailto:gururug at gmail dot com] 
Sent: Thursday, October 26, 2006 9:00 PM


To: Alex M
Subject: Re: [m0n0wall-dev] Available bandwidth warning system

 

If I understand your situation correctly you are using mono as an AP? And it
is at your AP's (not your gateway) that you experiance high loads?

If this is so, on second thought, due to the size of your setup, I would be
trying to;



-Mesh your AP's (this could be a feature that is needed in mono) and/or 
-use an interior routing protocol (OSPF) to distribute the load internally. 
or
- use some dedicated AP's and leave Captive / Routing / Firewalling to the
mono's



Good Luck

On 10/27/06, Alex M < <mailto:radiussupport at lrcommunications dot net>
radiussupport at lrcommunications dot net> wrote:

Im not realy sure about the first one and how it works, but second one with
blocking DHCP requests looks interesting, Now I wonder if that possible in
real life, and if I have enough knowledge to do this. I never really worked
w/ dhcp editing on either windows or linux or bsd. 

 

  _____  

From: Imran K [mailto: gururug at gmail dot com] 
Sent: Thursday, October 26, 2006 7:55 PM
To: Alex M
Subject: Re: [m0n0wall-dev] Available bandwidth warning system

 

You could try to achieve some eleviation here at the ip assignment or
routing levels. i.e. have separate wired border routers (between ap and
external mono/s and issue ip's via dhcp from these wired routers upstream
(not via the AP's downstream) 


Also, you may be able to tweak /script a dhcp server to release / block
(iptables/MAC) a client forcing them to go another route (get a lease from a
router with more resources)


Just a thought



On 10/27/06, Alex M <radiussupport at lrcommunications dot net > wrote:

Just a though:

I'm sitting at veryyyyyyyyyy loaded segment right now and its ridiculous. So
I think maybe we can ad function that I never seen so far which will
accompanying the traffic shaper?  Something like if too amny users are 
connected to mono it will show thw captice portal page saying that your
speed is affected by router overload; current load id 100%. Then use some
sort of algorithm or sockets system to find out if there is another mono box

from same provider, and if yes offer user to try to push them to another not
loaded box, and if they cant connect there switch back.



Reasons why this thought coma up and my current topology:

1)im in high-rise complex with around 48,000 people using wi-fi. Complex 
runs 15 hotspot controllers that do cover same ares. Some time one
controller can have load of 10,000 people while its neighbor can have only
100. In order to deal with such thing it is possible to enable load and 
balancing if all controllers cycled in one network (mono doesn't have it,
pfsense suppose to have it; but in this case controller will only save 20%
cpu and will still have to redirect traffic onto another controller, his 
could save external line bandwidth though) another case is when AP selects
which controller to send user too, in this case no traffic will go to only
not loaded controllers.



First Thought Requirements for this are: 

-Load and Balance support

-Custom APs (I'll say MonoAP as separate project that does only AP thingies)

-Algorithms to measure and analyze max possible bandwidth and overload
probability based on current and historical data 





Any thoughts on this?






-- 
IK 




-- 
IK 




-- 
IK