LinksysWrt54g

setup
https://www.youtube.com/watch?v=Ud-Hq3kgvk4 client bridge and repeater bridge(start with this tut.) https://www.youtube.com/watch?v=VAulVSHRnoA repeater https://www.youtube.com/watch?v=KE1mr-TXUPo client bridge https://www.youtube.com/watch?v=vMXSH4SRIuA&t=0s range booster(repeater) https://www.youtube.com/watch?v=oJaYE9Yk7gc repeater bridge https://www.youtube.com/watch?v=IL75exXBKac ap setup basic https://www.youtube.com/watch?v=CopGlX3Plr4 ap setup https://www.youtube.com/watch?v=5eSvYPw8yug hilton computer club basic ap setup

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

http://www.sveasoft.com/talismanmesh

https://flashrouters.zendesk.com/hc/en-us/articles/115000967873-How-To-Setup-a-DD-WRT-Guest-Wireless-Network-On-Your-FlashRouter

Linksys AP
{{{

=
== 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
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 ??

Linksys Firmware
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.

VOIP on the WRT54g Linksys
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

Wds and Linksys
{{{ - 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
MeshNetworking