DD-WRT Wireless mode on WHR-G54S

I want to set up one WHR-G54S attached to the cable modem via the WAN
port. (this one, now DD-WRT)

Then I want to use another WHR-G54S as a wireless access point where
computers will be plugged into the LAN ports.

Which Wireless Mode should the cable-attached router be set to?

Which Wireless Mode should the remote router be set to?

Wireless Mode
The wireless part of your router can run in different modes:

* AP mode – This is the default mode, also called
Infrastructure mode. Your router acts as an central connection point,
which wireless clients can connect to.

* Client mode – The radio interface is used to connect the
internet-facing side of the router (i.e., the WAN) as a client to a
remote accesspoint. NAT or routing are performed between WAN and LAN,
like in "normal" gateway or router mode. Use this mode, e.g., if your
internet connection is provided by a remote accesspoint, and you want to
connect a subnet of your own to it.

* Client Bridged mode – The radio interface is used to connect
the LAN side of the router to a remote accesspoint. The LAN and the
remote AP will be in the same subnet (This is called a "bridge" between
two network segments). The WAN side of the router is unused and can be
disabled. Use this mode, e.g., to make the router act as a "WLAN
adapter" for a device connected to one of its LAN ethernet ports.

* Ad-Hoc mode – This is for peer to peer wireless connections.
Clients running in Ad-Hoc mode can connect to each other as required
without involving central access points.

Louis Ohland <ohland@charter.net> hath wroth:

>I want to set up one WHR-G54S attached to the cable modem via the WAN
>port. (this one, now DD-WRT)

AP mode. The WAN port goes to the cable modem.

>Then I want to use another WHR-G54S as a wireless access point where
>computers will be plugged into the LAN ports.

That could be in either the client mode or the AP mode with WDS.
Client mode will work allowing you to plug in multiple computers into
this 2nd WHR-G54S. However, all wireless connections would need to go
to the first WHR-G54S. However, if you use the AP mode with WDS, you
can connect to either device via wireless. There will be a slow down
with wireless connections to the 2nd WHR-G54S, but no slow down with
the computers plugged into the LAN ports on the 2nd WHR-G54S.

However, there's a catch. WDS mode does not work with WPA encryption.
The best you can do is WEP encryption. If you're seriously worried
about hackers breaking into your system, then use the client mode and
WPA. If you can live with the marginal security of WEP, then use WDS.

I would go with AP mode, WEP, and WDS.

>Which Wireless Mode should the cable-attached router be set to?

AP mode with WDS.

>Which Wireless Mode should the remote router be set to?

AP mode with WDS.

>Wireless Mode

AP mode with WDS.
http://www.buffalotech.com/support/faq.php#21

Also, I suggest you consider installing DD-WRT firmware on both your
Buffalo WHR-G54S. Many more options and goodies to play with.
<http://www.gilanet.com/ohlandl/NIC/whr-g54s.html>
<http://www.dd-wrt.com/wiki/index.php/Installation#Buffalo_WHR-G54S.2C_WHR-HP-G54_and_WZR-RS-G54>

--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

On Sat, 25 Nov 2006 20:01:35 -0800, Jeff Liebermann
<jeffl@comix.santa-cruz.ca.us> wrote in
<sp3im2tqfp10m9u7v3var1h3dr36jciisn@4ax.com>:

>Louis Ohland <ohland@charter.net> hath wroth:
>
>>I want to set up one WHR-G54S attached to the cable modem via the WAN
>>port. (this one, now DD-WRT)
>
>AP mode. The WAN port goes to the cable modem.
>
>>Then I want to use another WHR-G54S as a wireless access point where
>>computers will be plugged into the LAN ports.
>
>That could be in either the client mode or the AP mode with WDS.
>Client mode will work allowing you to plug in multiple computers into
>this 2nd WHR-G54S. However, all wireless connections would need to go
>to the first WHR-G54S. However, if you use the AP mode with WDS, you
>can connect to either device via wireless. There will be a slow down
>with wireless connections to the 2nd WHR-G54S, but no slow down with
>the computers plugged into the LAN ports on the 2nd WHR-G54S.
>
>However, there's a catch. WDS mode does not work with WPA encryption.
>The best you can do is WEP encryption. If you're seriously worried
>about hackers breaking into your system, then use the client mode and
>WPA. If you can live with the marginal security of WEP, then use WDS.
>
>I would go with AP mode, WEP, and WDS.

My own recommendation would be to always use WPA, which rules out WDS.

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>

I am trying to communicate with the remote WHR-G54S. It shows up
under "Site Survey" from the cable-connected WHR-G54S.

On the W98SE box:
Trying PING 192.168.1.1 returns with site unavailable
Trying PING 192.168.11.1 returns time out on the pings.

I'm quite at a loss. Has it somehow automagically configured to
another IP? How the heck can I derive the IP of the remote WHR-G54S if
this is the case?

Stumped Chump...

