ttyUSB missing

[pacchiee]

Hello,

Am trying to connect my usb modem via wvdial. When running "wvdialconf" from command prompt it scans  S0 S1 S2 S3 and fails no modem detected.

On "lsusb", the modem is shown as:
Bus 005 Device 003: ID 12d1:1505 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard

Usually this modem will be recognised as ttyUSB0, which is missing (It works like this in puppy linux).

Can you please help to configure this modem?

Thank you!

[Rich]

Hi pacchiee
Go to the search page and change the   By user:   field to   floppy   and search for    wvdial.

[floppy]

find the correct usb_modeswitch file  here? http://ubuntuforums.org/archive/index.php/t-1814583.html
use my "howto" http://forum.tinycorelinux.net/index.php/topic,11509.msg61207/topicseen.html#msg61207
and adapt it.

[pacchiee]

Thanks floppy, for coming here to this thread.

I installed VLC Media Player and wow.. the modem is now detected and attached to ttyUSB0. Don't know what made the difference.

Am able to connect using wvdial; connects successfully and gives the IP Address, Remote IP, Primary DNS and Secondary DNS. But, there are two major problems now:

1. Though connected, am unable to browser through internet. Even, the Apps ends with a network error. Browser could find nothing on the internet too.
2. Every time I reboot the machine, the /etc/wvdial.conf file goes missing.

Please help me to overcome these two issues.

Thank you!

[gerald_clark]

Add 'etc/wvdial.conf' to /opt/.filetool.lst before you do the backup.
Do you have a valid route set?

[pacchiee]

Thanks, gerald_clark.

Add 'etc/wvdial.conf' to /opt/.filetool.lst before you do the backup.

It works, after following the above step the /etc/wvdial.conf file is saved on next boot.

Do you have a valid route set?

Sorry, I didn't get what you mean..

However, even after wvdial is connected, the system fails to communicate with the www.

Please help. Thank you!

[gerald_clark]

What is the output of 'route -n' ?

I suspect you will need to
route add default gw xxx.xxx.xxx.xxx
where  xxx.xxx.xxx.xxx is your gateway address as defined by your ISP.

[pacchiee]

Thanks again, gerald_clark.

I guess the problem lies with the /etc/resolv.conf. If I edit this file to use public dns and then connect wvdial, it works.

But, when I connect using wifi, /etc/resolv.conf is rewritten and nameserver will be set to 192.168.1.1 after which the wvdial connect doesn't work until the nameserver is changed to public dns.

Is there a way to make the wvdial use its own auto-generated nameservers (when wvdial connects, it shows an ip address, remote ip, pri dns and sec dns)?

Thank you!

[tinypoodle]

This is a bit confusing, are you alternatingly using wifi and cell connection?
Are you using udhcpc at all?
192.168.1.1 is a private range IP (LAN), not uncommon to be assigned to routers.

[pacchiee]

Thanks, tinypoodle.

This is a bit confusing, are you alternatingly using wifi and cell connection?

Sorry for not explaining things better. Yes, when at home or office I use wifi to connect to internet and when am moving, I use the USB Modem.

Are you using udhcpc at all?
192.168.1.1 is a private range IP (LAN), not uncommon to be assigned to routers.

Am not sure whether udhcpc is used or not. My only ways to connect to the internet are wifi and wvdial.

I opted to backup /etc/resolv.conf, but when using wifi nameservers are set to 192.168.1.1 and the same thing is backed up. When I boot on the move and connect the USB Modem, it demands for a change of nameservers in the /etc/resolv.conf.

I need to use both wifi and wvdial, often alternatively. Is it not possible that the wvdial uses its own nameservers as it shows at the connect?

Thank you!

[tinypoodle]

I'd suggest you set public nameservers with udhcpc and see if that works with wvdial as well.

http://forum.tinycorelinux.net/index.php/topic,8019.0.html

[pacchiee]

Thanks again, tinypoodle.

I had been to the thread you pointed earlier also, but somehow couldn't end up with the solution. Now, I have added public nameservers with udhcpc and opted to backup /etc/resolv.conf as well. This works for wvdial also.

Thanks everybody for all the help extended in resolving this issue.

:o)