Active Topics

 



Notices


Reply
Thread Tools
Posts: 50 | Thanked: 37 times | Joined on Nov 2009
#11
Just so you know you're not the only one that needs more VPN acccess options... I could use an IPSEC VPN client for the n900.
 
Posts: 2,152 | Thanked: 1,490 times | Joined on Jan 2006 @ Czech Republic
#12
OK, got it working to the point that pptp tunnel is up and i can ping the other end.

kernel modules : http://fanoush.wz.cz/maemo/modules-2...02-pptp.tar.gz
insmod order: slhc, ppp_generic, ppp_async, sha1_generic, ppp_mppe

pppd : http://fanoush.wz.cz/maemo/ppp_2.4.4...sso4_armel.deb
pptp-linux: http://fanoush.wz.cz/maemo/pptp-linux_1.7.2-1_armel.deb
__________________
Newbies click here before posting. Thanks.

If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.

Last edited by fanoush; 2009-12-11 at 22:39.
 

The Following 8 Users Say Thank You to fanoush For This Useful Post:
jiiv's Avatar
Posts: 124 | Thanked: 47 times | Joined on Aug 2008 @ Northern DFW
#13
Excellent, I'll give it a shot this weekend and let you know how it turns out.
__________________
Useful links for newcomers: New members say hello, New users start here, Community subforum, Beginners' wiki page, Maemo5 101, Frequently Asked Questions (FAQ)
NOTE: Most users should avoid the extras-testing and extras-devel app repositories.
I'm not really a Maemo/smartphone expert, but I can usually find my way around a *nix system. If I somehow manage to help you out, thanks are appreciated.
 

The Following User Says Thank You to jiiv For This Useful Post:
Posts: 2,152 | Thanked: 1,490 times | Joined on Jan 2006 @ Czech Republic
#14
I have used /usr/sbin/pptpsetup script to generate my configuration but had to edit it first and disable some checking inside (it is perl script) since there is no strings command and wc has no --lines argument. Also copying all modules to /lib/modules/2.6.28-omap1/ and running depmod -a helped with some check. Then "pppd call <nameofmytunnel>" worked for me. It also helped to try first with
"pppd call <nameofmytunnel> logfd 2 nodetach debug dump"
as per http://pptpclient.sourceforge.net/howto-diagnosis.phtml
__________________
Newbies click here before posting. Thanks.

If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.

Last edited by fanoush; 2009-12-11 at 23:21.
 

The Following User Says Thank You to fanoush For This Useful Post:
Posts: 1,224 | Thanked: 1,763 times | Joined on Jul 2007
#15
I hope you don't mind my encroaching on your thread.

I tried to use these modules and pppd for connecting to a 3G phone as a modem.

I setup rfcomm correctly (running rfcomm connect and then communicating with the phone over /dev/rfcomm2 appears to work).

Then I set ppp configuration files as in 6.2 here: http://www.xs4all.nl/~ernstagn/GPRS-...S-HOWTO-6.html and ran

pppd call gprs nodetach debug

The N900 reboots with the last line from pppd being
Connect: ppp0 <--> /dev/rfcomm2

Any ideas what the problem might be, or how to debug it?
 
Posts: 134 | Thanked: 91 times | Joined on Nov 2009 @ Imperial College London
#16
Just to let everyone know that this is now working perfectly for me after playing with a few settings. Getting the routing right without iproute installed was proving a bit tricky, but luckily Christoph has made it available (as described in this thread).

If anybody is having problems connecting to a similar VPN I'd be happy to make suggestions based on my adventures!

Thanks again Fanoush for all of your help.

Jan
 
Posts: 6 | Thanked: 3 times | Joined on Dec 2009 @ Germany
#17
Originally Posted by Big Phat Jan View Post
Just to let everyone know that this is now working perfectly for me after playing with a few settings. Getting the routing right without iproute installed was proving a bit tricky, but luckily Christoph has made it available (as described in this thread).

If anybody is having problems connecting to a similar VPN I'd be happy to make suggestions based on my adventures!
Thanks again Fanoush for all of your help.
Jan
I'm having problems to get it working.....
After installing pptp-linux and ppp I can't ssh to my device anymore. I can't even ping it although it still has a wifi connection and ip-adress (still can browse the web from the device).

after loading the modules I called 'pptpsetup' to set up a tunnel.
that gives me an error like 'mppe_compress not found' or something similar.

so could you be kind and provide a simple step-by-step guide to get everything working ?
I'd really appreciate this as I'm sort of desperate to have vpn to my network at work... ;-)

regards,chris
 
Posts: 134 | Thanked: 91 times | Joined on Nov 2009 @ Imperial College London
#18
Originally Posted by svart View Post
I'm having problems to get it working.....
After installing pptp-linux and ppp I can't ssh to my device anymore. I can't even ping it although it still has a wifi connection and ip-adress (still can browse the web from the device).

after loading the modules I called 'pptpsetup' to set up a tunnel.
that gives me an error like 'mppe_compress not found' or something similar.

so could you be kind and provide a simple step-by-step guide to get everything working ?
I'd really appreciate this as I'm sort of desperate to have vpn to my network at work... ;-)

regards,chris
I can't help with your first problem as I never experienced it, but a more detailed step-by-step may help you anyway. Here goes!

First, download the kernel modules and debs from Fanoush in post 12.