John Navas wrote:
> On Sat, 25 Nov 2006 20:01:35 -0800, Jeff Liebermann
> <jeffl@comix.santa-cruz.ca.us> wrote in
> <sp3im2tqfp10m9u7v3var1h3dr36jciisn@4ax.com>:
>
>> Louis Ohland <ohland@charter.net> hath wroth:
>>
>>> I want to set up one WHR-G54S attached to the cable modem via the WAN
>>> port. (this one, now DD-WRT)
>> AP mode. The WAN port goes to the cable modem.
>>
>>> Then I want to use another WHR-G54S as a wireless access point where
>>> computers will be plugged into the LAN ports.
>> That could be in either the client mode or the AP mode with WDS.
>> Client mode will work allowing you to plug in multiple computers into
>> this 2nd WHR-G54S. However, all wireless connections would need to go
>> to the first WHR-G54S. However, if you use the AP mode with WDS, you
>> can connect to either device via wireless. There will be a slow down
>> with wireless connections to the 2nd WHR-G54S, but no slow down with
>> the computers plugged into the LAN ports on the 2nd WHR-G54S.
>>
>> However, there's a catch. WDS mode does not work with WPA encryption.
>> The best you can do is WEP encryption. If you're seriously worried
>> about hackers breaking into your system, then use the client mode and
>> WPA. If you can live with the marginal security of WEP, then use WDS.
>>
>> I would go with AP mode, WEP, and WDS.
>
> My own recommendation would be to always use WPA, which rules out WDS.
>

Louis Ohland <ohland@charter.net> hath wroth:

> I am trying to communicate with the remote WHR-G54S. It shows up
>under "Site Survey" from the cable-connected WHR-G54S.
>
>On the W98SE box:
> Trying PING 192.168.1.1 returns with site unavailable
> Trying PING 192.168.11.1 returns time out on the pings.
>
> I'm quite at a loss. Has it somehow automagically configured to
>another IP? How the heck can I derive the IP of the remote WHR-G54S if
>this is the case?
>
>Stumped Chump...

