[CUWiN] N00b Question
"Jef Green" <[email protected]> Thu, 2 Aug 2007 13:19:57 -0500
| Newsgroups | gmane.network.wireless.cu-wireless |
|---|---|
| Message-ID | <11c901c7d531$bbad9ea0$40c09242@f3j> |
This is a multi-part message in MIME format. --===============2043357912== Content-Type: multipart/alternative; boundary="----=_NextPart_000_11C6_01C7D507.D2902D60" This is a multi-part message in MIME format. ------=_NextPart_000_11C6_01C7D507.D2902D60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, My name if Jef, and I am working with onShore Networks and the local = West Town Chamber of Commerce to provide a free community wireless = internet service to Chicago Avenue in Chicago, Illinois. I have two = Soekris kits here with CuWin/NetBSD installed. Everything is running = fine, but I have a few technical questions. If this is the wrong list = to post such questions, please cut me off short here. The main thing I want to get sorted out is how to manually manage mesh = connections from node to node. Mainly I've had problems with other = (brand name) nodes in the past allowing too many hops in a situation = where a hop could be avoided - i.e. a node could have associated with a = node closer to the root (core) node, but chose not to do so. I'd like = to know the best way of handling this manually when need be. Blocking = the node's MAC from associating through an ACL would be my first guess, = but not quite sure how to implement this. I'm a bit more familiar with = Debian and the like-Linux variety, and not-so familiar with wireless = mesh networking within Linux. So between that, NetBSD and = hsls/zebra/CuWin, etc. - I'm a little lost. Perhaps there is an easy = method that I'm missing, or whatnot. The CuWin release we're using here = has a broken web management interface - FYI. I have a few other technical things I need to get worked out, but I'll = wait for the response to this question. Any help is greatly = appreciated. Thanks for your time, Jef Green Level 2 Support onShore Networks, LLC. 312.850.5490 hotWire Internet! http://www.onshorehotwire.com ------=_NextPart_000_11C6_01C7D507.D2902D60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>My name if Jef, and I am working with = onShore=20 Networks and the local West Town Chamber of Commerce to provide a free = community=20 wireless internet service to Chicago Avenue in Chicago, Illinois. = I have=20 two Soekris kits here with CuWin/NetBSD installed. Everything is = running=20 fine, but I have a few technical questions. If this is the wrong = list to=20 post such questions, please cut me off short here.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The main thing I want to get sorted out = is how to=20 manually manage mesh connections from node to node. Mainly = I've had=20 problems with other (brand name) nodes in the past allowing too = many hops=20 in a situation where a hop could be avoided - i.e. a node could=20 have associated with a node closer to the root (core) node, = but chose=20 not to do so. I'd like to know the best way of handling this = manually when=20 need be. Blocking the node's MAC from associating through an = ACL=20 would be my first guess, but not quite sure how to implement this. = </FONT><FONT face=3DArial size=3D2>I'm a bit more familiar with Debian = and the=20 like-Linux variety, and not-so familiar with wireless mesh networking = within=20 Linux. So between that, NetBSD and hsls/zebra/CuWin, etc. - = I'm a=20 little lost. Perhaps there is an easy method that = I'm=20 missing, or whatnot. The CuWin release we're using here has a=20 broken web management interface - FYI.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial = size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I have a few other technical things I = need to get=20 worked out, but I'll wait for the response to this question. Any = help is=20 greatly appreciated.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks for your time,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Jef Green<BR>Level 2 Support<BR>onShore = Networks,=20 LLC.<BR>312.850.5490</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>hotWire Internet!<BR><A=20 href=3D"http://www.onshorehotwire.com">http://www.onshorehotwire.com</A><= /FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML> ------=_NextPart_000_11C6_01C7D507.D2902D60-- --===============2043357912== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ CU-Wireless mailing list [email protected] http://lists.chambana.net/cgi-bin/listinfo/cu-wireless Project Page: http://cuwireless.ucimc.org --===============2043357912==--