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.
I've recently "migrated" from FC4 to FC5 ("migrated" being in quotes because I didn't upgrade; I backed up the old install and did a fresh install). In FC4, I used VPNC to log into my school's network and had no problems using it in the past. So I installed it on FC5, copied over the exact same config file from my FC4 backup to my FC5 tree and attempted to run vpnc. It says it started in the background, which "ps aux" confirms. However, once VPNC starts, I can't use anything network-wise. That is, I still have an IP, but I can't even ping anything (let alone open pages in a browser). So the VPN doesn't work, and it also breaks everything else that did work. Killing vpnc/running 'vpnc-disconnect' fixes everything, but I still can't connect to my school's network.
Any ideas what the problem might be? I'm suspecting a routing issue, but I'm anything but a pro when it comes to routing.
well run vpnc from a command line and add "--debug 3" to the command line... see if there areany useful messages there. to be honest there probably aren't as it's a very obscure cryptic output, but worth a go. Personally I experience a very similar scenario, but it's the fault of my adsl router which stops passing ipsec traffic every so often until i reboot it. could it be something outside of the local environment?
Thanks for the response. You're not kidding about cryptic output! I even tried "--debug 2" but I didn't see anything that looked wrong--certainly no errors or warnings.
That's a good guess about there being a routing issue, but I've tried using this on campus (we have to log in through VPN even on campus so not just anybody uses our wireless). I got the exact same results at school as I did here at home, remotely.
ok, what if we go a bit simpler... could the default vpnc script simply be making everything route incorrectly? what about the output of "route"? check that the default gateway makes sense etc. also you are pinging by IP i take it? vpnc normally overwrites /etc/resolv.conf, something that really annoys me and i delete that function straight out of the script. also what i changed my default script to do is only route known networks via the vpn, and not take my default route. I can't remember the exact syntax, but the variables are listed at the top of the example script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.