Please do not assume that anyone reading your question has also read
every one of your previous postings. Keep it simple:
1. What are you trying to accomplish?
2. What have you got to work with (hardware and software)?
3. Where are you stuck? (What works, what doesn't).

If you successfully installed DD-WRT on both devices, they are both
set to 192.168.1.1. Duplicate IP's will not work. Plug an ethernet
cable into the 2nd AP and change its IP address to 192.168.1.2.


--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Louis Ohland wrote:
>
> * Client Bridged mode – The radio interface is used to connect
> the LAN side of the router to a remote accesspoint. The LAN and the
> remote AP will be in the same subnet (This is called a "bridge" between
> two network segments). The WAN side of the router is unused and can be
> disabled. Use this mode, e.g., to make the router act as a "WLAN
> adapter" for a device connected to one of its LAN ethernet ports.

I would use Client Bridged mode for this application. I have two DD-WRT
routers running as bridges and they work fine. I even use WPA with TKIP
encryption without any problems. The main router is a WHR-G45S running
the buffalo firmware and the client bridges are Motorola WR850g routers
running DD-WRT V23SP2.

OK, from the top:

Two WHR-G54S, both flashed to DD-WRT v23

WHR-G54S #1
Attached to cable modem via WAN port. Support wired LAN ports, plus
communicate with WHR-G54S via WPA-AES.
Set to 192.168.1.1
DHCP Server
AP mode

Router
Router Name DD-WRT
Router Model Buffalo WHR-G54S
LAN MAC 00:16:01:15:C5:6E
WAN MAC 00:16:01:15:C5:6F
Wireless MAC 00:16:01:15:C5:70
WAN IP 68.114.217.35
LAN IP 192.168.1.1
SSID dd-wrt

DHCP Clients
Host Name IP Address MAC Address Expires
CHUCK 192.168.1.112 xx:xx:xx:xx:08:36 1 day 00:00:00 Computer
* 192.168.1.113 xx:xx:xx:xx:D8:51 1 day 00:00:00 #2?

WHR-G54S #2
Set up as an access point for wired ethernet to be plugged into LAN
ports. It has no wired link to #1

I want to use the DHCP server in #1 to provide IP for all devices
attached to #2. Nothing flashy, I hope.

I solved one issue by turning off static IP on the computer that #2 was
attached to via a LAN port. I logged into #2 with 192.168.1.1, but
things went downhill from there. Using Site Survey, I changed it to
"Client", it detected #1.

>> On the W98SE box: (WHR-G54S #2)
>> Trying PING 192.168.1.1 returns with site unavailable
>> Trying PING 192.168.11.1 returns time out on the pings.

Could it be that #2 is now at 192.168.1.113?

Jeff Liebermann wrote:
> Louis Ohland <ohland@charter.net> hath wroth:
>
>> I am trying to communicate with the remote WHR-G54S. It shows up
>> under "Site Survey" from the cable-connected WHR-G54S.
>>
>> On the W98SE box:
>> Trying PING 192.168.1.1 returns with site unavailable
>> Trying PING 192.168.11.1 returns time out on the pings.
>>
>> I'm quite at a loss. Has it somehow automagically configured to
>> another IP? How the heck can I derive the IP of the remote WHR-G54S if
>> this is the case?
>>
>> Stumped Chump...
>
> Please do not assume that anyone reading your question has also read
> every one of your previous postings. Keep it simple:
> 1. What are you trying to accomplish?
> 2. What have you got to work with (hardware and software)?
> 3. Where are you stuck? (What works, what doesn't).
>
> If you successfully installed DD-WRT on both devices, they are both
> set to 192.168.1.1. Duplicate IP's will not work. Plug an ethernet
> cable into the 2nd AP and change its IP address to 192.168.1.2.
>
>

Louis Ohland <ohland@charter.net> hath wroth:

>I want to use the DHCP server in #1 to provide IP for all devices
>attached to #2. Nothing flashy, I hope.

Yep. That should work. However, last time I setup WDS, I used two
DHCP servers, with different IP address pools. It also worked.

>I solved one issue by turning off static IP on the computer that #2 was
>attached to via a LAN port. I logged into #2 with 192.168.1.1, but
>things went downhill from there. Using Site Survey, I changed it to
>"Client", it detected #1.

Third time is the charm. Change the IP address of #2 from 192.168.1.1
to 192.168.1.2. Life will be easier without duplicate IP's.

>Could it be that #2 is now at 192.168.1.113?

No.

Incidentally, make sure you have both routers set to the same channel.
Don't use Auto channel mode. Also, turn of Frame Burst (a.k.a. High
Speed Mode) which causes some performance weirdness.


--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

WHR-G54 #1 (192.168.1.1) can now ping #2 (192.168.1.2)

# 2 is set client bridged. No security right now. Still futzing. I need
to see if I can access the internet from #2.

Jeff Liebermann wrote:
> Louis Ohland <ohland@charter.net> hath wroth:
>
>> I want to use the DHCP server in #1 to provide IP for all devices
>> attached to #2. Nothing flashy, I hope.
>
> Yep. That should work. However, last time I setup WDS, I used two
> DHCP servers, with different IP address pools. It also worked.
>
>> I solved one issue by turning off static IP on the computer that #2 was
>> attached to via a LAN port. I logged into #2 with 192.168.1.1, but
>> things went downhill from there. Using Site Survey, I changed it to
>> "Client", it detected #1.
>
> Third time is the charm. Change the IP address of #2 from 192.168.1.1
> to 192.168.1.2. Life will be easier without duplicate IP's.
>
>> Could it be that #2 is now at 192.168.1.113?
>
> No.
>
> Incidentally, make sure you have both routers set to the same channel.
> Don't use Auto channel mode. Also, turn of Frame Burst (a.k.a. High
> Speed Mode) which causes some performance weirdness.
>
>

It's working. WHR #1 (192.168.1.1) is set to AP, #2 (192.168.1.2) is set
to client bridge. Playing with security.

Louis Ohland wrote:
> WHR-G54 #1 (192.168.1.1) can now ping #2 (192.168.1.2)
>
> # 2 is set client bridged. No security right now. Still futzing. I need
> to see if I can access the internet from #2.
>
> Jeff Liebermann wrote:
>> Louis Ohland <ohland@charter.net> hath wroth:
>>
>>> I want to use the DHCP server in #1 to provide IP for all devices
>>> attached to #2. Nothing flashy, I hope.
>>
>> Yep. That should work. However, last time I setup WDS, I used two
>> DHCP servers, with different IP address pools. It also worked.
>>
>>> I solved one issue by turning off static IP on the computer that #2
>>> was attached to via a LAN port. I logged into #2 with 192.168.1.1,
>>> but things went downhill from there. Using Site Survey, I changed it
>>> to "Client", it detected #1.
>>
>> Third time is the charm. Change the IP address of #2 from 192.168.1.1
>> to 192.168.1.2. Life will be easier without duplicate IP's.
>>
>>> Could it be that #2 is now at 192.168.1.113?
>>
>> No.
>>
>> Incidentally, make sure you have both routers set to the same channel.
>> Don't use Auto channel mode. Also, turn of Frame Burst (a.k.a. High
>> Speed Mode) which causes some performance weirdness.
>>
>>

What is the sequence for enabling WPA2 shared key? When I enabled it on
both WHR-G54S, my remote WHR can't even ping itself (192.168.1.2).

Both WHR were set to WPA2 Shared Key, AES, same key, and then I was
unable to connect from WHR #2. WHR #1 is still able to connect to the
internet, and I can log into it and change things.

Why did the second WHR-G54S refuse to let me log into it via 192.168.1.2?

Louis Ohland wrote:
> It's working. WHR #1 (192.168.1.1) is set to AP, #2 (192.168.1.2) is set
> to client bridge. Playing with security.
>
> Louis Ohland wrote:
>> WHR-G54 #1 (192.168.1.1) can now ping #2 (192.168.1.2)
>>
>> # 2 is set client bridged. No security right now. Still futzing. I
>> need to see if I can access the internet from #2.
>>
>> Jeff Liebermann wrote:
>>> Louis Ohland <ohland@charter.net> hath wroth:
>>>
>>>> I want to use the DHCP server in #1 to provide IP for all devices
>>>> attached to #2. Nothing flashy, I hope.
>>>
>>> Yep. That should work. However, last time I setup WDS, I used two
>>> DHCP servers, with different IP address pools. It also worked.
>>>
>>>> I solved one issue by turning off static IP on the computer that #2
>>>> was attached to via a LAN port. I logged into #2 with 192.168.1.1,
>>>> but things went downhill from there. Using Site Survey, I changed it
>>>> to "Client", it detected #1.
>>>
>>> Third time is the charm. Change the IP address of #2 from 192.168.1.1
>>> to 192.168.1.2. Life will be easier without duplicate IP's.
>>>
>>>> Could it be that #2 is now at 192.168.1.113?
>>>
>>> No.
>>>
>>> Incidentally, make sure you have both routers set to the same channel.
>>> Don't use Auto channel mode. Also, turn of Frame Burst (a.k.a. High
>>> Speed Mode) which causes some performance weirdness.
>>>
>>>

