FANDOM


TableOfContents back to http://scratchpad.wikia.com/wiki/Sasecurity


starnetwifi Edit

http://wiki.openwrt.org/toh/linksys/wrt54g

http://www.sveasoft.com/talismanmesh



Connect Linksys to mesh Edit

{{{


CONNECT Linksys Access Point to MESH: Attaching a standard AP to the ethernet port of a repeater node is a way to offer a local channel for wireless users. Use the "wired captiveportal" option to enable authentication over it and make sure to use a different channel/essid to your mesh. The AP needs to be operating in standard transparent bridging mode which is normally the default. This wont work on a gateway node though and if the "wired captive portal" option is enabled on a gateway it is likely to try and authenticate the upstream router resulting in no traffic being allowed to flow.



Linksys WRT54G Routed Client (CPE) setup instructions for Sveasoft Alchemy-6.0

You can implement the WRT54G in Routed Client mode, meaning everything is routed/NAT'd between the WRT54G Ethernet switch and the Mesh. The only device the Mesh sees is the Routers WAN MAC address. This allows you to plug in up to 4 devices into the WRT54G and only have to authenticate once on the Splash page for all devices. This implementation results in shared bandwidth for all clients attached to the WRT54G.

1. Under the Wireless tab, Basic Settings, change Wireless Mode: to Client 2. Change Wireless Network Mode: to B-Only (Found to work better than mixed mode with MeshAP's) 3. Change Wireless Network Name (SSID): to your MeshAP SSID 4. Save Settings 5. Leave Client Mode: as Routed 6. Under Wireless, Security, implement your Mesh security (ie. WEP) if appropriate 7. Save Settings 8. Under Status, Wireless, confirm link under AP Signal: (This will give the signal strength and MAC address of the associated AP) 9. If there is still no AP connection, go to the Setup tab, under Basic Setup, and choose Save Settings (sometimes it seems necessary to do a main Save Settings to implement major wireless changes)


Linsys WRT54G Bridged Client (CPE) setup instructions for Sveasoft Satori-4.0

You can implement the WRT54G in Bridged Client mode, meaning the WRT54G will appear invisible to the client and the Mesh. The Mesh will see all devices connected to the WRT54G. Each connected device will have to authenticate on the Splash page. This implementation results indedicated bandwidth for each client attached to the WRT54G.

1. Under the Wireless tab, Basic Settings, Change Wireless Mode: to Client 2. Change Wireless Network Mode: to B-Only (Found to work better than mixed mode with MeshAP's) 3. Change Wireless Network Name (SSID): to your MeshAP SSID 4. Save Settings 5. Change IP of associating AP: to the IP address of the MeshAP you wish to bridge to 6. Under Wireless, Security, implement your Mesh security (ie. WEP) if appropriate 7. Save Settings 8. Under Status, Wireless, confirm link under AP Signal: (This will give the signal strength and MAC address of the associated AP) 9. Under Setup, Basic Setup, disable DHCP server 10. Save Settings 11. Renew your IP address for your pc and you will be bridged to your Mesh.

Hi, It's Alchemy-6.0-RC1.w42 V2.04.4.8sv I've just reset the box. Have a connection via ethernet. Is that client mode routed or bridges? I also still can't see where to enter the AP's IP.If you could document something, that'd be really useful, and will stop me asking silly questions every five minutes!

Which version of Sveasoft are you running? I did all of this with the Satori version. I just got the latest version (Alchemy) in the last couple of days and am still playing with it. Make sure the DHCP server on the Linksys is on to begin with, plug an Ethernet cable into 1 of the 4 LAN ports, let you laptop or pc get an IP from the device, then follow the directions below. The IP should be the 192.168.x.1 ip address of your MeshAP. If this still doesn't work, let me know and I will set a brand new one up and document what I did.

Hi Scott, thanks for that. However, each time I change the wireless mode to 'client' I cannot find it again wirelessly from my client PC. Also, where do I enter the 'IP of associating AP'. And is this the 1.185.xxx.xxx address handed out by Wiana? I heard that ramping up the signal could make the box overheat. Any stuff on that?

In Sveasoft, choose Wireless, Basic settings, change Wireless Mode to "Client", enter the IP of associating AP:, implement Security if necessary, check your wireless connection under Status, Wireless to make sure it is associated with your MeshAP, then turn off the DHCP server under Setup and voila you should have a solid CPE wireless bridge to your mesh.BTW, the newest Sveasoft release is claiming to be able to amp the radios up to 250mW. Haven't tested it yet, but very interesting.

Hi all, I received the wrt54g this afternoon and have been playing all afternoon. It's just getting really frustrating now. So far .. I have loaded up the Sveasoft firmware. I have no idea what else to change to get the mesh network and it to talk. Has anyone got an idiots guide?

Am expecting delivery of a WRT54G this afternoon. My first task is to set it up as a standalone client equipment. Any advice on how to achieve this appreciated. For example, how can I access it's 192.168.1.1 pages from a client machine? Should I consider Sveasoft firmware? Etc etc Nick }}}


Linksys AP Edit

{{{

===

CONNECT Linksys Access Point to MESH:

Attaching a standard AP to the ethernet port of a repeater node is a really good way to offer a local channel for wireless users. Use the "wired captiveportal" option to enable authentication over it and make sure to use a different channel/essid to your mesh. The AP needs to be operating in standard transparent bridging mode which is normally the default. This wont work on a gateway node though and if the "wired captive portal" option is enabled on a gateway it is likely to try and authenticate the upstream router resulting in no traffic being allowed to flow.

==

>I'm experimenting with locustworld meshbox and wrt54g with sveasoft >firmware loaded. > >I'm wondering, is it possible to connect use a wrt54g as a client >device connected to a meshbox network? > >I'd like the wrt54g to kind of act as a repeater, so that clients in >a house can use laptops etc, connected back to the wrt54g, which in >turn connectes in to the Locustworld mesh network? > >Does anybody know if this is possible? >

The way I do this is to have two devices back to back - an AP Client device (WAP-11A, CB3 etc) which connects via wireless signal and passes it out through the ethernet port, and then plug a standard AP into the ethernet port, which takes the ethernet feed and acts as a standard AP on a different channel.

Consider the connection as an RJ45 broadband presentation, and then you are simply looking at how to provide a local Wifi connection, the same as you would do to share out an ADSL connection.

>>>I'm experimenting with locustworld meshbox and wrt54g with sveasoft >>>firmware loaded. >>> >>>I'm wondering, is it possible to connect use a wrt54g as a client >>>device connected to a meshbox network? >>> >>>I'd like the wrt54g to kind of act as a repeater, so that clients >>>in a house can use laptops etc, connected back to the wrt54g, >>>which in turn connectes in to the Locustworld mesh network? >>> >>>Does anybody know if this is possible? >>> >>

>>The way I do this is to have two devices back to back - an AP >>Client device (WAP-11A, CB3 etc) which connects via wireless signal >>and passes it out through the ethernet port, and then plug a >>standard AP into the ethernet port, which takes the ethernet feed >>and acts as a standard AP on a different channel. >> >>Consider the connection as an RJ45 broadband presentation, and then >>you are simply looking at how to provide a local Wifi connection, >>the same as you would do to share out an ADSL connection. >>

>In this case, if one user logs in from the AP logs in on the >network, aren't the other users from that AP authenticated >automatically because the meshbox only sees one client connecting?

No, because the MAC addresses of the client devices are transparently passed through. The meshbox therefore sees all the MAC addresses of the client machines, and can therefore authenticate as normal.

=====

}}}


WAP11 Edit

Linksys wap11, ESSID on mesh We use WAP11s for clients that need a wireless network. First tip: use the web interface not the crappy software that comes with it. Default IP of the device is 192.168.1.1.I usually set the first WAP11 up in APClient mode, default static IP, channel to whatever your Mesh uses and ESSID to your Mesh ESSID. Then we link with an RJ45 cable to the second WAP11 in AP mode, default static IP, different channel and ESSID. This is what clients connect to (typically using PheeNet WAP503 or Netgear MA111 USB adapters).I've never been able to get a WAP11 to obtain an IP address via DHCP from a Meshbox DHCP so I don't use it. Set up as described above, the WAP11s will happily pass DHCP to network clients. If you do a sigspy on a Mesh node you'll see the MAC IDs of the clients. I have several client networks working this way. Answ:

We are having some on-going problems getting the Pheenet WAP-011A access point to connect to anything in Client mode.This has included, so far, attempts to connect to a D-Link DI-624 Wireless AP/Router and even another Pheenet WAP-011A in AP mode !! We are due to set a bunch of these up with some MESH boxes being delivered next week. Has anybody any knowledge of these boxes, tips etc. they can pass on that might help ??

WAP11 and DHCP Edit

{{{ We use WAP11s for clients that need a wireless network. First tip: use the web interface not the crappy software that comes with it. Default IP of the device is 192.168.1.1.

I usually set the first WAP11 up in APClient mode, default static IP, channel to whatever your Mesh uses and ESSID to your Mesh ESSID. Then we link with an RJ45 cable to the second WAP11 in AP mode, default static IP, different channel and ESSID. This is what clients connect to (typically using PheeNet WAP503 or Netgear MA111 USB adapters). I've never been able to get a WAP11 to obtain an IP address via DHCP from a Meshbox DHCP so I don't use it. Set up as described above, the WAP11s will happily pass DHCP to network clients. If you do a sigspy on a Mesh node you'll see the MAC IDs of the clients. I have several client networks working this way. We are having some on-going problems getting the Pheenet WAP-011A access point to connect to anything in Client mode. This has included, so far, attempts to connect to a D-Link DI-624 Wireless AP/Router and even another Pheenet WAP-011A in AP mode We are due to set a bunch of these up with some MESH boxes being delivered next week. Has anybody any knowledge of these boxes, tips etc. they can pass on that might help. }}}


edit topic Edit

{{{

> 1. The WAP connects hapily to the MeshAP and gets a nice stable signal. > 2. The client connects to the ethernet side of the WAP and is able to > obtain an IP address from the MeshAP box. > 3. Then the cliend tries to open a web browser the page times out and > they do not get redirected to the splash page to authenticate. > 4. I tried to use VPN as a longin method but this would not work either. > 5. I can Ping the MeshBox from the client, i can SSH to the mesh box > from the client. > > Some sugested updating to the sveasoft firmware however this has > exactly the same issues. > > Just to be on the safe side and ensure the issue was not caused by the > meshbox blocking the WAP i added the WAP to the auto authentication > list however this made little if any diference. > > I picking that the issue is with the WAP and not MeshAP as it is > almost as if it has a firewall built in and will not pass any data > until a user has authenticated. (other than some services) > > Anyone have any ideas on this? }}}


DNS on Linksys Edit

{{{ Linksys and DNS I would change to www.openwrt.org I would check the DNS setup. Sounds like DNS is broken somehow. I know that there is some kind of DNS proxy setup with sveasoft but I am unsure how it is currently implemented or if they moved past it in the lastest release. > I was poking around trying to find an inexpensive client device, I was > pointed toward the WAP54G and after setting it up discovered some > really interesting issues. 1. The WAP connects hapily to the MeshAP and gets a nice stable signal. > 2. The client connects to the ethernet side of the WAP and is able to > obtain an IP address from the MeshAP box. > 3. Then the cliend tries to open a web browser the page times out and > they do not get redirected to the splash page to authenticate. > 4. I tried to use VPN as a longin method but this would not work either. > 5. I can Ping the MeshBox from the client, i can SSH to the mesh box > from the client. > Some sugested updating to the sveasoft firmware however this has > exactly the same issues. > Just to be on the safe side and ensure the issue was not caused by the meshbox blocking the WAP i added the WAP to the auto authentication list however this made little if any diference. I picking that the issue is with the WAP and not MeshAP as it is almost as if it has a firewall built in and will not pass any data until a user has authenticated. (other than some services) http://borg.co.nz/ }}}


get topic Edit

{{{ > 1. The WAP connects hapily to the MeshAP and gets a nice stable signal. > 2. The client connects to the ethernet side of the WAP and is able to > obtain an IP address from the MeshAP box. > 3. Then the cliend tries to open a web browser the page times out and > they do not get redirected to the splash page to authenticate. > 4. I tried to use VPN as a longin method but this would not work either. > 5. I can Ping the MeshBox from the client, i can SSH to the mesh box > from the client. > > Some sugested updating to the sveasoft firmware however this has > exactly the same issues. > > Just to be on the safe side and ensure the issue was not caused by the > meshbox blocking the WAP i added the WAP to the auto authentication > list however this made little if any diference. > > I picking that the issue is with the WAP and not MeshAP as it is > almost as if it has a firewall built in and will not pass any data > until a user has authenticated. (other than some services) }}}


Linksys and MAC of meshbox Edit

{{{ ANSW: check both bridge tables before and after rebooting the linksys. (man brctrl or brctl...don't remember) The linksys may only be accepting passive wds links while the lw box actively looks to connect through wds So when you boot the Linksys does nothing, while when you boot the lw it goes out and looks for friends and the Linksys passively accepts a request.. You must enable active wds negotiation for the Linksys or just add the mac address of the LW box to the Linksys' list of wds friends. The problem is not in the routing, as there are no routes between the two nodes, just bridges. To see what goes wrong you should do this: make sure both nodes work get a listing of the bridges on both units (brctl -a or -l or check the man page) reboot the linksys See how the bridgetables look look now. It may well be something like a negotiation issue where the Linksys does not actively negotiate a wds connection unless you enter the mac address of the LW box, while the LW box does actively negotiate wds and finds the Linksys passively accepting every time it boots.


ANSW: I have found the problem / solution. It seem that when the 54G router restarts it fails to trigger something on the LW side to rejoin. So I did a little snooping around in the mysterious HJ folder and I ran across the wscan script. This kicks of a scan to rejoin between AP's. This rejoins theLW node to the 54G AP and everything is happy again. Now for the help fromsome of you script guru's. I need an example of a script that will ping an IP address and if it fails then an action is taken. I would set the crontab to kick of this scrip every 5 minutes or so and if it didn't see the 54G ip address it would then call the wscan script in the HJ directory. Can anybody point me in the right direction or send me an example? I must say I love how flexible Linux is :) Now all this is preliminary, I don't know how wscanwill effect the node when you have other LW nodes connected and you run wscan, that is tonight's pot of coffee QUES: >I am currently connecting with WDS only as far as I know. I am not usinG tunneling just my ssid, wep and wds. Let me elaborate some, I have a LW node that is giving out 192.168.170.x as its local ip range. The wiana ip address>is 1.251.125.53 and it is running on 25dev85. The wrt54g is running Alchemy >pre 5.3 and the router address is 192.168.170.2 with it's dhcp turn off. I>have set the WDS settings on the wrt54g to link with the LW node and the>link work fine and anybody connecting to the wrt54g will hit the LW nodE's>dhcp and get an address. This also register the clients MAC on the LW node>fulfilling all the requirements for bandthwith control and authentication.>The issue arrases when the wrt54g reboots, it can't reconnect with the LW>node. This problem seems to be with the LW node at this point. I can leave>the wrt54g running and reboot the LW node all day without issue and the WDS>link is automatically recreated, but when rebooting the wrt54g something>seems to stick in the LW node. I have watched all the files I know to watch>"AP and WDS in the proc/net/hostap/wlan0 directory" and it looks like they>are functioning correctly but not connection after the original link unless>you reboot the LW node. I will include all info requested below and anything>else I can think of and thanks for the replies. I hope if this works so I>can have a "mesh lite" unit for small clusters of users with out the high>price of a regular node. The wrt54g use a 200 mhz processor with a broadcom>G wireless card. The mesh lite outdoor unit should run about 125 dollars>ready to install and acts as an AP thus increasing your coverage area, this>is my motivation. :O) >1.251.125.53@meshbox:~# netstat -a >Active Internet connections (servers and established) >Proto Recv-Q Send-Q Local Address Foreign Address State >tcp 0 0 *:5280 *:* LISTEN >tcp 0 0 *:51010 *:* LISTEN >tcp 0 0 *:10085 *:* LISTEN >tcp 0 0 *:domain *:* LISTEN >tcp 0 0 *:ssh *:* LISTEN >tcp 0 0 *:pptp *:* LISTEN >tcp 0 76 192.168.1.101:ssh 192.168.1.100:3639 >ESTABLISHED >udp 0 0 1.251.125.53:654 *:* >udp 0 0 *:domain *:* >udp 0 0 *:bootps *:* >raw 0 0 *:icmp *:* 7 >raw 0 0 1.251.125.53:255 *:* 7 >Active UNIX domain sockets (servers and established) >Proto RefCnt Flags Type State I-Node Path >unix 9 [ ] DGRAM 391 /dev/log >unix 2 [ ] DGRAM 43380 >unix 2 [ ] DGRAM 13990 >unix 2 [ ] DGRAM 3200 >unix 2 [ ] DGRAM 2837 >unix 2 [ ] DGRAM 1358 >unix 3 [ ] STREAM CONNECTED 1067 >unix 3 [ ] STREAM CONNECTED 1066 >unix 2 [ ] DGRAM 1064 >unix 2 [ ] DGRAM 322 QUES: I have watched the LW node after rebooting the 54G router and this is whatI am getting from "dmesg" > 1.251.125.53@meshbox:~# dmesg > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > 1.251.125.53@meshbox:~# The 5e:64 MAC is the 54G router. I can reboot only the LW node and everything works after that :O( So it looks like something is getting stuck in LW but I am not sure what. }}}


MAC transparency on Linksys Edit

{{{ >>>I'm experimenting with locustworld meshbox and wrt54g with sveasoft
>>>firmware loaded.I'm wondering, is it possible to connect use a wrt54g as a client
>>>device connected to a meshbox network?
>>>I'd like the wrt54g to kind of act as a repeater, so that clients
>>>in a house can use laptops etc, connected back to the wrt54g,
>>>which in turn connectes in to the Locustworld mesh network?
>>>Does anybody know if this is possible?
>>The way I do this is to have two devices back to back - an AP
>>Client device (WAP-11A, CB3 etc) which connects via wireless signal
>>and passes it out through the ethernet port, and then plug a
>>standard AP into the ethernet port, which takes the ethernet feed
>>and acts as a standard AP on a different channel.
>>Consider the connection as an RJ45 broadband presentation, and then
>>you are simply looking at how to provide a local Wifi connection,
>>the same as you would do to share out an ADSL connection.
>In this case, if one user logs in from the AP logs in on the
>network, aren't the other users from that AP authenticated
>automatically because the meshbox only sees one client connecting?
answ:
No, because the MAC addresses of the client devices are transparently
passed through. The meshbox therefore sees all the MAC addresses of
the client machines, and can therefore authenticate as normal.


}}}

Pull IP from Linksys WRT54g Edit

{{{ Linksys WRT54G pulls IP from mesh
On all of our clients, we use a bridge (outdoors) and bring it to a
ROUTER indoors. I have grown really fond of the little Linksys WRT54G.
I put everyone behind the router. That way they pull one IP only from
the network (mesh side). Using a hub or switch, each PC pulls an IP.

QUES:
would start monday off myself. Currently I have the following setup for my
home network: wireless signal from wisp comes in and goes throught
windows xp box(server) which I then pass to a hub. One computer connected to
hub(client) and my gateway meshbox also is connected to hub. I know
a hub is not the best solution, should I go with a router or switch?
}}}

Linksys Firmware Edit

Linksys firmware

I'm experimenting with locustworld meshbox and wrt54g with sveasoft >firmware loaded.I'm wondering, is it possible to connect use a wrt54g as a client >device connected to a meshbox network? >I'd like the wrt54g to kind of act as a repeater, so that clients in a house can use laptops etc, connected back to the wrt54g, which in turn connectes in to the Locustworld mesh network?

The way I do this is to have two devices back to back - an AP Client device (WAP-11A, CB3 etc) which connects via wireless signal and passes it out through the ethernet port, and then plug a standard AP into the ethernet port, which takes the ethernet feed and acts as a standard AP on a different channel.

Consider the connection as an RJ45 broadband presentation, and then you are simply looking at how to provide a local Wifi connection, the same as you would do to share out an ADSL connection.

Senao and Linksys Edit

{{{ what other routers have you found this problem with? Better yet, what routers have you found that will work with a CB3 in this situation? Also, I'm not quite sure I follow what you're doing when you flash the CB3 to a AP3 and tie it to a CB3. Can you explain?

> I have seen the same issue with some of the Linksys Routers as well as some > others. I have flashed one of the CB3's to a AP3 and tied it to a CB3 and > the problem went away. I believe it is in the routers not handling the lease > renewal correctly. Let me if you find something out.

> > I have a user in a strong signal area that is trying to tie into his home > > network with a client bridge to my mesh network. I have several other > > clients that are using the senao CB3 to tie into a single computer with no > > problems. The user with a home network gets booted off several times a day > > and has to totally restart his entire network each time. He is using a > > Linksys Cable/DSL router on a different subnet than the CB3. The CB3 is > > 192.168.1.1 and the Router is 192.168.2.1. I have the CB3 set up for MAC > > cloning. I'm running build25dev85. I have one other client that has a > > similar situation but they are in a weak signal area so I put in another > AP > > at their location and so their Linksys Router is tied by ethernet to the > AP. > > > > I have noticed that if I reboot the AP he is tied to, there is strong > signal > > to another AP but the CB3 doesn't switch to it. }}}




VOIP on the WRT54g Linksys Edit

Some words on using the WRT54G as an AP, maybe they will help. There are 3 MAC addresses on the WRT54G; the MAC address for the wireless side of things is the one the MESH will see. I use the box as an AP/CPE and for the time being have no plans to use any other. I have installed the latest version of Alchemy on the box, though I'm not sure that you really need it. I fixed on the WRT54G because it was cheap, configurable, easy to get my hands on and (now) stable.

I wouldn't recommend setting the power to 80. I had my boxes on this setting and found that they needed re-booting every now and again. I knocked them back to 40 and haven't needed to touch them since - that was 2 months ago. I couldn't say if setting to 80mw was causing the problem but as Kenny mentioned, the box was running warm/hot. Now it doesn't

The WRT54G's are used as VoIP clients (using Grandstream units) - I am currently testing Linksys PAP2's in preference to the Grandstream's.

On the mesh side I put the wireless MAC address of the WRT54G into WiaNa and allocate an appropriate tariff (member/owner). That's the only MAC address that the mesh will see as all wired clients are supported by DHCP from the WRT54G. The box only gets the bandwidth you have allocated so each client wired into the WRT54G gets a proportion of the total bandwidth.

Regarding VoIp, I suggest that you look Wireless|Applications & Gaming as this is where you can give priority to the SIP service. I have a Word doc with screen shots that I use for installs if you want a copy (it isn't brilliant - but there are screenshots - I just use it as a reminder), email me off list and I'll send you a copy. I have no idea whether this VoIP priority setting is passed down through the mesh all I know is that it works and I now have some happy customers. Having said that I am having an issue with using sipproxy on my mesh, writing this I am wondering if the WRT54G's have got anything to do with it. I currently run my mesh with sipproxy off. If I stick it on, the mesh fails.

Previously I was using a WAP011A as the AP with the WRT54G plugged into that (to give the clients a 54g internal wireless network). VoIP was crap and thanks to some pointers from others on this list the problem was identified as being the WAP011A. I swapped them around so the WRT54G is the AP - complete with 4 ports - and the WAP011A gives them a 11b wireless network in their home. After that change VoIP was fine.

Regarding WDS on the WRT54G - I agree with Kenny, the box was unstable and needing re-booting. So I didn't bother with it. Anything that needs constant (however infrequent) re-booting is a waste of space and if you are encountering issues with the service, how would you know whether it was or it wasn't the WDS setting that was causing the problem. As I am unable to specifically identify what is causing the box to stall with the WDS setting operative, I avoid it.

It will definitely replace a CB3 + 4-port router! Best of all, if you have a long range shot to make, you can put one of these into a RooTenna (same connector as the CB3). The only problem is that you need PoE, and by the time you add that, you are up to the same price as a Deliberant bridge - however you don't have the 4 ports with the Deliberant.

According to Wes, the 5V PoE will work with the Linksys, and since I had some of those, I tested that out, and can confirm they work very well. All in all, these Linksys units have good receive sensitivity, and note that if you dig around in the new firmware you have, you can turn it up to 250mW. Now in saying that, I've heard it puts out a bunch of noise and that will burn up the radio in no time. I'm setting mine up at 80mW, which is supposed to be much cleaner on the RF side and not as likely to burn up the radio in it.

I've had two of them running in my house for months. One is on my VoIP phone and the other is running on my kids iMac. I'm not sure of the version of firmware I last put on them, but it's been very stable. Some of the earlier versions had to be reset about twice a month, but this that I've got now is very solid. I've found that the unit on my VoIP phone (in my kitchen right under an AC vent) gets pretty warm when you place the VoIP terminal adapter on top of it (partially covering the vent holes) so I would make sure it's well ventilated if outside, and doesn't have anything sitting on top of it if it's inside.

   Most of my recent hookups have been in the 4 to 6 mile range from a tower and as you know, I don't jack around when it comes to my antennas and radios. Instead of quibbling with the lower powered Linksys units, I'd rather use the Deliberants. Still, I think the Linky will do what you want, and do it quite well.
   Oh - one more thing. The MAC address changes when you put it into client mode! You'll have to shell into the Meshbox and figure out what the new MAC is. Go to the Linky, see what the IP address is - then go to the Meshbox and type 'arp -n' to get the proper MAC.
        
       what i had in mind is this
        
       here at the ranch i have a cb3 > 4 port router > 48 port switch > 4 computers voip phone  playstation 2  nodes that i test etc...
       the ips look like this      cb3 on static 192.168.12.1 > wireless side router on obtain ip automatcially / wired side dhcp 192.168.7.100/150
        
       using this config all i have to do is authenticate any of the 4 computers and the rest is spoofed
        
       im kinda like Don im looking for a cheap solution
        
       cb3 $100 + 4 port router $50 = $150    vs   wrt54g  $52
        
        
       i was hoping to replace the cb3/router combination .. using a wrt54g in client mode
       if this wont work there is gona be a brand new wrt54g on ebay pretty dang quick
           We're using that in a few places Eddie for VoIP. There is no way to make it "mesh" in the proper sense, but rather it just behaves as a regular client device. Wes Allison (Gun Barrell City, TX) played with it some and found that if you go into the WDS section and place the MAC of the MeshAP in that field, it will form a WDS link and pass traffic. However, once you loose connection for some reason, the only way to get it back is reboot the MeshAP. From the sound of things, the WDS link is prone to flake out on you for reasons yet not known.
           I never could make any of that work following the directions he shared with the list. Therefore I turn the power up to 80mW and use them for CPE devices here and there in areas where I have good signal. For the most part, I'm stuck on using the Deliberant bridges these days, so my Linksys experience is rather limited. Still, compared to some of the other stuff Linksys has put out there, these are pretty respectable performers.
               i got a Wrt54g runnin that german guys alchemy final.. then reset it to factory defaults.. changed it to client mode.. put in my ssid.. i read something about puttin in the ip of the mesh node and other stuff but i dont know where to put it
               i get a splash sceen but cant authenticate
                
               help
                can someone walk me thru this from  factory reset
               please be specific im dumber than a box of rocks at this point


Intramesh calls Edit

{{{

I've been testing this feature and here's where I am - all phones are Grandstream. Some possible configuration required - I've set the codec to G729 for example, I'm sure the phone will cascade through the codec list but I haven't tested it. Apart from that 'phones should work out of the box for an IP to IP call (enter IP address in xxx.xxx.xxx.xxx format - filled with zeroes as appropriate). If you have SIP data loaded the IP number call process doesn't work as the phone is looking for a SIP server.

The possible problem with an IP address to IP address call is that the address is supplied from the local mesh dhcp server so the addresses can change (not much good for a phone number). Next you have to be on the same address range. As I write this I'm not up to speed with the address ranges being supplied by my meshboxes and haven't tested across the mesh. Test was 2 phones side by side connected to a Cabletron hub and then onto a WAP011A configured as an Access Point Client. You will need to set-up WIANA accounts for each device. You can't use username and password it has to be MAC address (if someone has figured out how you can get a phone to pass across the username and password in a non SIP Server environment please tell me)

I've been using the following firmware versions 1.0.4.23 and 1.0.5.16, both work.

Note: Careful of using the phones on a WRT54G in Routed Client Mode (and once again my thanks go to Scott Annis for the help he has given me on this). The WRT54G will supply a local IP address in this mode as you don't want to have to set-up clients on WIANA for each device hiding behind the Linksys box (WIANA can't see them). I guess that if client on WIANA rings the phone sitting behind the WRT54G WIANA address it could/should ring (some sort of translation happening here) but I haven't had the time to test this. Anyone clue me in on this it would be appreciate.

I suggest that a dhcp server should be added to your mesh and all clients routed to use it - seen some email stuff on this lately, haven't followed it through yet!

So I reckon we are at the "Black Box" stage - providing you have thought out your mesh network configuration. Now to the good part, all calls are free. This is a great selling point for your mesh and you can make a small profit on the 'phone sale at the same time.

Next, Wireless IP Phone. Tested using the same unit as Moshe. Works fine 2 hops down. I haven't got 3 hops so can't test further. Again beware IP address ranges, this phone won't query on the fly so if you wonder across mesh zones whilst chatting away your call could die. Another reason perhaps for a dhcp server.

Must own up and say that the dhcp server statements are all assumptions as haven't tested this. Would appreciate other folks findings. If this is of help I suggest someone bungs it on WIKI.

More testing will follow and I will email the list with my findings

   Hi
   Is this at the 'Black Box' stage for us steam age engineers?
   If so can any one recommend what kit (Black Box) that is available to UK user to get to us started using VoIP on our mesh network for 'internal' calls we have ruled out external as we use Satellite for backhaul at the moment,
   Can this be a handset ethernetted into a hub and then mesh box i.e. independent of users computer or is there a WiFi version that can be used for users not hosting MeshBoxes
    
    
   We are looking at adding a ADSL line to the system to take such latency effected services when we can figure out how to route them short of setting up a parallel network   
    
   This email and any attached files are confidential and copyright protected.
   If you are not the addressee, any dissemination of this communication is
   strictly prohibited. Unless otherwise expressly agreed in writing, nothing
   stated in this communication shall be legally binding.
   This all happens automatically by the magic of SIP.


       The SIP servers/registry belonging to the respective caller and called (usually off the network) sets up the call, and as an analogy, introduces the two parties to each other, making phones ring and getting protocols negotiated. Once this is all done, the SIP protocol has done its job, and the two SIP clients talk directly to one another by the magic of IP Routing.
  
       This is a highly simplified explanation of what goes on, before there are howls of outrage from SIP experts.
       Wiki says that I can make IP to IP calls across the mesh without going through my SIP provider (and thereby using precious bandwidth).
       How is this done?  Do I need to install the Asterisk module?
       How can I check that the call isn't actually leaving the mesh?
       Do I need to ring a special number, perhaps the IP address (which I can't imagine is right as it is served by DHCP and so can change)?

}}}


WDS to repeat signal Edit

{{{ So if it can operate as a repeater fine, and repeat the signal of the meshbox, I think this would work for me. It's not the best solution but I think it should suffice?


So if this list does not have an archive which is searchable, is it not possible to run the list somewhere else? I know somebody set up a list on yahoo groups recently but I think thier lists are bad. Perhaps there are other problems moving the list will create?

Any idea how many subscribers are on this list?


Theoretically the linksys can just repeat the wireless singal of the LW MeshAP. It can repeat the signal of a linux box set up as an access point using WDS.

MeshAP uses WDS to connect their nodes in infrastructure mode, but on top of that they use authentication, tunneling, compression and routing discovery to build a network. Your Linksys will not be accepted in that game and only repeating the wirelss signal of a MeshAP access point, won't give you the desired effect.

Your question and various others regarding this matter have been addressed on this list many times. A similar question regarding OpenWRT just a few days ago. Unfortunately, while the list is made of public contributions, past contributions aren't open to the public. Maybe you can order the archives with all the information you want on this subject together with the pro version from Locustworld.

>I'm experimenting with locustworld meshbox and wrt54g with sveasoft >firmware loaded. > >I'm wondering, is it possible to connect use a wrt54g as a client device connected to a meshbox network? > >I'd like the wrt54g to kind of act as a repeater, so that clients in a house can use laptops etc, connected back to the wrt54g, which in turn connectes in to the Locustworld mesh network? > >Does anybody know if this is possible? }}}

Number of WDS links Edit

{{{ What is the limiting factor on how many WDS links you can have on one AP,,
CPU? Memory? driver restrictions?

  

Answ:
I believe it is a limitation in the number of possible entries in the
wds bridge tables of the wireless cards. Each wds enabled ap has to
keep track of the mac address of the other wds ap's.
MeshAP doesn't rely on bridging for meshing, but on dynamic routing and
tunneling. So it's enough for a MeshAP node to know it's directly 2 or
3 wds connected neighbours which requires only a few entries in the wds
bridge table. On top of that the router discovery protocol detects
routing paths in the entire network and configures the routing table on
each node. At least that's about what is going on ;-)
So if you take a a few Linksys WRT54g's and load them with OpenWRT
which supports routing and routing discovery with oslr you could build a
similar mesh network with OpenWRT. In theory at least.
If there's a port of zebra (zebra.org) and ospf, I'm almost sure you
can do it as I have experience in setthing up ospf based routers. ospf
works fine. As said, an alternative to ospf is oslr, which *is* available for
OpenWRT.
In any case, you would connect them using WDS and have ospf
automatically build routing tables based on what it hears from the
neighbouring nodes.But reading
http://www.openwrt.org/forum/viewtopic.php?t=351&highlight=oslr I'm
afraid that even users on OpenWRT haven't much of a clue on how to do
it.
Imo if you have wds and routing in one unit, your wds enabled unit only
needs to know the neighbouring unit, not any more than that. The
routing then compensates for the limited space of bridge entries in the cards
firmware.
Did I mention chillisoft has a captive portal for OpenWRT? }}}

WRT54G in client mode Edit

{{{ Scott "yes" on both accounts ;) I am using the wrt54g in client mode and it works great. I also am working on a cheap range extender for areas that only service 10 or less clients. This lets me get into areas that a full blown LW mesh was just too expensive for 3 or 4 clients.

Just to throw my two cents worth in, I thought WDS was basically to mini-mesh, meaning to create wireless hops beyond wired networks. If you truly want to use the WRT54G as CPE, then implement it as a client device. In Sveasoft, choose Wireless, Basic settings, change Wireless Mode to "Client", enter the IP of associating AP:, implement Security if necessary and voila you have a solid CPE wireless bridge to your mesh.

If you are trying to extend the reach of your Mesh by implementing WDS, then that is another story.  ;) I have been testing the WRT54G as a CPE and as a low customer node. I have been able to get the WRT to create a WDS link with LW nodes and have clients pass thought and use the LW node for DHCP, Auth, bandwith control, etc. The only thing holding me back is when I reboot the WRT it will not recreate the WDS link with the LW node, do you have this problem? I have the same goals as you, I would like to use the WRT for CPE and for Nodes that only support 10 or less clients. How are you setting up your WDS in Sveasoft? and what version are you using? I have update to the 6.02 Sveasoft prerelease and I am use the LAN setting in WDS and just adding the MAC address. To follow up with the posts from Andrew Hooper and Jeromie Reeves concerning the use of Linksys WRT54x as CPE in a community wireless mesh.

I agree with Andrew that the WRT54x makes an excellent inexpensive piece of CPE. Its features make it a good choice for customer site. The WRT54x is dual PCI and can have an antenna fly-lead attached to connect it to an antenna. The device could enable a wi-fi connection in the home and link to a community mesh - in a single box solution. It has a four port hub and can be used to create a LAN for a customer if required. It is £54 UKP!!!

I have been working on getting a WRT54G connected to my community mesh here in London And I have had some success with the WRT54 and the Sveasoft firmware. So far I have been able to manually configure a P2P WDS connection on the WRT54 and have been able to ping from the WRT54 to the mesh-AP from clients connected by wi-fi and LAN to the WRT54.

From digging around on the mesh-AP when it is 'meshed' with other APs,

I have noticed that there are a number of WDS connections visible in the output of ifconfig. These WDS connections must be created automatically when the mesh-AP discover each other. I need to know how the mesh-AP discover and setup WDS connections to other devices so that I can either a) get this to happen automatically with any device (desirable) or b) get this to happen manually (preferred to the high cost of other CPE!)

(oh, for more documentation!)

Getting this working has further benefits that I can see. A large number of people in my catchment area are reluctant to migrate to the community mesh due to the high investment that they have already made in wi-fi equipment (a home router or similar) for their existing xDSL/Cable. Having the ability to reuse this equipment with one of the open-AP firmware hacks out there is a benefitial for a number of reasons a) low cost of of member setup, b) environmentally sound recycling of consumer electronic devices and c) extendeds the investment in technology made by a consumer. How many times have you been forced into an upgrade when you've wanted to change providers?

I don't want to use the WRT54 as a replacement for the meshAP. The Locustworld combination of hardware and software is exactly what I need for infrastructure and hot-spot implementations. However it is cost prohibitive for customer premise equipment.

I look forward to hearing your comments.

I am starting to feel like the Linksys salesman :O) Yes, I have one in testing right now. I replaced a D-Link 810+ that was giving me problems and the linksys is flashed with Sveasoft firmware, set to client mode. I haven't had a chance to dig around in the client mode yet as far as all the features "port filtering and firewall etc" But right now I have 3 computers hooked into the switch part of the linksys and they all bridge to my mesh network under the linksys MAC address and IP. So all you see on my node is one client "the linksys" and I have set the bandwidth limitation on the linksys. I hope it will work something like this, the bandwidth will be limited to the MAC address of the linksys in client mode. The user can plug up too 4 hardwired devices into the switch part of the linksys. I have not finished testing yet. I need to find out if the linksys unit only get 500 K of bandwidth and each hardwired device fight over 500K or if each hardwired device gets 500K each. My goal for the linksys is to have one unit that links to my mesh and provides a 4 port switch with firewalling all in one unit. The first hurtle is to make sure that no matter what is plugged into the linksys that it will only share it's allotted 500K of bandwidth. Then I will dive deeper into the firewalling stuff. It would be very nice to have a 802.11 G all in one client unit that you can buy at Wal-Mart for about 70 bucks.

The WDS feature is what links AP to AP

Can the WRT54G be flashed with appropriate firmware (i.e. Sveasoft) to make it a reasonable choice for CPE? Is that the WDS feature? They're $59 and they provide a lot of functionality the user will also need (port filtering, firewall, etc.).

}}}


Wrt54g in CPE mode Edit

{{{ Linksys WRT54G pulls IP from mesh
On all of our clients, we use a bridge (outdoors) and bring it to a
ROUTER indoors. I have grown really fond of the little Linksys WRT54G.
I put everyone behind the router. That way they pull one IP only from
the network (mesh side). Using a hub or switch, each PC pulls an IP.
QUES:
would start monday off myself. Currently I have the following setup for my
home network: wireless signal from wisp comes in and goes throught
windows xp box(server) which I then pass to a hub. One computer connected to
hub(client) and my gateway meshbox also is connected to hub. I know
a hub is not the best solution, should I go with a router or switch?
}}}

Wds and Linksys Edit

{{{ - there is no routing between the Linksys and the lwbox, only bridging. check both bridge tables before and after rebooting the linksys. (man brctrl or brctl...don't remember)

Suggestion:

The linksys may only be accepting passive wds links while the lw box actively looks to connect through wds So when you boot the Linksys does nothing, while when you boot the lw it goes out and looks for friends and the Linksys passively accepts a request.. You must enable active wds negotiation for the Linksys or just add the mac address of the LW box to the Linksys' list of wds friends.

>I am currently connecting with WDS only as far as I know. I am not using >tunneling just my ssid, wep and wds. Let me elaborate some, I have a LW node >that is giving out 192.168.170.x as its local ip range. The wiana ip address >is 1.251.125.53 and it is running on 25dev85. The wrt54g is running Alchemy >pre 5.3 and the router address is 192.168.170.2 with it's dhcp turn off. I >have set the WDS settings on the wrt54g to link with the LW node and the >link work fine and anybody connecting to the wrt54g will hit the LW node's >dhcp and get an address. This also register the clients MAC on the LW node >fulfilling all the requirements for bandthwith control and authentication. >The issue arrases when the wrt54g reboots, it can't reconnect with the LW >node. This problem seems to be with the LW node at this point. I can leave >the wrt54g running and reboot the LW node all day without issue and the WDS >link is automatically recreated, but when rebooting the wrt54g something >seems to stick in the LW node. I have watched all the files I know to watch >"AP and WDS in the proc/net/hostap/wlan0 directory" and it looks like they >are functioning correctly but not connection after the original link unless >you reboot the LW node. I will include all info requested below and anything >else I can think of and thanks for the replies. I hope if this works so I >can have a "mesh lite" unit for small clusters of users with out the high >price of a regular node. The wrt54g use a 200 mhz processor with a broadcom >G wireless card. The mesh lite outdoor unit should run about 125 dollars >ready to install and acts as an AP thus increasing your coverage area, this >is my motivation. :O) > >1.251.125.53@meshbox:~# netstat -a >Active Internet connections (servers and established) >Proto Recv-Q Send-Q Local Address Foreign Address State >tcp 0 0 *:5280 *:* LISTEN >tcp 0 0 *:51010 *:* LISTEN >tcp 0 0 *:10085 *:* LISTEN >tcp 0 0 *:domain *:* LISTEN >tcp 0 0 *:ssh *:* LISTEN >tcp 0 0 *:pptp *:* LISTEN >tcp 0 76 192.168.1.101:ssh 192.168.1.100:3639 >ESTABLISHED >udp 0 0 1.251.125.53:654 *:* >udp 0 0 *:domain *:* >udp 0 0 *:bootps *:* >raw 0 0 *:icmp *:* 7 >raw 0 0 1.251.125.53:255 *:* 7 >Active UNIX domain sockets (servers and established) >Proto RefCnt Flags Type State I-Node Path >unix 9 [ ] DGRAM 391 /dev/log >unix 2 [ ] DGRAM 43380 >unix 2 [ ] DGRAM 13990 >unix 2 [ ] DGRAM 3200 >unix 2 [ ] DGRAM 2837 >unix 2 [ ] DGRAM 1358 >unix 3 [ ] STREAM CONNECTED 1067 >unix 3 [ ] STREAM CONNECTED 1066 >unix 2 [ ] DGRAM 1064 >unix 2 [ ] DGRAM 322 >1.251.125.53@meshbox:~# > > >1.251.125.53@meshbox:~# ifconfig >br0 Link encap:Ethernet HWaddr 00:09:5B:74:01:B7 > inet addr:1.251.125.53 Bcast:1.255.255.255 Mask:255.0.0.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3653 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6548 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:239808 (234.1 Kb) TX bytes:1070408 (1.0 Mb) > >br0:1 Link encap:Ethernet HWaddr 00:09:5B:74:01:B7 > inet addr:192.168.170.1 Bcast:192.168.170.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >eth0 Link encap:Ethernet HWaddr 00:00:24:C1:FF:94 > inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:10340 errors:0 dropped:0 overruns:0 frame:0 > TX packets:16940 errors:2 dropped:0 overruns:2 carrier:2 > collisions:0 txqueuelen:100 > RX bytes:3955816 (3.7 Mb) TX bytes:3484378 (3.3 Mb) > Interrupt:11 Base address:0x5000 > >lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:786 errors:0 dropped:0 overruns:0 frame:0 > TX packets:786 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:65736 (64.1 Kb) TX bytes:65736 (64.1 Kb) > >wlan0 Link encap:Ethernet HWaddr 00:09:5B:74:01:B7 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:2741 overruns:0 frame:0 > TX packets:5432 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:543402 (530.6 Kb) > Interrupt:10 Memory:c4833000-c4834000 > >wlan0wds0 Link encap:Ethernet HWaddr 00:09:5B:74:01:B7 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3719 errors:0 dropped:518 overruns:0 frame:0 > TX packets:6499 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:294910 (287.9 Kb) TX bytes:1353386 (1.2 Mb) > Interrupt:10 Memory:c4833000-c4834000 > > > >PING 192.168.170.2 (192.168.170.2): 56 data bytes >64 bytes from 192.168.170.2: icmp_seq=0 ttl=64 time=8.660 ms >64 bytes from 192.168.170.2: icmp_seq=1 ttl=64 time=4.034 ms >64 bytes from 192.168.170.2: icmp_seq=2 ttl=64 time=4.192 ms >--- 192.168.170.2 ping statistics --- >3 packets transmitted, 3 packets received, 0% packet loss >round-trip min/avg/max/stddev = 4.034/5.629/8.660/2.144 ms > > >1.251.125.53@meshbox:~# netstat -rn >Kernel IP routing table >Destination Gateway Genmask Flags MSS Window irtt >Iface >1.251.125.53 1.251.125.53 255.255.255.255 UGH 40 0 0 br0 >192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 >eth0 >192.168.170.0 0.0.0.0 255.255.255.0 U 40 0 0 br0 >1.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 br0 >1.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 br0 >10.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 br0 >127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo >224.0.0.0 0.0.0.0 240.0.0.0 U 40 0 0 br0 >0.0.0.0 192.168.1.1 0.0.0.0 UG 40 0 0 >eth0 >1.251.125.53@meshbox:~# >1.251.125.53@meshbox:~#


the problem is not in the routing, as there are no routes between the two nodes, just bridges. To see what goes wrong you should do this: make sure both nodes work get a listing of the bridges on both units (brctl -a or -l or check the man page)reboot the linksys See how the bridgetables look look now. It may well be something like a negotiation issue where the Linksys does not actively negotiate a wds connection unless you enter the mac address of the LW box, while the LW box does actively negotiate wds and finds the Linksys passively accepting every time it boots.

found solution for WDS problem but need help on a script

I have found the problem / solution. It seem that when the 54G router restarts it fails to trigger something on the LW side to rejoin. So I did a little snooping around in the mysterious HJ folder and I ran across the wscan script. This kicks of a scan to rejoin between AP's. This rejoins the LW node to the 54G AP and everything is happy again. Now for the help from some of you script guru's. I need an example of a script that will ping an IP address and if it fails then an action is taken. I would set the crontab to kick of this scrip every 5 minutes or so and if it didn't see the 54G ip address it would then call the wscan script in the HJ directory. Can anybody point me in the right direction or send me an example? I must say I love how flexible Linux is :) Now all this is preliminary, I don't know how wscan will effect the node when you have other LW nodes connected and you run wscan, that is tonight's pot of coffee.


> I have watched the LW node after rebooting the 54G router and this is what I > am getting from "dmesg" > > 1.251.125.53@meshbox:~# dmesg > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > handle_ap_item - addr3(BSSID)=00:0f:66:ba:5e:64 not own MAC > 1.251.125.53@meshbox:~# > > The 5e:64 MAC is the 54G router. I can reboot only the LW node and > everything works after that :O( So it looks like something is getting stuck > in LW but I am not sure what.

> > Sorry if you received a msg a few times...something was wrong with my > > computer. If you didn't receive it, > > here's a short recap: > > > > - there is no routing between the Linksys and the lwbox, only bridging. > > check both bridge tables before and after rebooting > > the linksys. (man brctrl or brctl...don't remember) > > > > Suggestion: > > > > The linksys may only be accepting passive wds links while the lw box > > actively looks to connect through wds So when you boot the Linksys does > > nothing, while when you boot the lw it goes out and looks for friends > > and the Linksys passively accepts a request.. You must enable active wds > > negotiation for the Linksys or just add the mac address of the LW box to > > the Linksys' list of wds friends.

> > >I am currently connecting with WDS only as far as I know. I am not using > > >tunneling just my ssid, wep and wds. Let me elaborate some, I have a LW > node > > >that is giving out 192.168.170.x as its local ip range. The wiana ip > address > > >is 1.251.125.53 and it is running on 25dev85. The wrt54g is running > Alchemy > > >pre 5.3 and the router address is 192.168.170.2 with it's dhcp turn off. > I > > >have set the WDS settings on the wrt54g to link with the LW node and the > > >link work fine and anybody connecting to the wrt54g will hit the LW > node's > > >dhcp and get an address. This also register the clients MAC on the LW > node > > >fulfilling all the requirements for bandthwith control and > authentication. > > >The issue arrases when the wrt54g reboots, it can't reconnect with the LW > > >node. This problem seems to be with the LW node at this point. I can > leave > > >the wrt54g running and reboot the LW node all day without issue and the > WDS > > >link is automatically recreated, but when rebooting the wrt54g something > > >seems to stick in the LW node. I have watched all the files I know to > watch > > >"AP and WDS in the proc/net/hostap/wlan0 directory" and it looks like > they > > >are functioning correctly but not connection after the original link > unless > > >you reboot the LW node. I will include all info requested below and > anything > > >else I can think of and thanks for the replies. I hope if this works so I > > >can have a "mesh lite" unit for small clusters of users with out the high > > >price of a regular node. The wrt54g use a 200 mhz processor with a > broadcom > > >G wireless card. The mesh lite outdoor unit should run about 125 dollars > > >ready to install and acts as an AP thus increasing your coverage area, > this > > >is my motivation. :O) }}}

Links Edit

MeshNetworking

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.