VPN PPTP load on start and route all traffic DEBIAN 8
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
VPN PPTP load on start and route all traffic DEBIAN 8
Need some serious help for a very urgent situation involving PPTP protocol VPN in Debian 8 Jessie stable.
I recently became a paid VPN subscriber.
Using PPTP;
Is there a way to automatically route all traffic through ppp0? Im getting the vpn service killed (ip address goes back to normal unmasked state) whenever there is a power outage (modem reset) and there are alot of those where I live, Im going to get astabilizer and I need a software solution for the situation as well. Theres gotta be a way to route all traffic through the VPN route ppp0 . I tried adding persist and maxfail 0 to the pptp config file but it did not do what i wanted.
Heres my peer configuration file :
On a second note, its clear to add that I basically need a way to also auto load the line
pppd call blabla.net
and
route add default dev ppp0
on system startup by default so the computer does not use "Wired" connection ^at all^ when not through ppp0. Any other suggestion in the idea of not losing VPN anonymity ever due to hardware malfunction is greatly appreciated.
Is there a way to do this? Ive looked on the net and everything seems like its either from the nineties or can fry my pc , Im no debian expert, less than a year at linux
Any suggestions? Need it to use wired only if ppp0 is being used so if its no vpn, no connection at all period,
Sorry to diverge a little. If, I was in this situation, and assuming VPN connectivity (for secure communication) is all I was wanting, I think I'd be wanting to handle this VPN connectivity via a router eg using DD-WRT. Just an idea...
Sorry to diverge a little. If, I was in this situation, and assuming VPN connectivity (for secure communication) is all I was wanting, I think I'd be wanting to handle this VPN connectivity via a router eg using DD-WRT. Just an idea...
thanks for the help however this is just not feasable for my situation for various factors. and think about it, why use an external router when all it takes to do this is a couple commands in the terminal or editing some configuration file. then think about it when I have the proper configuration software-wise what am I going to do with the unnessesary peripheral?thx though
The router approach has the advantage that any device connecting to it will be protected by the VPN (not always possible using mobile devices for example). Anyway, I have seen script solutions online that test for VPN connectivity and retsart the VPN service whenever it is dropped for some reason. Good luck with finding a solution that works for you.
The router approach has the advantage that any device connecting to it will be protected by the VPN (not always possible using mobile devices for example). Anyway, I have seen script solutions online that test for VPN connectivity and retsart the VPN service whenever it is dropped for some reason. Good luck with finding a solution that works for you.
some script solutions would be great
thanks for expanding my mind though cause i didnt know about the router approach too bad its not it for me
Since Debian 8 is using systemd by default, you may want to investigate creating a custom service to get the PPTP tunnel started after the network is up. It's not as hard as it might appear, but you will want to do some reading first
the thing just doesnt work.
the /var/lib/rcconf/services file doesnt even exist.
How you make debian run the things in init.d ?
That would very much take care of the first half of the problem. However the second half, the dont use wired unless vpn, is still up in the air completely. The suggestion to use a cron job to ping every minute just wont do it for me bc im using a lot of cron jobs and dont want to clog that up besides , theres gotta be the real way to do it that just doesnt use the wired at all unless its ppp0.
Since Debian 8 is using systemd by default, you may want to investigate creating a custom service to get the PPTP tunnel started after the network is up. It's not as hard as it might appear, but you will want to do some reading first
Thanks a lot however the ping approach from http://www.jamescoyle.net/how-to/968...ux-pptp-client is just too risky for me, im not allowing the possibility of "it was not up, lets restart it" because in that half a minute there would definately be a leak of my real address
Just so people are informed - here's an article describing a security flaw relating to WebRTC (browser vulnerability) and why running VPN connectivity via the router is considered a superior option...
Update: We've been talking to a number of people in the security community about this issue, and after those conversations, we're not confident that configuring your VPN at the router level is any more effective (or rather, terribly effective at all) than blocking WebRTC at the browser. While we still recommend setting up your VPN at the router level for a number of reasons (outlined below), as far as this issue is concerned, right now, we'd suggest that you use one of the browser add-ons mentioned above while we all conduct more research into the root cause—and surefire remediation for it.
If you want a more surefire way to protect yourself beyond installing add-ons and making tweaks to your browser every time you install or update, there is a more permanent method. Run your VPN at your router instead of on your computer directly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