Louis Ohland wrote:
> What is the sequence for enabling WPA2 shared key? When I enabled it on
> both WHR-G54S, my remote WHR can't even ping itself (192.168.1.2).


With Bridge mode I have not been bale able to get WPA2-PSK to work. I
had to go back to WPA-PSK (TKIP) to get it to talk to my main router.
It could have been a limitation with my router, but I don't know.

Bryant Smith <bryantthesmith@lycos.com> hath wroth:

>Louis Ohland wrote:
>> What is the sequence for enabling WPA2 shared key? When I enabled it on
>> both WHR-G54S, my remote WHR can't even ping itself (192.168.1.2).

>With Bridge mode I have not been bale able to get WPA2-PSK to work. I
>had to go back to WPA-PSK (TKIP) to get it to talk to my main router.
>It could have been a limitation with my router, but I don't know.

WPA doesn't work in bridge or WDS mode. Only in access point or
client mode. The best you can do in bridge or WDS mode is WEP.

--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

TKIP works? I'll have to try it. WPA2 and AES does not work in client
bridge mode, or so it seems.

I tried Client mode on my setup, and it went stupid. I'll have to nuke
it back to the default settings and bring it up. But my setup was
working this morning (AP-Client Bridge) this morning.

http://www.gilanet.com/ohlandl/NIC/w...#Client_Bridge

I added a (crude) image of my setup.

Bryant Smith wrote:
> Louis Ohland wrote:
>> What is the sequence for enabling WPA2 shared key? When I enabled it
>> on both WHR-G54S, my remote WHR can't even ping itself (192.168.1.2).
>
>
> With Bridge mode I have not been bale able to get WPA2-PSK to work. I
> had to go back to WPA-PSK (TKIP) to get it to talk to my main router. It
> could have been a limitation with my router, but I don't know.

Jeff Liebermann wrote:
> Bryant Smith <bryantthesmith@lycos.com> hath wroth:
>
>> Louis Ohland wrote:
>>> What is the sequence for enabling WPA2 shared key? When I enabled it on
>>> both WHR-G54S, my remote WHR can't even ping itself (192.168.1.2).
>
>> With Bridge mode I have not been bale able to get WPA2-PSK to work. I
>> had to go back to WPA-PSK (TKIP) to get it to talk to my main router.
>> It could have been a limitation with my router, but I don't know.
>
> WPA doesn't work in bridge or WDS mode. Only in access point or
> client mode. The best you can do in bridge or WDS mode is WEP.
>


Well, I'm using my 760XL on the setup
>http://www.gilanet.com/ohlandl/NIC/whr-g54s.html#Client_Bridge<
I'll see about what security that I can get away with. Might be shut
down, but that will illustrate your contention.

Back to searching on it.

Client Bridged mode – The radio interface is used to connect the LAN
side of the router to a remote accesspoint. The LAN and the remote AP
will be in the same subnet (This is called a "bridge" between two
network segments). The WAN side of the router is unused and can be
disabled. Use this mode, e.g., to make the router act as a "WLAN
adapter" for a device connected to one of its LAN ethernet ports.

Limitation of WPA in DD-WRT v2.3?

///--------------------
I must surf more. Here's a WIKI tidbit...

http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge

6. Wireless Tab - Wireless Security Subtab

1. Security Mode: WEP (I have not tried anything but 128bit WEP!)
wpa-psk works as well -guyonphone; wpa-psk even works if original router
is wpa2 mixed -mcoope3; v2.3_sp2 in client bridge mode currently doesn't
support wpa2-psk, but only wpa2-psk mixed mode, so the AP has to be set
to mixed and not wpa2-only mode (it can be either AES or TKIP).-zevnik

------------------///

Louis Ohland wrote:
> Jeff Liebermann wrote:
>> Bryant Smith <bryantthesmith@lycos.com> hath wroth:
>>
>>> Louis Ohland wrote:
>>>> What is the sequence for enabling WPA2 shared key? When I enabled it
>>>> on both WHR-G54S, my remote WHR can't even ping itself (192.168.1.2).
>>
>>> With Bridge mode I have not been bale able to get WPA2-PSK to work.
>>> I had to go back to WPA-PSK (TKIP) to get it to talk to my main
>>> router. It could have been a limitation with my router, but I don't
>>> know.
>>
>> WPA doesn't work in bridge or WDS mode. Only in access point or
>> client mode. The best you can do in bridge or WDS mode is WEP.
>>
>
>
> Well, I'm using my 760XL on the setup
> >http://www.gilanet.com/ohlandl/NIC/whr-g54s.html#Client_Bridge<
> I'll see about what security that I can get away with. Might be shut
> down, but that will illustrate your contention.
>
> Back to searching on it.
>
> Client Bridged mode – The radio interface is used to connect the LAN
> side of the router to a remote accesspoint. The LAN and the remote AP
> will be in the same subnet (This is called a "bridge" between two
> network segments). The WAN side of the router is unused and can be
> disabled. Use this mode, e.g., to make the router act as a "WLAN
> adapter" for a device connected to one of its LAN ethernet ports.

