Howto setup Microsoft VPN with gpptp (4.12 - 4.31) + (5.xx)

[jafadmin]

jafa, once you fix PL's issue, would the correct command then be:
route add -net 192.168.0.0 netmask 255.255.255.0 ppp0

Ken

That route will give you access to: 192.168.0.1 thru 192.168.0.254 (254 addresses)

route add -net 192.168.0.0 netmask 255.255.0.0 ppp0

will give you access to: 192.168.0.1 thru 192.168.254.254 (65,533 addresses)

[I Have a New Puppy]

Understood finally about the whole subnet thang, thanks.

To access addresses 192.168.2.1 through 192.168.2.254
(which would cover my VPN's DHCP IPs) would be:

route add -net 192.168.2.0 netmask 255.255.255.0 ppp0


_________
Where any of my M$ route print data helpful?
Do you want the whole table?

Can at least browser traffic be forced through VPN via proxy settings?

Thanks,
Ken

[jafadmin]

Where any of my M$ route print data helpful?
Do you want the whole table?

Can at least browser traffic be forced through VPN via proxy settings?

Thanks,
Ken

1. No, I don't need to see any more route tables.

2. If there is a proxy server on the subnet you are connecting to over VPN, then you can set that in your browser and get to the web.

[jafadmin]

One important note.

I have not been able to assign a default route to a pptp vpn tunnel in the puppy implementation of ppp.

If your network admins assume you can set the default route to the VPN tunnel, there will be issues. You will need them to tell you the networks inside their company that you need to reach and set the routes to them after connecting.

I'm working on trying to find out what the underlying problem is with this.

I have been testing Barry's latest version of puppy (Woof Alpha 9) and the problem with the default route seems to be gone in that version. As more info becomes available we'll let you know.

[I Have a New Puppy]

What's the latest on all this, please?
Does the newer Puppy VPN work?
Does the code have the answer to fix 4.21, or must I install the new Puppy?

Thanks!

[jafadmin]

This version of gpptp works fine except that you cannot assign the default route through the vpn. This appears to be a problem with all 4.xx puppy versions. Puppy versions based on "Jaunty" don't have this problem. If you want to be able to set the default route through your vpn then I recommend using one of the jaunty based puppys.

Other than that one difference, this enhanced version of gpptp will work with either.

The inability to set a default route through a vpn has nothing to do with the gpptp app. It's a limitation of the "ppp" and "route" utilities in the standard puppy kernels.

I hope this clears it up a little ...

[jafadmin]

I have compiled a new version of gpptp for puppy 5.28. It's available in my top post.

VPN on the lucid kernel is much smoother and you don't need to worry about the route assignments as much. It will automatically route all traffic (default route) throuth the VPN connection.

You can start the gui and connect, then kill the gui. When you restart it, it will know you have an active VPN session already running, and offer you a button to disconnect. When you disconnect via the gui it fixes up your routes and DNS.

Good Luck!

[disciple]

Can you please provide the source?
Thanks.