Reflash ASUS WL500GP V2 with DD-WRT

dd-wrt:192.168.1.1 255.255.255.0
wl500gp v2 192.168.1.2
255.255.255.0
wireless dhcp 192.168.1.135 255.255.255.0
ethernet dhcp
192.168.1.3 255.255.255.0
RJ45 cable connect pc to wl500gp-v2 lan1, wl500gp v2 wan to dd-wrt lan
ping 192.168.1.1 ok
brower 192.168.1.1 ok
ping 192.168.1.2 ok
brower 192.168.1.2 ok
ping google.com ok
WL-500gP V2's subnet ID and the subnet ID in WAN are the same

solution: instead plugging into router2 wan port, connect router1 lan an port to router2 lan port.

Installation

Connect to the router 2 @ http://192.168.1.1
disconnect this router from the main one or create a static ARP entry.
Open the Setup ; Basic Setup tab
WAN Connection Type : Disabled( ??could I assigned a static IP for it)
Local IP Address: 192.168.1.2 (i.e. different from primary router and out of DHCP pool)
Subnet Mask: 255.255.255.0 (i.e. same as primary router)
DHCP Server: Disable (also uncheck DNSmasq options)
(Recommended) Gateway/Local DNS: IP address of primary router (many things will fail without this)
(Optional) Assign WAN Port to Switch (visible only with WAN Connection Type set to disabled): Enable this if you want to use WAN port as a switch port
(Optional) NTP Client: Enable/Disable (if Enabled, specify Gateway/Local DNS above)
Save
Open the Setup ; Advanced Routing tab
(Optional) Change operating mode to: Router
Save
Open the Wireless ; Basic Settings tab
Wireless Network Name (SSID): YourNetworkNameHere
(Optional) Sensitivity Range: The max distance (in meters) to clients x2
Save
Open the Wireless ; Wireless Security tab
Note: Security is optional, but recommended! Clients must support whatever mode you select here.
(Recommended) Security Mode: WPA2
(Recommended) WPA Algorithm: AES
(Recommended) WPA Shared Key: ;8 characters
Save
Open the Services ; Services tab
(Optional) DNSMasq: Disable
(Optional) ttraff Daemon: Disable
Save
Open the Security ; Firewall tab
Uncheck all boxes except Filter Multicast
Save
Disable SPI firewall
Save
Open the Administration ; Management tab
(Recommended) Info Site Passw
ord Protection: Enable
Under routing select disabled
Apply Settings and connect Ethernet cable to main router via LAN-to-LAN uplink*

Notes:
To connect the WAP to the main router, you can probably use either a patch cable, straight-thru, or a crossover cable. Most DD-WRT capable devices can do auto-sensing so the cable type doesn't usually matter.
You can connect the WAP to the main router via LAN-to-WAN so long as you have assigned the WAN port to switch (see step 3).
There were three basic configuration changes you made to set up your router as a wireless access point.
Turn Off DHCP
If you did not turn off DHCP, when you plug your router into the network (after configuration), your WAP may provide IP addresses to clients on the wired network, and this may be inappropriate. Tracking down problems caused by multiple DHCP servers can be time-consuming and difficult.
Because its so important, it is worth repeating: Turn off DHCP before you continue!
Set the IP address of the LAN Interface
Immediately after turning off DHCP, while your PC still has the IP address the WAP gave you, set the LAN interface of the WAP to the IP address you want it to use, eg. if host router is 192.168.1.1, give WAP an IP of 192.168.1.2. Alternatively, you can use the instructions below to set the WAPs IP address via DHCP.
If you cannot connect to the WAP in order to set the LAN interface's IP address, it is probably because your computer no longer has an IP address on the same subnet. To get past this issue, simply set your computer's IP address and subnet to 192.168.1.8 and 255.255.255.0 respectively. (This assumes you are still using the default settings. If not, change the IP address and subnet as appropriate) You should now be able to point your browser at 192.168.1.1 (again assuming default settings).
LAN Uplink
There are two ways to connect your WAP to the LAN. You can either Uplink through one of the router's LAN ports, or use the WAN port that is normally connected to the cable/DSL modem.
LAN Uplink Through LAN Port
To complete the link between the two routers, connect a LAN port on the central router, to a LAN port on Linksys router (to be used as your WAP). You may need a crossover cable to do this, although many modern routers have an automatic polarity sensing. To test this, connect a standard ethernet cable between the two routers. If the LAN light comes on, the router has automatically switched the polarity and a crossover cable is not required.
LAN Uplink Through WAN Port
If you use your DD-WRT router as a WAP only, you may use your DD-WRT router's WAN port to connect it to your existing LAN. To do this, you need to disable the Internet Connection and "Assign WAN Port to Switch".
Normally, the router does Layer 3 IP routing. but by "Assigning WAN Port to Switch," your DD-WRT router will bypass that functionality and just pass on the Layer 2 ethernet packets from your wired network to the wireless network and vice versa.
Alternatively, if you have a router that supports assigning the WAN port to the switch:
Setup ; Basic Setup ; Internet Connection Type ; Connection Type = Disabled
Setup ; Basic Setup ; Network Setup ; WAN Port ; Assign WAN Port to Switch
you can connect the WAN port as your uplink to your main router. All this really buys you is an extra port (4 available instead of 3), but why not?
Roaming access