WPA-Personal, looks to be possible...

http://www.dd-wrt.com/wiki/index.php...e#WPA-Personal

Louis Ohland wrote:
> Limitation of WPA in DD-WRT v2.3?
>
> ///--------------------
> I must surf more. Here's a WIKI tidbit...
>
> http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge
>
> 6. Wireless Tab - Wireless Security Subtab
>
> 1. Security Mode: WEP (I have not tried anything but 128bit WEP!)
> wpa-psk works as well -guyonphone; wpa-psk even works if original router
> is wpa2 mixed -mcoope3; v2.3_sp2 in client bridge mode currently doesn't
> support wpa2-psk, but only wpa2-psk mixed mode, so the AP has to be set
> to mixed and not wpa2-only mode (it can be either AES or TKIP).-zevnik
>
> ------------------///
>
> Louis Ohland wrote:
>> Jeff Liebermann wrote:
>>> Bryant Smith <bryantthesmith@lycos.com> hath wroth:
>>>
>>>> Louis Ohland wrote:
>>>>> What is the sequence for enabling WPA2 shared key? When I enabled
>>>>> it on both WHR-G54S, my remote WHR can't even ping itself
>>>>> (192.168.1.2).
>>>
>>>> With Bridge mode I have not been bale able to get WPA2-PSK to work.
>>>> I had to go back to WPA-PSK (TKIP) to get it to talk to my main
>>>> router. It could have been a limitation with my router, but I don't
>>>> know.
>>>
>>> WPA doesn't work in bridge or WDS mode. Only in access point or
>>> client mode. The best you can do in bridge or WDS mode is WEP.
>>>
>>
>>
>> Well, I'm using my 760XL on the setup
>> >http://www.gilanet.com/ohlandl/NIC/whr-g54s.html#Client_Bridge<
>> I'll see about what security that I can get away with. Might be shut
>> down, but that will illustrate your contention.
>>
>> Back to searching on it.
>>
>> Client Bridged mode – The radio interface is used to connect the LAN
>> side of the router to a remote accesspoint. The LAN and the remote AP
>> will be in the same subnet (This is called a "bridge" between two
>> network segments). The WAN side of the router is unused and can be
>> disabled. Use this mode, e.g., to make the router act as a "WLAN
>> adapter" for a device connected to one of its LAN ethernet ports.

Could you please hold the stream of consciousness thing, and just post
when you get to your destination? Thanks.

On Wed, 29 Nov 2006 19:39:01 -0600, Louis Ohland <ohland@charter.net>
wrote in <yCqbh.37$lm5.35@newsfe05.lga>:

>WPA-Personal, looks to be possible...
>
>http://www.dd-wrt.com/wiki/index.php...e#WPA-Personal
>
>Louis Ohland wrote:
>> Limitation of WPA in DD-WRT v2.3?
>>
>> ///--------------------
>> I must surf more. Here's a WIKI tidbit...
>>
>> http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge
>>
>> 6. Wireless Tab - Wireless Security Subtab
>>
>> 1. Security Mode: WEP (I have not tried anything but 128bit WEP!)
>> wpa-psk works as well -guyonphone; wpa-psk even works if original router
>> is wpa2 mixed -mcoope3; v2.3_sp2 in client bridge mode currently doesn't
>> support wpa2-psk, but only wpa2-psk mixed mode, so the AP has to be set
>> to mixed and not wpa2-only mode (it can be either AES or TKIP).-zevnik
>>
>> ------------------///
>>
>> Louis Ohland wrote:
>>> Jeff Liebermann wrote:
>>>> Bryant Smith <bryantthesmith@lycos.com> hath wroth:
>>>>
>>>>> Louis Ohland wrote:
>>>>>> What is the sequence for enabling WPA2 shared key? When I enabled
>>>>>> it on both WHR-G54S, my remote WHR can't even ping itself
>>>>>> (192.168.1.2).
>>>>
>>>>> With Bridge mode I have not been bale able to get WPA2-PSK to work.
>>>>> I had to go back to WPA-PSK (TKIP) to get it to talk to my main
>>>>> router. It could have been a limitation with my router, but I don't
>>>>> know.
>>>>
>>>> WPA doesn't work in bridge or WDS mode. Only in access point or
>>>> client mode. The best you can do in bridge or WDS mode is WEP.
>>>>
>>>
>>>
>>> Well, I'm using my 760XL on the setup
>>> >http://www.gilanet.com/ohlandl/NIC/whr-g54s.html#Client_Bridge<
>>> I'll see about what security that I can get away with. Might be shut
>>> down, but that will illustrate your contention.
>>>
>>> Back to searching on it.
>>>
>>> Client Bridged mode – The radio interface is used to connect the LAN
>>> side of the router to a remote accesspoint. The LAN and the remote AP
>>> will be in the same subnet (This is called a "bridge" between two
>>> network segments). The WAN side of the router is unused and can be
>>> disabled. Use this mode, e.g., to make the router act as a "WLAN
>>> adapter" for a device connected to one of its LAN ethernet ports.

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>

