VPN Problem

[boxst]

This is driving me crazy. I can't get VPN to work. It *used* to work, but I've configured new firmware and haven't tested it for a while.

I am now using Merlin's beta (although it did the same on the new Asus firmware). I set up the default PPTP VPN, put a username/password and checked the other settings as default.

I can connect from my Mac, have set the 'send all traffic' but once it is connected I get an IP address and no traffic. It is most bizarre. I have set the DNS on the Mac VPN to opendns to see if that is the problem (it isn't).


Any suggestions appreciated.

 

[RMerlin]

Make sure that the IP block you allocate to the VPN is in the same subnet as the LAN at home. Ideally have DHCP allocate a smaller range, for example 192.168.1.2 through 192.168.1.99, then have the VPN configured to allocate 192.168.1.100 to 192.168.1.109.

 

[boxst]

Thank you, that still didn't work.

Most odd.

 

[kfmfe04]

fwiw, just to get it working, all I did was
1. Enable the PPTP VPN server
2. Add username/password
3. Configure a block of IPs as Merlin suggested

in OSX,
I just used these settings
1. PPTP
2. Server: a public IP name
3. DNS: a private, internal DNS
4. username/password

and it all worked.

This is using STOCK firmware 3.0.0.4.260, if you want to just get it working first...

I think one of these days, I will play with Merlin's build, dd-wrt, Tomato, or some other build, but I need to make sure I can always rollback to a working/stable FW easily before I try.

 

[RMerlin]

I think one of these days, I will play with Merlin's build, dd-wrt, Tomato, or some other build, but I need to make sure I can always rollback to a working/stable FW easily before I try.

You can. Just make sure you flash the right DD-WRT version if you decide to try that one, because flashing the wrong version can lead to a semi-brick, requiring a serial cable to fix.