WRT54GSv5 AP > DDWRT Join as client

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2  Next
Author Message
bushtor
DD-WRT Novice


Joined: 23 Jun 2006
Posts: 22

PostPosted: Tue Jul 04, 2006 7:50    Post subject: WRT54GSv5 AP > DDWRT Join as client Reply with quote
Hi,

I have a WRT54GSv5 AP configured as a 'normal' router w/o encryption (for testing). Its LAN IP is 192.168.22.10 and its DHCP scope is from .100 I can connect to the internet flawlessly to this AP from any wireless computer and they receive IPs via DHCP.

I have a DD-WRT box where I have restored factory defaults. Then I go to: Status / Wireless / Site survey /selected the above AP's SSID / Join

I get 'Successfully joined the SSID as client'. Then I go back to Status / Router and check if I have received an WAN IP. 0.0.0.0 all over. I click DHCP renew, but still only zeros.

What is expected to be done after the 'Successfully joined...' message? I have tried with a static WAN IP too, but I can still not connect...

Thanks for hints on how to get this up and running.
regards

Tor
Sponsor
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5771

PostPosted: Tue Jul 04, 2006 7:56    Post subject: Reply with quote
Second box hardware? Also give me me ifconfig and route.
bushtor
DD-WRT Novice


Joined: 23 Jun 2006
Posts: 22

PostPosted: Tue Jul 04, 2006 8:57    Post subject: Reply with quote
Eko, that was quick ;-)

2nd (client) box WRT54GSv4 w/DD-WRT v23SP1final

Since it has not received any IP from the AP's DHCP there is not much in the routing table:

Code:
Destination LAN IP Subnet Mask Gateway Interface
192.168.1.0 255.255.255.0 0.0.0.0 LAN & WLAN


ifconfig:
Code:

br0       Link encap:Ethernet  HWaddr 00:14:BF:E1:D4:65 
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5018 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5727 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:493395 (481.8 KiB)  TX bytes:3316601 (3.1 MiB)
eth0      Link encap:Ethernet  HWaddr 00:14:BF:E1:D4:65 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6110 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9462 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:728999 (711.9 KiB)  TX bytes:4475310 (4.2 MiB)
          Interrupt:4
eth1      Link encap:Ethernet  HWaddr 00:14:BF:E1:D4:66 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:21586
          TX packets:236 errors:742 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:14545 (14.2 KiB)
          Interrupt:2 Base address:0x5000
lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:348 (348.0 B)  TX bytes:348 (348.0 B)
vlan0     Link encap:Ethernet  HWaddr 00:14:BF:E1:D4:65 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6110 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9395 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:619019 (604.5 KiB)  TX bytes:4393506 (4.1 MiB)
vlan1     Link encap:Ethernet  HWaddr 00:14:BF:E1:D4:66 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:39798 (38.8 KiB)
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5771

PostPosted: Tue Jul 04, 2006 9:08    Post subject: Reply with quote
Check Wireless page if mode is set to "Client", maybe just press "Save" again.
bushtor
DD-WRT Novice


Joined: 23 Jun 2006
Posts: 22

PostPosted: Tue Jul 04, 2006 10:03    Post subject: Reply with quote
BTDT

One aspect of the problem seems to be that the client box doesn't receive / acquire an IP address from the AP. Its Status / Internet IP still shown only 0s...

I have earlier tried to set a static router IP in the AP's subnet, but that did not work either. As I mentioned earlier, I restored factory defaults just before doing the Join Client. And computers connect flawlessly to the AP receiving DHCP IPs et al..

What is my next step? Give a second try with a static router IP? If so, do I need to manually set up routing (how?)

Tor
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5771

PostPosted: Tue Jul 04, 2006 10:23    Post subject: Reply with quote
Do you get wireless signal? (bar on status_wireless page)
If you set static IP you don't have to do anything manualy)
bushtor
DD-WRT Novice


Joined: 23 Jun 2006
Posts: 22

PostPosted: Tue Jul 04, 2006 10:41    Post subject: Reply with quote
Hi again,

I don't see any specific 'Radio signal' bar, however at:

Status / Wireless / Packet Info I have:
Received (RX)100%0 OK, no errors <bar 100%>
Transmitted (TX)13%236 OK, 1572 errors <bar 13%>

Site Survey:
SSID MAC Address Channel Rssi Noise beacon Open dtim Rate
MySSID 00:16:B6:C2:nn:94 1 -69 -94 100 Yes 0 12(g)

The AP is transmitting on ch 1. It was interesting though that the DD-WRT client displayed current radio channel 6 in Status / Wireless.
I opened Wireless setup, changed to AP and selected ch1 and saved. Then I reselcted Client mode and saved this.
Now Status / Wireless displays the correct Ch1.

As I can Join my AP from Site Survey and it returns success I thought that the radio transmissions were working ok...?

Tor
bushtor
DD-WRT Novice


