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 <(E-Mail Removed)> 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 (E-Mail Removed)
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
<(E-Mail Removed)> wrote in
<(E-Mail Removed)>:

>Louis Ohland <(E-Mail Removed)> 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
> <(E-Mail Removed)> wrote in
> <(E-Mail Removed)>:
>
>> Louis Ohland <(E-Mail Removed)> 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 <(E-Mail Removed)> 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 (E-Mail Removed)
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:xx8: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 <(E-Mail Removed)> 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 <(E-Mail Removed)> 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 (E-Mail Removed)
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 <(E-Mail Removed)> 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 <(E-Mail Removed)> 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.
>>
>>