Then in an xterm type the following commands ($ and # are the normal user and root prompts respectively, don't type them!):

Become root (you'll need rootsh installed from the extras repository):

Code:
$ sudo gainroot
Then install pptp_linux and ppp:

Code:
# dpkg -i pptp-linux_1.7.2-1_armel.deb
# dpkg -i ppp_2.4.4rel-osso4_armel.deb
Extract the kernel modules from the tar.gz file downloaded from Fanoush:

Code:
# tar -zxvf modules-2.6.28-200903102-pptp.tar.gz
This will create two directories called "drivers" and "crypto" which contain the loadable kernel modules (LKMs) you need to load. Copy these to the standard place that LKMs live (your path may vary slightly):

Code:
# cp ./drivers/net/ppp_async.ko /lib/modules/2.6.28-omap1/
# cp ./drivers/net/ppp_generic.ko /lib/modules/2.6.28-omap1/
# cp ./drivers/net/ppp_mppe.ko /lib/modules/2.6.28-omap1/
# cp ./drivers/net/slhc.ko /lib/modules/2.6.28-omap1/
# cp ./crypto/sha1_generic.ko /lib/modules/2.6.28-omap1/
As a note you could achieve the same in one line with the following:

Code:
# cp ./drivers/net/ppp_async.ko ./drivers/net/ppp_generic.ko ./drivers/net/ppp_mppe.ko ./drivers/net/slhc.ko ./crypto/sha1_generic.ko /lib/modules/2.6.28-omap1/
Change to this directory, update your module dependancy file, and load the modules in the order suggested by Fanoush:

Code:
# cd /lib/modules/2.6.28-omap1/
# depmod -a
# insmod slhc.ko
# insmod ppp_generic.ko
# insmod ppp_async.ko
# insmod sha1_generic.ko
# insmod ppp_mppe.ko
You don't need to use pptpsetup to set up your tunnel, but it does make life easier. However, as Fanoush mentioned, it uses the strings command and the --lines argument for wc, which aren't available in perl on the N900. These are present in the sub which checks whether MPPE is enabled, which is on line 192 of the script. I just edited the script to remove the check, there's probably a more elegant solution, but there we go!

Open the file /usr/sbin/pptpsetup in your text editor of choice. Then you can either search for "strings", or go straight to line 192. There's a sub called Check_MPPE_in_pppd. I just commented out all the lines from the sub except for "return 1;". As I say, not the most elegant solution and one to bear in mind if you use pptpsetup in the future!

Here's how the sub looks after the edit:

Code:
sub Check_MPPE_in_pppd {
#    my $command = q/strings `which pppd`|grep -i mppe|wc --
#    my $answer  = `$command`;                              
#    if ($answer > 0) {                                     
        # ok!                                               
        return 1;                                           
#    } else {                                               
#        return 0;                                          
#    }                        
}
That done, run pptpsetup with your settings. If you use a domain you need to make sure that you add two slashes after it (or two before your username). If you have previously set up a tunnel I would remove it and start again if you're having problems, or I imagine it would be enough to just set it up with a slightly different name.

pptpsetup sets up the files you require in /etc/ppp/ but doesn't attempt to start the tunnel unless you add the start option - don't do this yet!

You can start the vpn with:

Code:
# pppd call <tunnelname> logfd 2 nodetach debug dump
Which gives you much more information. Hopefully this will report an established tunnel (although you probably won't be connected through it). If not you may need to play with your options.

For reference, here are all of my options, as found in my /etc/ppp/peers/<tunnelname> file (you can pass them on the command line every time you start the tunnel if you want, but that's obviously a bit more work!). Your server is probably set up differently so you may need to change these.

lock
noauth
nobsdcomp
nodeflate
name DOMAIN//username
require-mppe-128
noipdefault
usepeerdns
defaultroute
replacedefaultroute
persist

Assuming you have a connection, you now need to set up your routing to use it. This doesn't work by default because we are missing /sbin/ip. You could probably fix this with the "route" command, but the easiest way is to install iproute by following Christoph's instructions in this post.

And restart it. At this stage my VPN was working perfectly. Hopefully yours will be too!

Call it with just:

Code:
# pppd call <tunnelname>
once it's working to avoid the log output. To stop the connection, use:

Code:
# killall pppd
To check whether it's running or not, use:

Code:
# route
which may also help you to troubleshoot your current connection issues.

This is probably unclear in many places so feel free to seek clarification!

Cheers,
Jan

Last edited by Big Phat Jan; 2009-12-21 at 13:44. Reason: better description of pptpsetp edit.
 

The Following 18 Users Say Thank You to Big Phat Jan For This Useful Post:
Posts: 6 | Thanked: 3 times | Joined on Dec 2009 @ Germany
#19
Excellent, it's running now !!

Thank you very much for your help !

Regards,
Chris
 
Posts: 16 | Thanked: 1 time | Joined on Dec 2009 @ Paris, France
#20
Hi,

I don't know much about VPN but I was interested in this thread for my willing to connect to my laptop from my N900 using BT.

I created a rfcomm interface which seems ok to connect but I was missing pppd to create the IP link.

I followed your instructions but the connection vanishes just after I launch the two pppd instructions.

It was something like :

$ pppd /dev/rfcomm0 192.168.1.1:192.168.1.2 noauth # on PC
$ pppd /dev/rfcomm0 192.168.1.2:192.168.1.1 noauth # on N900

What's wrong ?

I'd rather not use the maemo-pc-connectivity package (I tried and it didn't work anyway).

Last edited by azorni; 2009-12-23 at 12:47.
 
Reply

Tags
vpn pptp mppe n900


 
Forum Jump


All times are GMT. The time now is 11:38.