but now this leads me to a question.. prior to posting [my problem] i went to /usr/sbin in console and tested 'ip' without any parameters and it echo'd the usage for this command. it appeared that the command was valid, which is what led me to believe it was a permission issue.

now tho, i'm a bit confused on /usr/sbin, /usr/bin, /sbin, and /bin as all have commands. how did you know that /bin/ip would work? is this normal on slack-based machines? to use /bin vs one of the others? if /usr/sbin/ip had not existed i could completely understand, but since it acted like it was a valid command, that's where it loses me.

sorry if i'm not explaining my question well, just wanting to grasp the concept.

thanks again for the assistance in fixing my problem.

I found this article and it makes a little bit more sense.. doesn't completely de-muddle the situation, just somewhat explains why it's confusing to begin with.

it didn't matter which directory i was in when i attempted to call 'ip.' it (the system) was using /bin/ip due to it having priority ranking in $PATH. i incorrectly took this to mean that /usr/sbin/ip was working, when in fact it was /bin/ip that was responding without me realizing.

this then explains that the program was calling /usr/sbin/ip when the actual command the system uses is /bin/ip.

Thanks for this thread, and solution. I travel a lot, So, openvpn is VERY important to me. It would be a "deal breaker" for Puppy if I couldn't have made it work.

In case someone else reaches this thread, I just wanted to add some additional information which may be useful. I use "Precise" instead of "Slacko", but this may work for other versions as well.

I had the same problem described above. I used the same command to link the directories. However, when I ran openvpn, my log file showed that I was not finding "/bin" ...... when it SHOULD have shown that I was not finding "/bin/ip". In other words, it was missing "ip", even though I knew it was there.

The solution to this? I uninstalled openvpn, then re-installed it. Problem solved! It connected!

By the way, I had already tested that everything (certs, keys, configs) worked on another linux machine. So, I knew that the only issue I was having had to be with how I set things up on Puppy..

Took a lot of time making working OpenVPN, now with Slacko 5.5. I remade symlinks to Busybox and put the command ln as suggested on previous posts. Now i can use Private Internet Access (my current ISP blocks PPTP/L2TP access)

However, Gadmin GUI is too silly to understand some values that PIA or other VPN services doesn't provide, so i should use openvpn by the old way (command). Exists plans to simplify this on Slacko 5.6?

And, believe me, it was a long time coming and took a long way to get to this point.

Since I now have the means to access this sort of thing more readily, I intend to enhace my computer skillz with far greater rapidity.

So let's get to it....

I hit this OpenVPN problem also, and it was due to a 'missing link'. Or, the client was looking for the ip command in the wrong place. It wants /usr/sbin/ip. My Slacko 5.6 k 3.4.52 has only /sbin/ip. So symlink it such that the former is channeled to the latter. Of course, /sbin/ip is just a link to busybox. This description seems to be a bit at odds with what has been said above, but I am just describing what has been my experience. Also, this message sequence did help me figure out my problem. Thanks, all!

Hey, 'chillinfart', I got a fairly recent OpenVPN client from the mirrors.slackware.com repositiories, and LZO from either there or SlackBuilds. This worked ok, but I tried to compile LZO and OpenVPN 2.3.10. LZO compiled, but did not seem to make the liblzo2.so.2 file but instead a file of a similar name. So, OpenVPN could not get to the lzo lib that it needed. OpenVPN itself would not get past the configure stage due to a lacking libpam....I could not find it anywhere....it only seemed to exist for alternate *nixes like BSD and such...any ideas on how to address these problems? You seem to have a handle on this based on your messages here.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum