Posted: Mon Aug 09, 2010 19:40 Post subject: Windows server router wirelessly connected to WRT54GL
Anyone have any ideas on this? I'm running BS 13525 STD on a WRT54GL v1.1 in AP wireless mode. The router IP is 192.168.0.1/24. I wish to connect a Windows server 2003 RRAS server as a second router to the WRT54GL. The RRAS server has 2 NIC's: 1 connected to the WRT54GL is 192.168.0.3 and the other is 10.10.10.1 (mask /24).
I have added a static route to the WRT54GL as follows:
dest LAN = 10.10.10.0
subnet mask = 255.255.255.0
gateway = 192.168.0.3
interface = LAN & WLAN
When the RRAS router is "wired" directly to a LAN port on the WRT54GL, I can ping both 192.168.0.3 and 10.10.10.1 from the WRT54GL and get replies as expected.
But when the RRAS router is "wirelessly" connected to the WRT54GL, attempts to ping 10.10.10.1 fail. (Pinging 192.168.0.3 works).
Any ideas? Since the static route interface is LAN & WLAN, shouldn't behaviour be the same?
Posted: Thu Aug 12, 2010 4:26 Post subject: wirelessly connected LAN router (no NAT)
Doesn't anyone have any idea or suggestion on this? I'm attaching a diagram to better explain the scenario and what works and doesn't work. In a nutshell, I'm trying to route to the other side of a simple LAN router (no NAT) using a static route on the primary router. When the LAN router is wired to the WRT54GL, it works. When wirelessly connected, it doesn't work.
Any ideas? Please?
WRT.jpg
Description:
static route for a wirelessly connected LAN router (no NAT)
Joined: 06 Jun 2006 Posts: 3763 Location: I'm the one on the plate.
Posted: Thu Aug 12, 2010 5:54 Post subject: Re: Windows server router wirelessly connected to WRT54GL
ghall wrote:
I'm running BS 13525 STD on a WRT54GL v1.1 in AP wireless mode. The router IP is 192.168.0.1/24. I wish to connect a Windows server 2003 RRAS server as a second router to the WRT54GL.
I see two problems already. First, a WRT54GL in AP mode will not route packets.
Second, if you re-configure it as a router then you will need to perform a DUAL WAN modification, and that is a non-standard mod that you can find here in these forums.
ghall wrote:
The router IP is 192.168.0.1/24.
Third, that is not a router, and fourth, 192.168.0.1/24 is not an IP address.
Thanks GeeTek. At least now I know that what I'm trying to do will not / cannot work in AP mode. I'll do a search in the forums for DUAL WAN to see what I can find. I'd still like to route packets over the WLAN if possible.
>>192.168.0.1/24 is not an IP address
You're right, it's incorrectly stated as a network. I was just being lazy and using CIDR notation to specify 24-bit subnet mask "and" 192.168.0.1 address.
By the way, sorry for the large pic -- I should have previewed before submitting
Joined: 06 Jun 2006 Posts: 3763 Location: I'm the one on the plate.
Posted: Thu Aug 12, 2010 18:01 Post subject:
ghall wrote:
At least now I know that what I'm trying to do will not / cannot work in AP mode.
DD-WRT is quite flexible and has other wireless modes that will allow routing. The dual wan part may be tricky, but still may be possible by using virtual wireless interfaces.
I need to digest your drawing some more to better understand what you are trying to do.
More details on what I'm ultimately trying to achieve...I have a WRT54GLv1.1 (primary router) configured in AP mode and a WRT54Gv8 configured as a client bridge. There is a vmware esx server wired to the CB router and is accessible by wireless clients connected to the primary router AP. The virtual machines running on the esx server are on the same subnet (192.168.0.0/24) as the primary router and accessible by the wireless clients over the bridge. That's all good.
I have a VM on the esx server that is a software router (Windows Server RRAS), one vNIC on the the 192.168.0.0/24 network and the other vNIC on a 10.10.10.0/24 subnet (private subnet on the esx server) and a couple of VM's on the 10.10.10.0/24 subnet. The RRAS router works fine, but I can't route packets to it from the WRT54GL over the WLAN (cause of AP mode). Note that if I wire the esx server to the primary router (WRT54GL) instead of the CB router, packets route to it just fine. Just not over the WLAN. Therein lies my problem.
Joined: 06 Jun 2006 Posts: 3763 Location: I'm the one on the plate.
Posted: Fri Aug 13, 2010 2:14 Post subject:
ghall wrote:
Note that if I wire the esx server to the primary router (WRT54GL) instead of the CB router, packets route to it just fine. Just not over the WLAN.
I've drawn what I think you have described. Your drawing shows the Client Bridge device to have a WAN and a LAN IP. In Client Bridge mode there is no WAN or WAN IP. Client mode would have both WAN and LAN with the wireless being WAN.
Properly configured, a client bridge radio will pass any subnet from wireless to wired. At least it did in older DD-WRT versions. If it does no longer, or if you would prefer to use a more proper wireless bridging protocol then set up a WDS bridge between the wireless radios. WDS is a layer 2 bridge and is not concerned with layer 3 subnets. It functions essentially as would a CAT5 cable, and will bridge the LANs and WLANs of the two radios together.
Terrific ! WDS works like a charm...I can now route to the esx server. Thanks GeeTek for your advice. FYI...I'm using r14929 on both routers. No issues yet.
One question...is it possible (and safe) to disable AP mode on the secondary router so that it doesn't accept wireless client connections?
Doesn't anyone have any idea or suggestion on this? I'm attaching a diagram to better explain the scenario and what works and doesn't work. In a nutshell, I'm trying to route to the other side of a simple LAN router (no NAT) using a static route on the primary router. When the LAN router is wired to the WRT54GL, it works. When wirelessly connected, it doesn't work.