That's "client bridge", not WDS.

p.s. Please don't switch posting styles (top vs bottom) in mid-thread
-- it's confusing. Thanks.

On Wed, 29 Nov 2006 19:39:01 -0600, Louis Ohland <ohland@charter.net>
wrote in <yCqbh.37$lm5.35@newsfe05.lga>:

>WPA-Personal, looks to be possible...
>
>http://www.dd-wrt.com/wiki/index.php...e#WPA-Personal
>
>Louis Ohland wrote:
>> Limitation of WPA in DD-WRT v2.3?
>>
>> ///--------------------
>> I must surf more. Here's a WIKI tidbit...
>>
>> http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge
>>
>> 6. Wireless Tab - Wireless Security Subtab
>>
>> 1. Security Mode: WEP (I have not tried anything but 128bit WEP!)
>> wpa-psk works as well -guyonphone; wpa-psk even works if original router
>> is wpa2 mixed -mcoope3; v2.3_sp2 in client bridge mode currently doesn't
>> support wpa2-psk, but only wpa2-psk mixed mode, so the AP has to be set
>> to mixed and not wpa2-only mode (it can be either AES or TKIP).-zevnik
>>
>> ------------------///
>>
>> Louis Ohland wrote:
>>> Jeff Liebermann wrote:
>>>> Bryant Smith <bryantthesmith@lycos.com> hath wroth:
>>>>
>>>>> Louis Ohland wrote:
>>>>>> What is the sequence for enabling WPA2 shared key? When I enabled
>>>>>> it on both WHR-G54S, my remote WHR can't even ping itself
>>>>>> (192.168.1.2).
>>>>
>>>>> With Bridge mode I have not been bale able to get WPA2-PSK to work.
>>>>> I had to go back to WPA-PSK (TKIP) to get it to talk to my main
>>>>> router. It could have been a limitation with my router, but I don't
>>>>> know.
>>>>
>>>> WPA doesn't work in bridge or WDS mode. Only in access point or
>>>> client mode. The best you can do in bridge or WDS mode is WEP.
>>>>
>>>
>>>
>>> Well, I'm using my 760XL on the setup
>>> >http://www.gilanet.com/ohlandl/NIC/whr-g54s.html#Client_Bridge<
>>> I'll see about what security that I can get away with. Might be shut
>>> down, but that will illustrate your contention.
>>>
>>> Back to searching on it.
>>>
>>> Client Bridged mode – The radio interface is used to connect the LAN
>>> side of the router to a remote accesspoint. The LAN and the remote AP
>>> will be in the same subnet (This is called a "bridge" between two
>>> network segments). The WAN side of the router is unused and can be
>>> disabled. Use this mode, e.g., to make the router act as a "WLAN
>>> adapter" for a device connected to one of its LAN ethernet ports.

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>

Jeff Liebermann wrote:
> Bryant Smith <bryantthesmith@lycos.com> hath wroth:
>
>> Louis Ohland wrote:
>>> What is the sequence for enabling WPA2 shared key? When I enabled it on
>>> both WHR-G54S, my remote WHR can't even ping itself (192.168.1.2).
>
>> With Bridge mode I have not been bale able to get WPA2-PSK to work. I
>> had to go back to WPA-PSK (TKIP) to get it to talk to my main router.
>> It could have been a limitation with my router, but I don't know.
>
> WPA doesn't work in bridge or WDS mode. Only in access point or
> client mode. The best you can do in bridge or WDS mode is WEP.
>

I currently have 2 routers working in Client Bridge mode with DD-WRT
V23SP2 that are using WPA-PSK and TKIP encryption (I could not get AES
working). Is this the client mode or the bridge mode you speak of? I
guess I am confused at the difference between client mode and client
bridge mode. I always use Client Bridge mode because I have more than
one computer hooked to the device. WPA-PSK seems to be working just
fine with that mode. In DD-WRT there are two different settings for WPA
and WPA2. I use WPA-PSK not WPA2-PSK.

On Thu, 30 Nov 2006 11:26:07 -0700, Bryant Smith
<bryantthesmith@lycos.com> wrote in
<ekn722$r9b$1@az33news01.freescale.net>:

