Bridge mode

gbalbach · EVDO Newbie Joined: 16 Oct 2007 Posts: 8

Hello everyone,

Does anyone know of a way (with any firmware) to put the WRT54G3G-ST into bridge mode? I am trying to do this:

Put the w54g3g-st into bridge mode with a sprint wireless card then have a netgear fvs338 behind it (lan port on linksys -> wan port on netgear) then have the FVS338 do a site to site vpn to a sonicwall 2040 at another location.

Thanks in advance...

rlw · Posted: Tue Oct 16, 2007 7:08 pm Post subject:

gbalbach · EVDO Newbie Joined: 16 Oct 2007 Posts: 8

Thanks for the tips, I tried what you suggested. I can establish the VPN connection to the remote sonicwall from the netgear that is behind the wrt54g3g-st but I can't do anything...maybe I need to open some ports on the netgear...in the sonicwall logs it says that the remote peer doesnt support nat traversal. I have nat traversal turned on in the sonicwall advanced options (enhanced version of the firmware). I since the netgear fvs338 supposedly supports nat traversal I figured it was because I was going through the linksys...?

rlw · Posted: Wed Oct 17, 2007 7:21 am Post subject:

gbalbach · EVDO Newbie Joined: 16 Oct 2007 Posts: 8

Trying to ping anything across the vpn doesnt work, but I can connect to the sonicwall from a PC with the sonicwall vpn client and it works/can ping particular machines without problem. The part that fixed it/let me get the connection working was the DMZ part. Thanks again for that, I'll dig more into the netgear...

rlw · Posted: Wed Oct 17, 2007 8:20 am Post subject:

I'm not sure what your LAN (inside the WRT) looks like, but if you can use the Sonicwall client on your PC to talk to the remote LAN through the client, it might just be a routing issue on your LAN.

When you use the Sonicwall client, it probably changes your default route to the virtual IP it gets as a result of creating the connection.

When you try to use the Netgear, it's just another device on your LAN, and is probably not configured in your PC to be a route to the remote net.

Here's an example:

Let's say your local net is 192.168.1.x, your WRT is 192.168.1.1, and is the default route before you try setting up the tunnel either with the Netgear or the SW client software. 192.168.1.1 would be your gateway.

Let's also assume the network on the other side is 10.1.1.x. When you run the SW client, it is assigned 10.1.1.99 as it's end of the connection, 10.1.1.55 as the far end, and it also updates your routing table to make 10.1.1.55 as your default gateway. All is well with the world.

When you use the Netgear, assume it's LAN side IP (inside your network) is 192.168.1.2. It connects, establishes the tunnel, but your PC still thinks its default gateway is 192.168.1.1 (the WRT).

What you may need to do is add a persistent route to get to the 10.1.1.x network on your PC, something like:

gbalbach · EVDO Newbie Joined: 16 Oct 2007 Posts: 8

Thank you very much for the info, I will check it out!

gbalbach · EVDO Newbie Joined: 16 Oct 2007 Posts: 8

Well I checked out that you suggested and apparently there is something else wrong with this setup. Even though the vpn tunnel connects, the sonciwall logs say that the peer doesn't support nat traversal...I think that is why I can't hit anything across the connection but I know the netgear fvs338 supports traversal...I am guessing the linksys is having problems passing the info...shame, I will keep trying but if anyone has any other tips to try let me know...

rlw · Posted: Wed Oct 17, 2007 7:52 pm Post subject: