OpenWrt Forum Archive

Topic: Routing VPN trafic to Internet

The content of this topic has been archived on 20 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Post #1
hugo
4 Dec 2005, 22:38

Hello,

I'm new to this forum and to openWrt, but I was an experienced user of Oleg's firmware, before moving to openwrt because of the user support and the working PPTP solution.

I'm using white russian RC4 on my WL-HDD, and set up pptpd as described by the HOWTO. I can connect using my pocket pc client, and ping station on the lan, or use the ressources on my WL-hdd.

The problem is that I would like to use this VPN to have access to all port via my ADSL connection: In many company I work in, port are locked by firewall. I want to connect to my home using a pptp link (usually allowed), then use this connection to check my email using port not available inside the company network.

All doc I can find is about adding route to get access to a specific lan, but none describe the route to add to the ip-up script so I can be redirected to internet via the other end of the tunnel (not the client side obviously, as it is in the corporate network)

The network would be like this:

PPC client ---- PPTP VPN ----- company firewall ------ internet ------- wl-hdd(openwrt WR RC4) pptp link----- 192.168.0.1
                                                                                                              |
                                                                                                          internet

So I would make no use of the internet connectivity on the company side.
Is it an easy answer, or do you need all my network config files?

Thanks

(Last edited by hugo on 4 Dec 2005, 22:39)

Post #2
LSU_guy
2 Jan 2006, 12:31

Hugo - my pptp client can connect to the internet using the router's internet connection. Please follow the howto to setup the pptpd connection

http://wiki.openwrt.org/PPTPDHowto

The only thing different that you would have to do is in the routing rule.
Substitute this line "iptables        -A forwarding_rule -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT" for "iptables        -A forwarding_rule -s 192.168.1.0/24 -j ACCEPT".

Essentially all we are doing is allowing all your client requests to be forwarded everywhere.

The discussion might have continued from here.