Topic: VPN configuration assistance please

[turtle2472]

How can I give rep points around here?  I'd love to give a cookie to all those who helped me fix my VPN issue but I can't figure out how to do it. 

[pfloor]

How can I give rep points around here?  I'd love to give a cookie to all those who helped me fix my VPN issue but I can't figure out how to do it. 

Sorry, only Global Moderators, Dev Team and Admins are allowed to do that.

[turtle2472]

Sorry, only Global Moderators, Dev Team and Admins are allowed to do that.

Oh, well I hope they get passed out then.

[turtle2472]

I'm having a challenge again. 

Code: [Select]

[root@lenny ~]# grep -i pp*pd /var/log/messages
Jul 12 02:59:20 lenny esmith::event[2971]: expanding /var/service/wan/pppoe.pppd.conf 
Jul 12 03:05:46 lenny pptpd[5536]: CTRL: Starting call (launching pppd, opening GRE)
Jul 12 03:05:46 lenny pppd[5537]: Plugin radius.so loaded.
Jul 12 03:05:46 lenny pppd[5537]: RADIUS plugin initialized.
Jul 12 03:05:46 lenny pppd[5537]: pppd 2.4.4 started by root, uid 0
Jul 12 03:05:46 lenny pppd[5537]: Using interface ppp0
Jul 12 03:05:46 lenny pppd[5537]: Connect: ppp0 <--> /dev/pts/0
Jul 12 03:06:16 lenny pppd[5537]: Modem hangup
Jul 12 03:06:16 lenny pppd[5537]: Connection terminated.
Jul 12 03:06:16 lenny pppd[5537]: Exit.
[root@lenny ~]# rpm -qa kernel*
kernel-2.6.9-67.0.4.EL
kernel-2.6.9-55.0.6.EL
kernel-2.6.9-55.0.9.EL
kernel-2.6.9-55.0.12.EL
kernel-2.6.9-67.0.7.EL
kernel-utils-2.4-13.1.105
kernel-2.6.9-55.0.2.EL
kernel-2.6.9-67.0.1.EL
warning: only V3 signatures can be verified, skipping V4 signature
[root@lenny ~]# rpm -qa kmod*
kmod-slip-1.0-2.2.6.9_67.0.7.EL
kmod-ppp-1.0.2-2.2.6.9_67.0.7.EL
kmod-appletalk-1.0-2.2.6.9_67.0.7.EL
warning: only V3 signatures can be verified, skipping V4 signature

Now to see what to do about it this time.  Any help would be greatly appreciated.   I get the same error messages when trying to connect as before.  Something about not being able to negotiate the connection.

[turtle2472]

turtle2472

You can select the correct kernel at startup when the appropriate screen is displayed (ie a list of kernels), and I think that selection remains permanently changed. It's only on for a few seconds so be quick.

Otherwise login as root & do
pico -w /boot/grub/grub.conf

CAREFULLY make any necessary changes eg assuming the first listed kernel is what you want then change the line to read.
default=0
Ctrl o (to save)
Ctrl x (to exit)

then reboot.

Never mind, I got impatient and decided to try this again.  It worked.  default=2 was the state when I found it and I changed it to 0.  all is fine now.

So why does this or how does this mix up happen?  Am I the only one effected by it or are other SME users too?  Is there something I can do differently to make sure this mixup doesn't happen again?