Joined: 23 Jun 2006
Posts: 22

PostPosted: Wed Jul 05, 2006 7:08    Post subject: Reply with quote
I have now flashed the client box with the latest DD-WRT firmware and restored defaults again. Also I have restored defaults at the AP box (a WRT54GSv5 with stock linksys fw). I entered a strong WPA2 key at the AP to check if the client mode is only supposed to work with encryption.

At the DD-WRT client I opened Status / Wireless and clicked the Join button at my SSID. I received a successfully joined message, but no question for a WPA2 key. I enetered the key manually and saved.

But as yesterday I have still no router IP assigned at the client despite that the AP has DHCP enabled. Computers connect wirelessly to the AP as normal...

What are the basic steps to check that my DD-WRT client is actually connected to my AP..? I'm really stuck on this, thanks if someone can provide some hints to check radio and network connection to the AP in 'small steps' so I can find out at which point this fails.

best regards

Tor
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5771

PostPosted: Wed Jul 05, 2006 7:17    Post subject: Reply with quote
Do you have "funny" SSID?

I would join as client manualy:
1). Set client router to dhcp (setup page)
2). Enter all WPA data (wireless security)
3). Set "Client" mode and enter your SSID (wireless basic page)

wait 1 min, then reboot router.

Firs try without WPA. I'm not sure if WPA2 will work in client mode. I have tested WPA AES and it's OK.

YOu shoud see client on AP status page (as all other clients)
bushtor
DD-WRT Novice


Joined: 23 Jun 2006
Posts: 22

PostPosted: Wed Jul 05, 2006 8:22    Post subject: Solved! Reply with quote
No, I have a 12 chars plain ASCII SSID ;-)

However, this time it worked Wink

I have restored defaults and started from scratch with just plain settings a zillion times, but finally now all is well. Will apply MAC filtering etc in steps and hope everything will hang on until finished.

I have two more general questions: Does it exist a utility to log into an WRT AP to see graphically signal strength and other vital data of all connected clients...?

Also I have a WRT54GSv4 with Talisman 1.1. For my bare life I cannot get another fw into this box. Even when TFTPing linksys' own latest fw for v4 TFTP reports 'Wrong code pattern'. The box' label shows v4 and still I get this message when using linksys v4 fw. Any other clue how to get DD-WRT into this box..?

regards anyway

tor
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5771

PostPosted: Wed Jul 05, 2006 8:25    Post subject: Reply with quote
Tftp generic dd-wrt at boot-wait must work.
bushtor
DD-WRT Novice


Joined: 23 Jun 2006
Posts: 22

PostPosted: Wed Jul 05, 2006 10:21    Post subject: Reply with quote
Eko wrote:
Tftp generic dd-wrt at boot-wait must work.


I did the two tests below in the boot-wait (TTL=100 ping reply) mode:

When I used winxp's own tftp -i 192.168.1.1 put dd-wrt.bin

.. i got: Server error: Invalid password

When I used Linksys' GUI tftp with password I got the aforementioned "Wrong code Pattern" error

BIN file: dd-wrt generic of July 4th.

Does it exist a tftp app which takes password as parameter but ignores the 'code pattern' problem?

Tor
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5771

PostPosted: Wed Jul 05, 2006 10:28    Post subject: Reply with quote
At boot-wait there should be no password. Maybe rename image to code.bin
BrainSlayer
Site Admin


Joined: 06 Jun 2006
Posts: 7492
Location: Dresden, Germany

PostPosted: Wed Jul 05, 2006 11:24    Post subject: Reply with quote
bushtor wrote:
I have now flashed the client box with the latest DD-WRT firmware and restored defaults again. Also I have restored defaults at the AP box (a WRT54GSv5 with stock linksys fw). I entered a strong WPA2 key at the AP to check if the client mode is only supposed to work with encryption.

At the DD-WRT client I opened Status / Wireless and clicked the Join button at my SSID. I received a successfully joined message, but no question for a WPA2 key. I enetered the key manually and saved.

But as yesterday I have still no router IP assigned at the client despite that the AP has DHCP enabled. Computers connect wirelessly to the AP as normal...

What are the basic steps to check that my DD-WRT client is actually connected to my AP..? I'm really stuck on this, thanks if someone can provide some hints to check radio and network connection to the AP in 'small steps' so I can find out at which point this fails.

best regards

Tor


the join button does not apply any encryption. it just switches to client bridge mode and sets the ssid. you will always drive better with manually configuring your ssid and your network details as well as encryption. and please use "client" mode. not "client bridge"

_________________
"So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
bushtor
DD-WRT Novice


Joined: 23 Jun 2006
Posts: 22

PostPosted: Wed Jul 05, 2006 12:07    Post subject: Reply with quote
BS,

Thanks for the update. As mentioned a couple of posts up I suddenly got it to work, and all is ok now. Thanks a lot for all support.

Does anyone have a comment on my tftp question above...?

regards

Tor
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum