DD-WRT Client Bridge
Our Fios internet connection is on the opposite end of the house from my home office. This weekend, I got a wireless bridge running from the Fios connection to the office. This will allow me to use my Cisco desk phone over a VPN connection to work.
Here’s how I currently have it configured:
Verizon Fios wifi router -wired-> Cisco ASA 5505 -wired-> Linksys WRT54GL -wifi-> Linksys WRT54G V.3
Both Linksys routers are running the latest version of DD-WRT. Installing the new firmware went smoothly on both routers. The one catch on the WRT54GL is I didn’t let it sit and finish booting, as the wiki instructs. You really have to give it a few minutes.
The WRT54GL is configured as an AP, and the WRT54G is set to be in client bridge mode. The ASA is plugged in to one of the switch ports on the WRT54GL. The result is, any devices connected to the WRT54G will be on the subnet hosted by the ASA.
The only downside I can find thus far is the DHCP and DNS (for the VPN only?) are not forwarded to clients that are physically connected to the WRT54G. When I configure my desktop to have a static IP that is served by the ASA, I have connectivity. When I try DHCP, I don’t get an IP. From what I can find on the net, some people claim it works for them, while there are descriptions of why it doesn’t work from others. I’ll dig deeper into this at some other time.
Since my work laptop connects to the WRT54GL via wifi, DHCP works fine there. And DNS does as well, although I’m assuming the reason I get DNS resolution for hosts on the extranet and not for hosts served by the VPN is my desktop is not on the work domain, and my laptop is.
Thanks to the DD-WRT team for producing a very impressive open source product!