>Jeff Liebermann wrote:
>> Bryant Smith <bryantthesmith@lycos.com> hath wroth:
>>
>>> Louis Ohland wrote:
>>>> What is the sequence for enabling WPA2 shared key? When I enabled it on
>>>> both WHR-G54S, my remote WHR can't even ping itself (192.168.1.2).
>>
>>> With Bridge mode I have not been bale able to get WPA2-PSK to work. I
>>> had to go back to WPA-PSK (TKIP) to get it to talk to my main router.
>>> It could have been a limitation with my router, but I don't know.
>>
>> WPA doesn't work in bridge or WDS mode. Only in access point or
>> client mode. The best you can do in bridge or WDS mode is WEP.
>
>I currently have 2 routers working in Client Bridge mode with DD-WRT
>V23SP2 that are using WPA-PSK and TKIP encryption (I could not get AES
>working). Is this the client mode or the bridge mode you speak of? I
>guess I am confused at the difference between client mode and client
>bridge mode. I always use Client Bridge mode because I have more than
>one computer hooked to the device. WPA-PSK seems to be working just
>fine with that mode. In DD-WRT there are two different settings for WPA
>and WPA2. I use WPA-PSK not WPA2-PSK.

Jeff is referring to WDS mode (WPA no workee),
not client bridge mode (WPA works).

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>

In article <at9um2p9enhfirhov4c9tcufr8u6l0l54p@4ax.com>, on Thu, 30 Nov
2006 18:50:14 GMT, John Navas wrote:

>
> Jeff is referring to WDS mode (WPA no workee),
> not client bridge mode (WPA works).
>

The current documentation supplied with DD-WRT v23 SP2 for WDS says you
can use WPA, but not WPA2:


.

http://192.168.1.1/help/HWDS.asp



Do you know for a fact that the documentation is wrong?

--
Seth Goodman

I now have WPA-PSK TKIP working on my setup.

WHR-G54S #1 (192.168.1.1), AP mode, DHCP server, WPA-PSK TKIP
WHR-G54S #2 (192.168.1.2), Client-Bridge mode, WPA-PSK TKIP

Bryant Smith wrote:
> I currently have 2 routers working in Client Bridge mode with DD-WRT
> V23SP2 that are using WPA-PSK and TKIP encryption (I could not get AES
> working). Is this the client mode or the bridge mode you speak of? I
> guess I am confused at the difference between client mode and client
> bridge mode. I always use Client Bridge mode because I have more than
> one computer hooked to the device. WPA-PSK seems to be working just
> fine with that mode. In DD-WRT there are two different settings for WPA
> and WPA2. I use WPA-PSK not WPA2-PSK.

On Thu, 30 Nov 2006 14:12:07 -0500, Seth Goodman <seth_news@yahoo.com>
wrote in <MPG.1fd8f714208c5518989b88@newsgroups.comcast.net >:

>In article <at9um2p9enhfirhov4c9tcufr8u6l0l54p@4ax.com>, on Thu, 30 Nov
>2006 18:50:14 GMT, John Navas wrote:
>
>> Jeff is referring to WDS mode (WPA no workee),
>> not client bridge mode (WPA works).
>
>The current documentation supplied with DD-WRT v23 SP2 for WDS says you
>can use WPA, but not WPA2:
>
>

Quote:

>8. It is strongly recommended to enable Wireless Security. WPA Pre- >shared Key with AES is recommended as it is secure and easy. > >Note >WDS is only available in AP mode. Also Wireless encryption WPA2 and >Wireless network mode B-Only are not supported under WDS. >

.
>
>http://192.168.1.1/help/HWDS.asp
>
>Do you know for a fact that the documentation is wrong?

I didn't say anything about the documentation -- I reported only what
Jeff was saying.

As for the documentation, Google finds
<http://www.dd-wrt.com/wiki/index.php?title=WDS_Linked_router_network>
So Jeff was apparently misinformed. But note that WPA apparently works
with WDS _only_ with DD-WRT to DD-WRT.

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>

http://www.gilanet.com/ohlandl/NIC/w...#Client_Bridge

Though it is perfectly possible that WPA-PSK AES would work as well.

Louis Ohland wrote:
> I now have WPA-PSK TKIP working on my setup.
>
> WHR-G54S #1 (192.168.1.1), AP mode, DHCP server, WPA-PSK TKIP
> WHR-G54S #2 (192.168.1.2), Client-Bridge mode, WPA-PSK TKIP
>
> Bryant Smith wrote:
>> I currently have 2 routers working in Client Bridge mode with DD-WRT
>> V23SP2 that are using WPA-PSK and TKIP encryption (I could not get AES
>> working). Is this the client mode or the bridge mode you speak of? I
>> guess I am confused at the difference between client mode and client
>> bridge mode. I always use Client Bridge mode because I have more than
>> one computer hooked to the device. WPA-PSK seems to be working just
>> fine with that mode. In DD-WRT there are two different settings for
>> WPA and WPA2. I use WPA-PSK not WPA2-PSK.

On Thu, 30 Nov 2006 19:39:09 GMT, John Navas
<spamfilter0@navasgroup.com> wrote:

>>Do you know for a fact that the documentation is wrong?

No. I do know that WPA failed when I tried these configuration. There
may be others that work, but I do know that these don't work:
1. WAP54G to WAP54G (ver 3.2) in bridge mode. WEP only, no WPA.
2. WRT54G v1.1 to WRT54G v3 in WDS mode. DD-WRT v23 sp1 final
release. This was the latest at the time. WEP worked, but WPA and
WPA2 failed.
3. Same setup as above but both in "client bridge" mode. WEP worked,
but WPA did not. I forgot to try WPA2.

It's possible (and probable) that DD-WRT v23 SP2 is different. If so,
I stand corrected.

>As for the documentation, Google finds
><http://www.dd-wrt.com/wiki/index.php?title=WDS_Linked_router_network>

Scroll down the above URL to near the bottom under Apple Airport
Express. Quoting:
WPA/WPA2 encryption does not appear to work over WDS (but will work
when the Airport Express is configured in client mode - but in
client mode, the RJ45 connection is not usable)
Seems to confirm that WPA only works with WDS between DD-WRT routers.

>So Jeff was apparently misinformed. But note that WPA apparently works
>with WDS _only_ with DD-WRT to DD-WRT.

Possibly. I didn't know that WPA now works with WDS. It's never
worked when I tried it, but I can retest. It would really be nice if
it did.

Incidentally, I just noticed that v23 SP2 now had a "WPA Mixed" mode
that supports both WPA1 and WPA2 clients with both TKIP and AES
encryption. Nice.
WPA2 Mixed
This mode allows for mixing WPA2 and WPA clients. If only some
of your clients support WPA2 mode, then you should choose WPA2
Mixed. For maximum interoperability, you should choose WPA2
Mixed/TKIP+AES.


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558 jeffl@comix.santa-cruz.ca.us
# http://802.11junk.com jeffl@cruzio.com
# http://www.LearnByDestroying.com AE6KS

On Fri, 01 Dec 2006 05:06:45 GMT, Jeff Liebermann
<jeffl@comix.santa-cruz.ca.us> wrote in
<mbdvm2hglrfdv754q39n5qgg0kcv9tlabj@4ax.com>:

>Possibly. I didn't know that WPA now works with WDS. It's never
>worked when I tried it, but I can retest. It would really be nice if
>it did.
>
>Incidentally, I just noticed that v23 SP2 now had a "WPA Mixed" mode
>that supports both WPA1 and WPA2 clients with both TKIP and AES
>encryption. Nice.

Nice indeed. So why isn't some enterprising hardware vendor shipping a
product with DD-WRT installed? ;)

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>

John Navas wrote:
> On Fri, 01 Dec 2006 05:06:45 GMT, Jeff Liebermann
> <jeffl@comix.santa-cruz.ca.us> wrote in
> <mbdvm2hglrfdv754q39n5qgg0kcv9tlabj@4ax.com>:
>
>> Possibly. I didn't know that WPA now works with WDS. It's never
>> worked when I tried it, but I can retest. It would really be nice if
>> it did.
>>
>> Incidentally, I just noticed that v23 SP2 now had a "WPA Mixed" mode
>> that supports both WPA1 and WPA2 clients with both TKIP and AES
>> encryption. Nice.
>
> Nice indeed. So why isn't some enterprising hardware vendor shipping a
> product with DD-WRT installed? ;)
>

I saw someone selling WHR-G54S with DD-WRT already installed. But that
is not a manufacturer selling with DD-WRT installed.

In article <mbdvm2hglrfdv754q39n5qgg0kcv9tlabj@4ax.com>, on Fri, 01 Dec
2006 05:06:45 GMT, Jeff Liebermann wrote:

> >So Jeff was apparently misinformed. But note that WPA apparently works
> >with WDS _only_ with DD-WRT to DD-WRT.
>
> Possibly. I didn't know that WPA now works with WDS. It's never
> worked when I tried it, but I can retest. It would really be nice if
> it did.


changelog.txt on v23 SP2 lists a bug supposedly fixed in July:

0001456 [DD-WRT v23] WDS with WPA TKIP does not work

I hope you will retest, though - especially since changelog.txt lists
that bug as being fixed on two different dates. (I only have one router,
so I can't do it myself.) Being able to use WPA instead of WEP is an
important security feature.

--
Seth Goodman

Seth Goodman <seth_news@yahoo.com> hath wroth:

>changelog.txt on v23 SP2 lists a bug supposedly fixed in July:
>
>0001456 [DD-WRT v23] WDS with WPA TKIP does not work
>
>I hope you will retest, though - especially since changelog.txt lists
>that bug as being fixed on two different dates. (I only have one router,
>so I can't do it myself.) Being able to use WPA instead of WEP is an
>important security feature.

I'll try it hopefully this weekend. I'll need to bring home some
extra hardware and laptops from the office. It will be a mix of
Linksys and Buffalo, but all with DD-WRT v23 SP2 (09/15/06). I also
want to do a wireless thruput test per some previous long forgotten
promise.

My guess(tm) is that there's something fishy going on with WPA working
over WDS. It's my understanding that there's no easy way to assign
dynamic keys through a mesh matrix of WDS access points. I can see
how to kludge it with exactly one pair of access points, but not with
a network of AP's. Therefore, I want to have 3ea WDS access points
handy for testing.

http://www.tomsnetworking.com/2004/0...to_wds_bridge/
"Dynamically assigned and rotated encryption keys are not supported in
a WDS connection. This means that Wi-Fi Protected Access (WPA) and
other dynamic key assignment technology may not be used. Static WEP
keys only may be used in a WDS connection, including any STAs that
associate to a WDS repeating AP."

--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558