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 ===
openwrt
=== Connect Linksys to mesh ===
=== Linksys AP ===
=== 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 ??
=== WAP11 and DHCP ===
=== edit topic ===
=== DNS on Linksys ===
=== get topic ===
=== Linksys and MAC of meshbox ===
=== MAC transparency on Linksys ===
=== Pull IP from Linksys WRT54g ===
=== 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.
=== Senao and Linksys ===
=== 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
=== Intramesh calls ===
 
=== WDS to repeat signal ===
=== Number of WDS links ===
=== WRT54G in client mode ===
=== Wrt54g in CPE mode ===
=== Wds and Linksys ===
=== Links ===
MeshNetworking
Openwrt
Category:Sasecurity
Category:Mesh