[SOLVED] Having difficulties to connect to the internet with a USB-UMTS-Modem
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A connection is established. This seems not to be the problem. It is shown with ifconfig as ppp0.
I cannot ping 8.8.8.8, at first I supposed that is due to filtering icmp packages by the provider. But this is not the case. When I have a connection here with Windows I can ping 8.8.8.8
So I think either the connection does not work or I have a firewall working (but didn't configure one).
Your last post shows that you have made a successful connection. The problems you describe suggest a problem with DNS. What is the content of /etc/resolv.conf after the connection is made? Can you ping the DNS servers at 212.23.97.2 and 212.23.97.3?
no I cannot ping any IP-adress, I don't think that it is a DNS-Problem, because when I ping a name, the IP-adress of the host is shown, maybe they are in the DNS-cache, but I did ping adresses which I did not visit since several month and had an IP-adress although. So my idea is that DNS works, but routing does not work.
I found an example routingtable for a ppp-connection in a network-book, I'll try that out.
Anyway, thanks for your help, any suggestions are appreciated.
sakis3g does not work. It tries to use wvdial and crashes then, as I wrote earlier wvdial has a bug and exits.
The problem seems to be that I have the correct settings, but sometimes I don't have enough signalstrength in order to receive a correct configuration.
And when I have a connection, I suppose I have a routing-problem.
I've read much about GSM and PPP recently, I don't have a solution yet, but it seems that the newsgroup comp.protocols.ppp is very valuable regarding to this.
I didn't read this thread but I'll read it carefully. My problem with sakis3g was that it uses wvdial which yet does not work correctly with Slackware-current (32bit and 64bit as well). I will at first have to rebuild wvstreams with the patches ponce posted above and then rebuild wvdial.
i believe that this really is a routing issue, although the output of "/sbin/route" that you posted looks quite similar to mine (except that i have a lo interface set up). wvdial as well as sakis3g will just run pppd sooner or later.
looking at the sakis3g script, there are at least two snippets which might interest you:
firstly the pppd-options:
Code:
pppdoptions="${PPPD_OPTIONS}"
[ "a${pppdoptions}" = "a" ] && pppdoptions="modem crtscts -detach defaultroute dump noipdefault usepeerdns usehostname ktune logfd 2 noauth name sakis3g lock maxfail 3"
if [ "a${PPPD_PEERS}" != "a" ]; then
if [ -d "${PPPD_PEERS}" ]; then
if [ -f "${PPPD_PEERS}/sakis3g" ]; then
debug "Found peers file %s.\n" "${PPPD_PEERS}/sakis3g"
pppdoptions="-detach dump logfd 2 name sakis3gpeer maxfail 3 call sakis3g"
fi
fi
fi
you might try to pass these to pppd
and secondly the post-connection stuff, especially this one:
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Posts: 781
Rep:
Been following this since my earlier suggestions, and apologies if they have not worked. Anyhow, I have been trying to figure out what might be happening (or not) and I have no idea if this is related or not, but running 64-current, I too am unable to connect with my Huwaei 3g Modem, but, using the same modem on the 32 bit edition, I have no problem at all.
Can't for the life of me figure out why. Is it possible that the hardware itself will only work under a 32bit environment?
...
... I have no idea if this is related or not, but running 64-current, I too am unable to connect with my Huwaei 3g Modem, but, using the same modem on the 32 bit edition, I have no problem at all.
Can't for the life of me figure out why. Is it possible that the hardware itself will only work under a 32bit environment?
I have a Subnotebook Lenovo Thinkpad x100e with Slackware-current (32bit) and a Notebook (Samsung) with Slackware64-current. As far as I can tell, the issues are the same, I tried all chat-scripts and pppd-configurations I wrote on both computers and the errormessages and debug-output respectively were almost the same.
Also I have Installed Win 7 on both machines, 64bit on the Laptop 32bit on the subnotebook, the stick works with both.
The errormessages regarding wvdial are also the same for both, 32 and 64bit.
Well, now I've veryfied that it works with Slackware-current and with Slackware64-current as well.
my umts.chat file
Code:
#/etc/ppp/umts.chat
ABORT "BUSY"
ABORT "NO CARRIER"
ABORT "NO ANSWER"
'' AT
TIMEOUT 5
OK 'AT+cgdcont,"IP","internet.eplus.de","0.0.0.0"'
TIMEOUT 5
'' AT
TIMEOUT 5
OK ATDT*99#
TIMEOUT 5
I copied the resolv.conf file (which is created in /etc/ppp/ when the connection is established to /etc and added nameserver 8.8.8.8
Also I did what san wrote
Code:
route add default gw 10.64.64.64
That was all. The problem was obviously that I did not really know how this line in the chat-file
Code:
OK 'AT+cgdcont,"IP","internet.eplus.de","0.0.0.0"'
had to look like. It was not clear if it was needed, but if one omits the line and additionally uses "local" instead of "modem" in the umts-file, there is a local echo working and it looks like a connection is established and the authentication worked, but this is not the case.
One question remains. Regarding to the chat-file I pushed the PIN to the stick via the commandline
Code:
echo "AT+CPIN=XXXX" > /dev/ttyUSB0
which works (XXXX is the PIN), but one has to push the pin to the stick only once when the stick is connected to the computer. If I put the line for the PIN into the chat-file, the file fails when the PIN is already given to the stick. Question: does anyone know, if it is possible in the chat-file to ask if the PIN is already commited to the stick? regarding to some documentation I read a line
Code:
AT+CPIN?
should work, but I had no success because I don't know the syntax for an optional argument.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.