On 6/19/06, Damir Perisa <[EMAIL PROTECTED]> wrote:
Saturday 17 June 2006 18:48, Kernel wrote:
| I'm not sure why, but I had issues with vpnc-0.3.3. I was never
| quite able to get it to set the route properly, so I've stayed
| with version-0.3.2 since it's always worked for me. I'm not a
| vpnc expert by any stretch, so maybe someone else can chime in
| with what might be the cause of the errors you're getting. Below
| are my files used with vpnc-0.3.2 in the event they may help.
| Sorry, I can't be of more help. I'll dig through some of my
| notes from when I set this up on my system to see if I come across
| anything else.
thanx for your info. i was now able to fix the error messages by
creating some dirs in /var but the tun-device is stil not being
generated successfully. i will try downgrading to see if this
helps... seems that this vpnc is not that trivial as it seems ;)
greetings,
Damir
--
Power, after love, is the first source of happiness.
-- Stendhal
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
In the vpnc-connect script I sent, I modified it to do a "modrpobe tun" in the beginning. This needs to be run as root (obviously). Do you get any errors when you run "modprobe tun" from the command line?
--
****************
jps
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
