[SOLVED] vpnc on Slackware 14.2 is bringing up network configuration dialog each time
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
vpnc on Slackware 14.2 is bringing up network configuration dialog each time
Greetings!
Running both the SBo and non-SBo versions of vpnc causes Slackware 14.2 to display the network configuration dialog every time, even though the network has already been set up. (please see attached screenshot of the dialog). Thinking maybe it was a one-time thing, I went through the network setup screens, only for it to appear again after I finished the setup.
After I Ctrl + C out of the setup dialog, then vpnc connects properly. This is a pain because scripting this blocks execution when the network setup dialog comes up (in a hidden shell) every time.
Is there anything I need to check for to prevent the network dialog from coming up when vpnc is run?
Thank you in advance,
Will B
Last edited by willbprog127; 12-15-2016 at 02:16 PM.
Reason: Removed incorrect vpnc version
I have no idea what is happening, but have you tried grepping the source to see if it is calling it directly? Or have you tried removing/renaming the script to prevent the program from calling it up?
/var/log/setup/setup.netconfig
Or have you tried contacting the SlackBuild maintainer to see if they're run into the issue at all? Or contact the actual developers of vpnc?
Or have you tried contacting the SlackBuild maintainer to see if they're run into the issue at all? Or contact the actual developers of vpnc?
I contacted the SBo maintainer a week or two ago and they have not replied.
I have tried compiling the upstream version of vpnc and the problem still exists. I have compiled upstream's version on other platforms and distros and it does not do this.
On my 14.2 (current) box vpnc from SBo runs without a problem. I have never seen that network dialog.... Have you set up vpnc correctly?
Thanks for the info.
I have set up vpnc properly. My config has not changed for years. My config works fine on every other Linux and BSD distro, just not Slackware. My network was properly set up at installation time and I have no other issues, only this one.
Thanks for the info.
My config works fine on every other Linux and BSD distro, just not Slackware. My network was properly set up at installation time and I have no other issues, only this one.
Well during my upgrade to 14.2/current, my vpnc-config was not changed either; combined with your other distros having no problem with this vpnc set-up it seems that something in your Slackware network set-up prevents calling vpnc directly or that the manner in which you call the vpnc-tunnel is somehow compromised. That network dialog only pops-up when /sbin/netconfig is called; something I do not think is needed once your network connections are set-up. Can you find out where in your vpnc-route /sbin/netconfig gets called?
Can you find out where in your vpnc-route /sbin/netconfig gets called?
I don't have a 'vpnc-route' file, however I do have a 'vpnc-script' file. netconfig is mentioned on line 128:
Code:
if [ -r /etc/openwrt_release ] && [ -n "$OPENWRT_INTERFACE" ]; then
. /etc/functions.sh
include /lib/network
MODIFYRESOLVCONF=modify_resolvconf_openwrt
RESTORERESOLVCONF=restore_resolvconf_openwrt
elif [ -x /sbin/resolvconf ] && [ "$OS" != "FreeBSD" ]; then # Optional tool on Debian, Ubuntu, Gentoo - but not FreeBSD, it seems to work different
MODIFYRESOLVCONF=modify_resolvconf_manager
RESTORERESOLVCONF=restore_resolvconf_manager
elif [ -x /sbin/netconfig ]; then # tool on Suse after 11.1 # <<<<<<<<<<<<<<<<<<<<<<<< netconfig MENTIONED HERE <<<<<<<<<<<<<<<<<
MODIFYRESOLVCONF=modify_resolvconf_suse_netconfig
RESTORERESOLVCONF=restore_resolvconf_suse_netconfig
elif [ -x /sbin/modify_resolvconf ]; then # Mandatory tool on Suse earlier than 11.1
MODIFYRESOLVCONF=modify_resolvconf_suse
RESTORERESOLVCONF=restore_resolvconf_suse
else # Generic for any OS
MODIFYRESOLVCONF=modify_resolvconf_generic
RESTORERESOLVCONF=restore_resolvconf_generic
fi
This has resolved the problem (although it's very hackish)
Code:
#if [ -r /etc/openwrt_release ] && [ -n "$OPENWRT_INTERFACE" ]; then
#. /etc/functions.sh
#include /lib/network
#MODIFYRESOLVCONF=modify_resolvconf_openwrt
#RESTORERESOLVCONF=restore_resolvconf_openwrt
#elif [ -x /sbin/resolvconf ] && [ "$OS" != "FreeBSD" ]; then # Optional tool on Debian, Ubuntu, Gentoo - but not FreeBSD, it seems to work different
#MODIFYRESOLVCONF=modify_resolvconf_manager
#RESTORERESOLVCONF=restore_resolvconf_manager
#elif [ -x /sbin/netconfig ]; then # tool on Suse after 11.1
#MODIFYRESOLVCONF=modify_resolvconf_suse_netconfig
#RESTORERESOLVCONF=restore_resolvconf_suse_netconfig
#elif [ -x /sbin/modify_resolvconf ]; then # Mandatory tool on Suse earlier than 11.1
#MODIFYRESOLVCONF=modify_resolvconf_suse
#RESTORERESOLVCONF=restore_resolvconf_suse
#else # Generic for any OS
MODIFYRESOLVCONF=modify_resolvconf_generic
RESTORERESOLVCONF=restore_resolvconf_generic
#fi
I don't have a 'vpnc-route' file, however I do have a 'vpnc-script' file. netconfig is mentioned on line 128:
What is the source of this 'vpnc-script', as I do not think it has a Slackware oriented origin? What you could try is to make sbin/netconfig un-executable in your Slackware (i.e. chmod -x as root) and see whether this helps to bypass your problem on Slackware. Possibly Suse has a similarly named program in sbin that could be needed for setting up vpnc on SUSE but this has nothing to do with SLackware.
Quote:
So it appears that the SBo needs to patched to use the right network config program instead of thinking Slackware is Suse.
No, as that script has nothing to do with Slackware -as it seem s to me- but everything with Suse; and SBo is for Slackware users....
[...] that script has nothing to do with Slackware -as it seem s to me- but everything with Suse; and SBo is for Slackware users....
I think we have our wires crossed. When that part of the script finds 'netconfig' it assumes that Slackware is actually Suse, which is obviously incorrect. With ponce's change to that line of code, it now does not assume that I'm running Suse, and doesn't try to run 'netconfig'. It falls through to the appropriate part of the condition testing and uses that instead.
Last edited by willbprog127; 12-27-2016 at 02:23 PM.
It was not clear from your post what other linux-es you were running. If you look into it a bit more my proposed work-around would do the same although netconfig on slackware wouldn't work. Ponce's solution is making your script unworkable on Suse. If you happen to run that distribution while using that same script your vpnc-problem might happen there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.