Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: vinnie on April 05, 2011, 07:40:07 PM
-
i have 2 intertet key and would want to succeed to connect at least one of the two that to short I will go outside for a few time.
One is huawey E173 and other is MBD-220HU (http://www.mobidata.cn/en/product/productshow.asp?id=188), of this I possess a handbook but i don't have capacity to understanding it
http://dl.dropbox.com/u/10544567/Mobidata%20Hspa%20IMPOSTAZIONI%20PER%20Linux.pdf
-
I managed to switches mode to one of two modems with usb_modeswitch.
I compile wvdial, but I can not get it to work:
This is my /etc/wvdial.conf:
[Dialer Defaults]
Phone = *99#
Username = wind
Password = wind
Stupid Mode = 1
Dial Command = ATD
Modem = /dev/ttyUSB2
Baud = 460800
Init1= ATZ
Init2 = AT+CGDCONT=1,"IP","internet.wind"
ISDN = 0
Modem Type = Analog Modem
PPPD = /usr/local/sbin/pppd
Carrier Check = noBut, after i ran wvdial:
root@box:~# wvdial
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT+CGDCONT=1,"IP","internet.wind"
AT+CGDCONT=1,"IP","internet.wind"
OK
--> Modem initialized.
--> Sending: ATD*99#
--> Waiting for carrier.
ATD*99#
ERROR
--> Invalid dial command.
--> Disconnecting at Sat Apr 9 14:54:15 2011
root@box:~#
I hope someone can help me
-
What happens if you use ATDT instead of ATD?
Also try atdt
-
Yes, but this has not resolved the situation.
Actually I did several tests by changing the file wvdial.conf
To this I would ask if you could help me understand if the problem is different.
Maybe even trying to bypass with pppd.
I are forced to hurry because in a week, if not solve, the only way to connect is to use windows, and I do not like :'(
-
vinnie: I take it you have checked that your service provider is indeed using '*99#' as the number to dial.
-
've tried several, but in the end I kept that because it is the same as used on windows, where I connect
-
@vinnie: First up I need to state that I don't own a USB 3G modem and my knowledge is therefore only of rather theoretical nature, furthermore I don't really know the Italian language. Nevertheless I had a bit a look around the web page of your provider (which I assumed to be "wind.it"). I found theses generic instructions (http://telefonino.libero.it/documenti/ALCATEL/-%20PARAMETRI%20GENERICI/internet_cod_201424.pdf). Just briefly looking at things like the screenshots I can't say that I spotted anything I've would have done differently. I assume that you've already tried out the various variations of the "phone" number (e.g. "*99***1#", and maybe even "*99***9#" or "*99**1*1#").
In the "good old days" (like 10-15 years ago) when analog modems were the norm my typical troubleshooting step at this stage (i.e. after the modem initailisation) would have been to just listen for a dial tone (e.g. by using 'ATDT' without any number). And as the next step to just listen whether I could get the modem to dial out at all (e.g. by using a single digit like 'ATDT 9'). But alas I'm afraid that won't work with your type of modem any more.
As a generic comment: Make sure that you are using the correct combination of 'modem', 'init' strings and 'phone' suitable for your modem and provider. As soon as you get a 'CONNECT ...' it should be merely an issue with the PPPD parameters (e.g. username/password) that you'll have to sort out.
-
I think the problem lies somewhere else
few times ago i tried to give command with minicom (I can not do the same with cutecom, seems to repeat the input instead uutput):
Welcome to minicom 2.4
OPTIONS: I18n
Compiled on Jun 22 2010, 21:33:10.
Port /dev/ttyUSB2
Press CTRL-A Z for help on special keys
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
AT
OK
ATZ
OK
AT+CGDCONT=1,"ip","internet.wind"
OK
ATD*99#
ERROR
Since I am not convinced, as the guide i posted, I would try to switch the modem with AT commands instead modeswtich, But the guide says to refer to "network manager" to know the name of the device to be set in minicom.
Now I ask, after i insert the usb dispositive, how I can know its device (alias /dev/tty*)?
@maro= thanks for your attention, in pdf that you are finding are apn and number, correspond to those that I already use, but it's good to have a verification, username & password is ininfluent.
For several days this part can assure that I'm doing so many tests (with ppp pppsetup umtsmon eznet/xeznet sakis wvdial...) not last the test with minicom.
Tomorrow I'll try with ubuntu to see if is a linux problem or not.
-
Now I ask, after i insert the usb dispositive, how I can know its device (alias /dev/tty*)?
Hmmm, I would have thought that there will be some sort of message in the 'dmesg' output.
So what I would do in this case is to boot without the USB device, take a 'dmesg' snapshot (e.g. via dmesg > d1), connect the device in question, and check what has changed (e.g. via dmseg | diff -U 0 d1 -). Likewise if the device requires a firmware file, or a kernel module to be recognised or properly enabled that should also show up in the 'dmesg' output in some form or another.
-
before doing the test with dmesg and minicom I did that with ubuntu, and in ubuntu works.
This is wvdial.conf that work in ubuntu:
[Dialer Defaults]
Dial Command = ATD
Init1 = at
Init2 = AT+CGDCONT=1,"IP","internet.wind"
Modem Type = Analog Modem
ISDN = 0
New PPPD = yes
Carrier Check = no
Phone = *99#
Modem = /dev/ttyUSB2
Username = wind
Password = wind
Baud = 460800
Stupid Mode = 1
This gave me an opportunity to understand a little more and repeat.
Now the modem as connected with wvdial in tinycore, but I can not use this connection for Internet.
tc@box:/mnt/sda6/wvdial-1.61/wvdial-1.61$ sudo wvdial
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: at
at
OK
--> Sending: AT+CGDCONT=1,"IP","internet.wind"
AT+CGDCONT=1,"IP","internet.wind"
OK
--> Modem initialized.
--> Sending: ATD*99#
--> Waiting for carrier.
ATD*99#
CONNECT 7200000
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Mon Apr 11 20:41:40 2011
--> Pid of pppd: 9526
--> Using interface ppp0
--> pppd: H&d[08]`#d[08]
--> pppd: H&d[08]`#d[08]
--> pppd: H&d[08]`#d[08]
--> pppd: H&d[08]`#d[08]
--> pppd: H&d[08]`#d[08]
--> pppd: H&d[08]`#d[08]
--> local IP address 164.132.123.57
--> pppd: H&d[08]`#d[08]
--> remote IP address 10.64.64.64
--> pppd: H&d[08]`#d[08]
--> primary DNS address 193.70.152.25
--> pppd: H&d[08]`#d[08]
--> secondary DNS address 193.70.192.25
--> pppd: H&d[08]`#d[08]
Wireshark a program that recommended by one friend, identifies the new network as ppp0, now the question is this:
how do I set this connection to be used by tinycore? (in ubuntu it automatically)
Please answer me, I feel, are close to conclusion
-
Have you looked into output of 'route'?
-
I do not know what it is! (I also searched route in /var/log)
-
Well, the 'wvdial' log in reply #9 indicates to me that you had a connection. To expand reply #10 a bit I'd suggest to share with us the output of: ifconfig -a ; cat /etc/resolv.conf ; route (obviously after you ran 'wvdial').
Next (potential) simple troubleshoouting steps:
(1) Try to ping the 'local IP address' (e.g. 164.132.123.57 in the example from reply #9, which is a public IP address belonging to Infostrada).
(2) Try to ping a well-know public server (i.e. outside of the realm of your ISP), e.g. ping 8.8.8.8
(3) Test the DNS (e.g. via nslookup google.com)
(4) Test a HTTP transmission (e.g. via wget -qO- http://example.com)
This step-by-step approach should allow you to pinpoint what works and what is faulty (and again you might want to share those results here, if you have problems).
-
I do not know what it is! (I also searched route in /var/log)
route
;)
Though I hope maro made that already clear in the meantime
-
Ok, preface:
the connection that I use (and allows me to write at this time) is a adsl with router alice, therefore dhcp.
To make test of maro I unplugged the ethernet cable and start wvdial.
The first thing to say and that the file /etc/resolv.conf does not automatically change, and then to validate the remainder of the test, I manually changed with the two dns provided by output of wvdial.
resolv.conf after change:
tc@box:/$ cat /etc/resolv.conf
nameserver 193.70.152.25
nameserver 193.70.192.25
Here are the other tests:
tc@box:/$ ifconfig -a
dummy0 Link encap:Ethernet HWaddr 9A:55:B6:B7:E6:F2
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 20:CF:30:6E:C8:D2
inet addr:192.168.1.173 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:63052354 errors:0 dropped:0 overruns:0 frame:0
TX packets:77894 errors:0 dropped:0 overruns:0 carrier:6
collisions:0 txqueuelen:1000
RX bytes:143971588 (137.3 MiB) TX bytes:8767633 (8.3 MiB)
Interrupt:30
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:896 errors:0 dropped:0 overruns:0 frame:0
TX packets:896 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:99248 (96.9 KiB) TX bytes:99248 (96.9 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:164.132.96.39 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:118 (118.0 B) TX bytes:154 (154.0 B)
wlan0 Link encap:Ethernet HWaddr 48:5D:60:04:E8:F7
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
tc@box:/$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.64.64.64 * 255.255.255.255 UH 0 0 0 ppp0
127.0.0.1 * 255.255.255.255 UH 0 0 0 lo
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
tc@box:/$ ping 164.132.96.39
PING 164.132.96.39 (164.132.96.39): 56 data bytes
64 bytes from 164.132.96.39: seq=0 ttl=64 time=0.174 ms
64 bytes from 164.132.96.39: seq=1 ttl=64 time=0.081 ms
tc@box:/$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes...indefinitely time...
tc@box:/$ nslookup google.com
Server: 193.70.152.25
Address 1: 193.70.152.25
nslookup: can't resolve 'google.com'
tc@box:/$ wget -qO- http://example.com
wget: bad address 'example.com'
-
try this (adapted if parameters change)
sudo route del default gw 192.168.1.1
sudo route add default gw 10.64.64.64
Also avoid to have any dhcp client running, because that could overturn your settings later, static address for eth0 might be more simple.
Generally speaking, it might be easiest to kill udhcpc and have eth0 down while you are testing with ppp0.
-
i don't have del & add among my commands, however, udhcpc is killed when I try to set the ppp0 in netcard conf of controlpanel, after uncheck "use DHCP"
-
i don't have del & add among my commands, however, udhcpc is killed when I try to set the ppp0 in netcard conf of controlpanel, after uncheck "use DHCP"
Yeah tinypoodle did give you slightly incomplete commands, it probably should have been:
sudo route del default gw 192.168.1.1
sudo route add default gw 10.64.64.64
But from my own experience with testing WiFi setup when I also have a working 'eth0' I can say with confidence: "that's just asking for trouble". As you now have two internet connection "fighting" with each other. Instead of trying to adjust routes, I simple turn off the 'eth0' NIC with sudo ifconfig eth0 down and the routing will sort itself out.
Please try this and then the four tests I gave you in reply #12 might show different results.
Edit: I don't see the need to mess around with 'udhcpc' processes when the 'eth0' NIC is down. IIRC I just kept 'udhcpc' (for 'eth0') running, and when I decided to re-activate 'eth0' (via sudo ifconfig eth0 up) it continued to use the settings it had originally obtained from my local router (which is just as well as typically each of my local clients gets the same local IP address assigned again and again).
-
i don't have del & add among my commands, however, udhcpc is killed when I try to set the ppp0 in netcard conf of controlpanel, after uncheck "use DHCP"
Yeah tinypoodle did give you slightly incomplete commands, it probably should have been:
sudo route del default gw 192.168.1.1
sudo route add default gw 10.64.64.64
Oops! ::)
Sorry vinnie and thanks maro for rectifying that.
(last post corrected accordingly)
-
But from my own experience with testing WiFi setup when I also have a working 'eth0' I can say with confidence: "that's just asking for trouble". As you now have two internet connection "fighting" with each other. Instead of trying to adjust routes, I simple turn off the 'eth0' NIC with sudo ifconfig eth0 down and the routing will sort itself out.
Please try this and then the four tests I gave you in reply #12 might show different results.
Edit: I don't see the need to mess around with 'udhcpc' processes when the 'eth0' NIC is down. IIRC I just kept 'udhcpc' (for 'eth0') running, and when I decided to re-activate 'eth0' (via sudo ifconfig eth0 up) it continued to use the settings it had originally obtained from my local router (which is just as well as typically each of my local clients gets the same local IP address assigned again and again).
Not being an expert in networking and more empirically speaking, my impression is that for multiple network interfaces without going into any particular configuration it could work fine under the condition that there is only one dhcpc client and other interfaces are statically configure, but only if the dhcpc interface is connected to the desirable default gateway.
-
@maro, here is the test
root@box:~# ifconfig eth0 down
root@box:~# wvdial
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: at
at
OK
--> Sending: AT+CGDCONT=1,"IP","internet.wind"
AT+CGDCONT=1,"IP","internet.wind"
OK
--> Modem initialized.
--> Sending: ATD*99#
--> Waiting for carrier.
ATD*99#
CONNECT 7200000
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Tue Apr 12 02:21:36 2011
--> Pid of pppd: 13638
--> Using interface ppp0
--> pppd: H�l[08]`�l[08]
--> pppd: H�l[08]`�l[08]
--> pppd: H�l[08]`�l[08]
--> pppd: H�l[08]`�l[08]
--> pppd: H�l[08]`�l[08]
--> pppd: H�l[08]`�l[08]
--> local IP address 164.132.23.235
--> pppd: H�l[08]`�l[08]
--> remote IP address 10.64.64.64
--> pppd: H�l[08]`�l[08]
--> primary DNS address 193.70.152.25
--> pppd: H�l[08]`�l[08]
--> secondary DNS address 193.70.192.25
--> pppd: H�l[08]`�l[08]
tc@box:/$ ifconfig -a
dummy0 Link encap:Ethernet HWaddr 9A:55:B6:B7:E6:F2
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 20:CF:30:6E:C8:D2
inet addr:164.132.63.82 Bcast:164.132.63.82 Mask:255.255.255.255
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:126060841 errors:0 dropped:0 overruns:0 frame:0
TX packets:132916 errors:0 dropped:0 overruns:0 carrier:12
collisions:0 txqueuelen:1000
RX bytes:229426766 (218.7 MiB) TX bytes:15027641 (14.3 MiB)
Interrupt:30
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2325 errors:0 dropped:0 overruns:0 frame:0
TX packets:2325 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:225774 (220.4 KiB) TX bytes:225774 (220.4 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:164.132.23.235 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:118 (118.0 B) TX bytes:154 (154.0 B)
wlan0 Link encap:Ethernet HWaddr 48:5D:60:04:E8:F7
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
tc@box:/$ cat /etc/resolv.conf
nameserver 193.70.152.25
nameserver 193.70.192.25(entered manually)
tc@box:/$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.64.64.64 * 255.255.255.255 UH 0 0 0 ppp0
127.0.0.1 * 255.255.255.255 UH 0 0 0 lo
default 164.132.63.254 0.0.0.0 UG 0 0 0 lo
default 151.81.44.254 0.0.0.0 UG 0 0 0 lo
default 127.0.0.254 0.0.0.0 UG 0 0 0 lo
tc@box:/$ ping 164.132.23.235
PING 164.132.23.235 (164.132.23.235): 56 data bytes
64 bytes from 164.132.23.235: seq=0 ttl=64 time=0.118 ms
64 bytes from 164.132.23.235: seq=1 ttl=64 time=0.083 ms
64 bytes from 164.132.23.235: seq=2 ttl=64 time=0.083 ms
^C
--- 164.132.23.235 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.083/0.094/0.118 ms
tc@box:/$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes...indefinitely time...
tc@box:/$ nslookup google.com
Server: 193.70.152.25
Address 1: 193.70.152.25
nslookup: can't resolve 'google.com'
tc@box:/$ wget -qO- http://example.com
wget: bad address 'example.com'
Now i go to bed, here is 3'o'clock, within four hours I have to wake up ;D
I think tomorrow (actually, tonight) I'll try to do the whole process without ever having attacked the ethernet cable from the boot, and also tinypoddle's command (I forgot to try)
in the meantime, thanks maro & tinyp. for your help
-
@vinnie
had you success with your project?
I try to make running a Huawei E1750 from www.fonic.de (http://www.fonic.de) and Im interested in any result on your side.
-
I had done with the MBD-220HU but then that modem was broken twice and I have renounce.
I remember you had to start without connecting any wires tinyconre network, or connect via "dial-up modem" not working.
At the time I did the tests with a ubuntu live, once I get a certainly configuration working, then I tried to make it work in tinycore.
I also looked for answers in the official forum:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=4406#4406 (http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=4406#4406)
Currently I have only the pen E173, but I could not get it to work, I connect through windows (cross cable).
I took notes, but I can not see if they are correct, I translate them to you quickly:
1)install usb-utils, and enter command "lsusb", annotate the output, insert key and reenter "lsusb", the new entry in second output is your modem (in my case is Bus 001 Device 007: ID 1c9e:f000)
2) install modeswitch and wvdial, I remember that a restart is required.
after restart insert the internetkey, wait a few minutes to do allow modeswitch to do its job (transform the device from mass storage to analog modem) and retype "lsusb", if string of modem is changed modeswith work correctly.
2bis) if the string remain the same you check if a file with the name of your device is in /usr/share/usb_modeswitch/vendor:product, otherwise you have to search in internet. (the command to tell to modeswith to swith a devise usb_modeswitch -c /usr/share/usb_modeswitch/vendor:product, but it should be automatic)
3) Once the modem has been properly recognized and switched (control with lsusb) you mount a modem properly with :"modprobe usbserial vendor=0xvendor product=0xproduct" (take valor from lsusb vendor --> xxxx:xxxx <-- product)
4) If all going well you must see in /dev/ ttyUSB2 ttyUSB3 ttyUSB1 ttyUSB0, for connect i use 2
5) edit /etc/wvdial.conf according to your key (search in internet), You sure you did not put an ethernet cable, I do not remember what was the reason but it gave me problems, otherwise reset. Control /etc/resolv.conf , to be sure you can use 8.8.8.8 and 8.8.4.4 (google dns)
9) start connection with sudo wvdial (and remember store /etc/wvdial.conf and /etc/resolv.conf to your backup file of tinycore)
All operations should be automatic unless wvdial configuration and its launch.
-
Thanks Vinnie for the last status.
I am progressing in another thread. see http://forum.tinycorelinux.net/index.php/topic,11509.msg60985.html#msg60985 (http://forum.tinycorelinux.net/index.php/topic,11509.msg60985.html#msg60985)
According your message I forgot to put /etc/resolv.conf in the .filetool.lst
I will have a look if this is the issue I currently have.
As I can see, you are the issuer of wvdial.tcz. Do you have any idea what are the reasons of the errors in the other thread?