Topic: Remote Access from WAN

[Brave Dave]

I don't play with 47, just 1723

The 691 error - actually quite good, at least you are hitting the server

Have you updated your server

uname -a
Linux k 2.6.9-55.EL #1 Wed May 2 13:52:16 EDT 2007 i686 i686 i386 GNU/Linux

Check
rpm -qa | grep "kmod-p"
kmod-ppp-smp-1.0.2-2.2.6.9_55.EL
kmod-ppp-1.0.2-2.2.6.9_55.EL

note that kernel modules match, I think it's smeupdates-testing to get the correct kernel modules

maybe the us-robotics router doesn't pass the VPN pass-through - lot of variables there, maybe you may need to configure it in bridge mode and put your pppoe setup directly into the sme box, not sure, Routre needs to pass GRE through

VPN seems to just work for me, I use netgear routers by choice, but have success with many others.

Just looking at your original post, 192.168.1.0/24 was your internal network

you should be using 2 network cards with a different network on inside and outside

say [wanip] [dmz net] [internal net]

say [wanip] [192.168.5.0/24] [192.168.1.0/24]

[ronaldson40]

uname -a
Linux k 2.6.9-55.EL #1 Wed May 2 13:52:16 EDT 2007 i686 i686 i386 GNU/Linux

Check
rpm -qa | grep "kmod-p"
kmod-ppp-smp-1.0.2-2.2.6.9_55.EL
kmod-ppp-1.0.2-2.2.6.9_55.EL

I am getting these

[root@datahub ~]# uname -a
Linux datahub 2.6.9-55.ELsmp #1 SMP Wed May 2 14:28:44 EDT 2007 i686 i686 i386 GNU/Linux

[root@datahub ~]# rpm -qa | grep "kmod-p"
kmod-ppp-smp-1.0.2-1.2.6.9_42.0.10.EL
kmod-ppp-1.0.2-1.2.6.9_42.0.10.EL

[ronaldson40]

One more thing I have this page on USR. Is it because of this I am not getting VPN?

Purchase Features
In order to enable the router to establish VPN connections, you need to purchase the VPN feature from U.S. Robotics.

 


If you’ve already purchased the VPN feature, please press the Unlock button so that the router can unlock it. The router will contact the U.S. Robotics Web site in order to confirm your purchase. Please note that the router does not send any personal information. The only information it sends is the MAC address of the device.



Back to the Status page

[Stefano]

On router, port forward ports 1723 and 47 to 192.168.1.2 (SME)

it is not port 47, it's protocol 47 GRE

HTH
Stefano

[ronaldson40]

So this protocol should be enabled on the router or the SME server?

[ronaldson40]

I tried changing the router to another one... tested the port forwards.... I am still getting this GRE error.... and Error 691

Will a SME update help or is it some problem of the modem...?

[ronaldson40]

hi... i had not enabled vpn access to the users i.e why i was getting error 691 in windows xp

But now I am getting this error
"Error 734: The PPP link control protocol was terminated"
and this is my server log

Jul  9 16:47:08 datahub pptpd[7709]: CTRL: Starting call (launching pppd, opening GRE)
Jul  9 16:47:08 datahub pppd[7710]: Plugin radius.so loaded.
Jul  9 16:47:08 datahub pppd[7710]: RADIUS plugin initialized.
Jul  9 16:47:08 datahub pppd[7710]: pppd 2.4.4 started by root, uid 0
Jul  9 16:47:08 datahub kernel: divert: not allocating divert_blk for non-ethernet device ppp0
Jul  9 16:47:08 datahub pppd[7710]: Using interface ppp0
Jul  9 16:47:08 datahub pppd[7710]: Connect: ppp0 <--> /dev/pts/2
Jul  9 16:47:08 datahub pppd[7710]: MPPE required, but kernel has no support.
Jul  9 16:47:08 datahub pppd[7710]: Connection terminated.
Jul  9 16:47:08 datahub pppd[7710]: Connect time 0.0 minutes.
Jul  9 16:47:08 datahub pppd[7710]: Sent 0 bytes, received 0 bytes.
Jul  9 16:47:08 datahub pptpd[7709]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
Jul  9 16:47:08 datahub pptpd[7709]: CTRL: Reaping child PPP[7710]
Jul  9 16:47:08 datahub kernel: divert: no divert_blk to free, ppp0 not ethernet
Jul  9 16:47:08 datahub pppd[7710]: Exit.

I have also searched the forums and came across several posts on the same MPPE required issue.. But most of them refer to the bug tracker and there are no resolutions.
http://pptpclient.sourceforge.net/howto-diagnosis.phtml#mppe_rbkhns
I also refered the above site...but did not help...

Could you suggest any technique to solve it....

[ronaldson40]

Could you point me to some post or link where I can re-enable the MPPE support for the kernel....
I tried with a VMWARE image of SME 7.1 without the updates... I was able to estalish the Vpn connection...but since my production server is SME 7.1.3...i think the vpn support is broken...

[Stefano]

Could you point me to some post or link where I can re-enable the MPPE support for the kernel....
I tried with a VMWARE image of SME 7.1 without the updates... I was able to estalish the Vpn connection...but since my production server is SME 7.1.3...i think the vpn support is broken...

- boot with 'old' kernel (2.6.9-42.3  AFAIR)
- rpm -e --nodeps kernel-2.6.9-55 kernel-smp-2.6.9-55 (check rpms' name)
- disable CENTOS* repositories
- yum update: it should inslaa last sme kernel 2.6.9-42.10
- signal-event post-upgrade; signal-event reboot

it should work

HTH

ciao
Stefano

[Stefano]

Could you point me to some post or link where I can re-enable the MPPE support for the kernel....
I tried with a VMWARE image of SME 7.1 without the updates... I was able to estalish the Vpn connection...but since my production server is SME 7.1.3...i think the vpn support is broken...

- boot with 'old' kernel (2.6.9-42.3  AFAIR)
- rpm -e --nodeps kernel-2.6.9-55 kernel-smp-2.6.9-55 (check rpms' name)
- disable CENTOS* repositories
- yum update: it should inslaa last sme kernel 2.6.9-42.10
- signal-event post-upgrade; signal-event reboot

it should work

HTH

ciao
Stefano

[Stefano]

Could you point me to some post or link where I can re-enable the MPPE support for the kernel....
I tried with a VMWARE image of SME 7.1 without the updates... I was able to estalish the Vpn connection...but since my production server is SME 7.1.3...i think the vpn support is broken...

- boot with 'old' kernel (2.6.9-42.3  AFAIR)
- rpm -e --nodeps kernel-2.6.9-55 kernel-smp-2.6.9-55 (check rpms' name)
- disable CENTOS* repositories
- yum update: it should inslaa last sme kernel 2.6.9-42.10
- signal-event post-upgrade; signal-event reboot

it should work

HTH

ciao
Stefano

[ronaldson40]

Will this be fixed in the next update of SME?

Any how I am presently using the old SME 7.1 kernel installed on Vmware for VPN on my network till the issue is fixed in the next update....