If you are installing additional Access Points to cover a broader area with Wi-Fi access, it is possible to allow clients to roam freely between them. The common method is to use the same SSID and Security settings on each access point.
Use a different channel on each AP. e.g. if you are in the US and installed two access points, use channels #1 and #11. Or if three access points, then use channels #1, #6, and #11 (setting the channels at least 5 apart should help keep interference between APs to a minimum). If you have a residential gateway with wireless turned on, and just one AP, then the same applies: each gets a different channel.
When using multiple Access Points, each one should be connected by LAN to LAN uplink as described above. They can even be attached to different switches within the same organization.
How To Use DHCP to Set the WAP's IP Address

Note: This step is optional. It is not required to set the WAP's IP address via DHCP. It can be made static, as shown above.
It is not possible to set the LAN interface to get its IP address via DHCP using the web configuration interface. You can, however, set your startup script to obtain an IP address.
Simply set your IP address to:
udhcpc -i br0 -p /var/run/udhcpc.pid -s /tmp/udhcpc -H test-wrt-wireless
hostname `nslookup \`ifconfig br0 | grep 'inet addr' |cut -f 2 -d ':'\` | grep 'Name:' | awk '{print $2;}' | cut -f 1 -d '.'`
if test `hostname` != `nvram get wan_hostname`; then
     nvram set wan_hostname=`hostname`;
     nvram set router_name=`hostname`;
     nvram commit;
fi
Only the first line is required if you don't want your WAP to set its name based on the IP address it gets. However, if you want to save a configuration file which will apply to several WAPs, that can be a handy feature.
It seems that in some cases, the /tmp/udhcpc link doesn't exist. in that case, prepend:
ln -s /sbin/rc /tmp/udhcpc
to your startup script.
[edit]Related Forum links

Secure remote management for a WAPInstallation

Connect to the router 2 @ http://192.168.1.1
disconnect this router from the main one or create a static ARP entry.
Open the Setup ; Basic Setup tab
WAN Connection Type : Disabled
Local IP Address: 192.168.1.2 (i.e. different from primary router and out of DHCP pool)
Subnet Mask: 255.255.255.0 (i.e. same as primary router)
DHCP Server: Disable (also uncheck DNSmasq options)
(Recommended) Gateway/Local DNS: IP address of primary router (many things will fail without this)
(Optional) Assign WAN Port to Switch (visible only with WAN Connection Type set to disabled): Enable this if you want to use WAN port as a switch port
(Optional) NTP Client: Enable/Disable (if Enabled, specify Gateway/Local DNS above)
Save
Open the Setup ; Advanced Routing tab
(Optional) Change operating mode to: Router
Save
Open the Wireless -> Basic Settings tab
Wireless Network Name (SSID): YourNetworkNameHere
(Optional) Sensitivity Range: The max distance (in meters) to clients x2
Save
Open the Wireless ; Wireless Security tab
Note: Security is optional, but recommended! Clients must support whatever mode you select here.
(Recommended) Security Mode: WPA2
(Recommended) WPA Algorithm: AES
(Recommended) WPA Shared Key: >8 characters
Save
Open the Services ; Services tab
(Optional) DNSMasq: Disable
(Optional) ttraff Daemon: Disable
Save
Open the Security ; Firewall tab
Uncheck all boxes except Filter Multicast
Save
Disable SPI firewall
Save
Open the Administration ; Management tab
(Recommended) Info Site Passw
ord Protection: Enable
Under routing select disabled
Apply Settings and connect Ethernet cable to main router via LAN-to-LAN uplink*

Notes:
To connect the WAP to the main router, you can probably use either a patch cable, straight-thru, or a crossover cable. Most DD-WRT capable devices can do auto-sensing so the cable type doesn't usually matter.
You can connect the WAP to the main router via LAN-to-WAN so long as you have assigned the WAN port to switch (see step 3).
[edit]Review

There were three basic configuration changes you made to set up your router as a wireless access point.
[edit]Turn Off DHCP
If you did not turn off DHCP, when you plug your router into the network (after configuration), your WAP may provide IP addresses to clients on the wired network, and this may be inappropriate. Tracking down problems caused by multiple DHCP servers can be time-consuming and difficult.
Because its so important, it is worth repeating: Turn off DHCP before you continue!
[edit]Set the IP address of the LAN Interface
Immediately after turning off DHCP, while your PC still has the IP address the WAP gave you, set the LAN interface of the WAP to the IP address you want it to use, eg. if host router is 192.168.1.1, give WAP an IP of 192.168.1.2. Alternatively, you can use the instructions below to set the WAPs IP address via DHCP.
If you cannot connect to the WAP in order to set the LAN interface's IP address, it is probably because your computer no longer has an IP address on the same subnet. To get past this issue, simply set your computer's IP address and subnet to 192.168.1.8 and 255.255.255.0 respectively. (This assumes you are still using the default settings. If not, change the IP address and subnet as appropriate) You should now be able to point your browser at 192.168.1.1 (again assuming default settings).
[edit]LAN Uplink
There are two ways to connect your WAP to the LAN. You can either Uplink through one of the router's LAN ports, or use the WAN port that is normally connected to the cable/DSL modem.
[edit]LAN Uplink Through LAN Port
To complete the link between the two routers, connect a LAN port on the central router, to a LAN port on Linksys router (to be used as your WAP). You may need a crossover cable to do this, although many modern routers have an automatic polarity sensing. To test this, connect a standard ethernet cable between the two routers. If the LAN light comes on, the router has automatically switched the polarity and a crossover cable is not required.
[edit]LAN Uplink Through WAN Port
If you use your DD-WRT router as a WAP only, you may use your DD-WRT router's WAN port to connect it to your existing LAN. To do this, you need to disable the Internet Connection and "Assign WAN Port to Switch".
Normally, the router does Layer 3 IP routing. but by "Assigning WAN Port to Switch," your DD-WRT router will bypass that functionality and just pass on the Layer 2 ethernet packets from your wired network to the wireless network and vice versa.
Alternatively, if you have a router that supports assigning the WAN port to the switch:
Setup -> Basic Setup -> Internet Connection Type -> Connection Type = Disabled
Setup -> Basic Setup -> Network Setup -> WAN Port -> Assign WAN Port to Switch
you can connect the WAN port as your uplink to your main router. All this really buys you is an extra port (4 available instead of 3), but why not?
[edit]Roaming access

If you are installing additional Access Points to cover a broader area with Wi-Fi access, it is possible to allow clients to roam freely between them. The common method is to use the same SSID and Security settings on each access point.
Use a different channel on each AP. e.g. if you are in the US and installed two access points, use channels #1 and #11. Or if three access points, then use channels #1, #6, and #11 (setting the channels at least 5 apart should help keep interference between APs to a minimum). If you have a residential gateway with wireless turned on, and just one AP, then the same applies: each gets a different channel.
When using multiple Access Points, each one should be connected by LAN to LAN uplink as described above. They can even be attached to different switches within the same organization.
[edit]How To Use DHCP to Set the WAP's IP Address

Note: This step is optional. It is not required to set the WAP's IP address via DHCP. It can be made static, as shown above.
It is not possible to set the LAN interface to get its IP address via DHCP using the web configuration interface. You can, however, set your startup script to obtain an IP address.
Simply set your IP address to:
udhcpc -i br0 -p /var/run/udhcpc.pid -s /tmp/udhcpc -H test-wrt-wireless
hostname `nslookup \`ifconfig br0 | grep 'inet addr' |cut -f 2 -d ':'\` | grep 'Name:' | awk '{print $2;}' | cut -f 1 -d '.'`
if test `hostname` != `nvram get wan_hostname`; then
     nvram set wan_hostname=`hostname`;
     nvram set router_name=`hostname`;
     nvram commit;
fi
Only the first line is required if you don't want your WAP to set its name based on the IP address it gets. However, if you want to save a configuration file which will apply to several WAPs, that can be a handy feature.
It seems that in some cases, the /tmp/udhcpc link doesn't exist. in that case, prepend:
ln -s /sbin/rc /tmp/udhcpc
to your startup script.
[edit]Related Forum links

Secure remote management for a WAP
There was an error in this gadget
There was an error in this gadget
There was an error in this gadget