[8.930][CLOSED] 3G Modem - Huawai K3715

Hi all,

I used to have my Huawei k3715 as a standby interface.
I just tried to configure it in v9 and it doesn't work anymore!

It keeps complaining about a pin. (mine didn't need one)
I went a windows pc and set the pin to 0000 with the included software.
It still diesn't work. I know the settings are correct because I copied them from said windows pc.

Which i used to test.

However I did notice something odd, with the modem attached... I see 2 devices, once is labeled k3715 the other unknown. I don't remember seeing 2 in v8.

Parents

0 wingman over 13 years ago

Did you use a backup or recreate the interface?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sjorge over 13 years ago in reply to wingman

No, I didn't take a backup of my v8 config, I started over from scratch and made a few infrastructure changes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 cziel over 13 years ago in reply to sjorge

Hi sjorge,

did anything change with 8.940016 in general? Does the UTM identify your Huawei K3715 correctly, or does it still show two devices (one correct and one unknown)?

Please get back with some feedback.

Cheers,
Cristof
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sjorge over 13 years ago in reply to cziel

Hi sjorge,

did anything change with 8.940016 in general? Does the UTM identify your Huawei K3715 correctly, or does it still show two devices (one correct and one unknown)?

Please get back with some feedback.

Cheers,
Cristof

I'll get back to you on this early next week.
VirtualBox isn't really workout and so I'm migrating back to ESXi.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sjorge over 13 years ago in reply to sjorge

Still seeing double, both identified the same.
Will see if I can get one of them to work later, need to lookup pin again.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sjorge over 13 years ago in reply to sjorge

Follow up 2:
ttyUSB0 works, then dies I think.

Was up and usable for a bit, tried to turn it off (expensive, I pay per 10Kb) but doesn't seem to work. Neither can I rename it due to a typo.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 sjorge over 13 years ago in reply to sjorge

Follow up 2:
ttyUSB0 works, then dies I think.

Was up and usable for a bit, tried to turn it off (expensive, I pay per 10Kb) but doesn't seem to work. Neither can I rename it due to a typo.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 cziel over 13 years ago in reply to sjorge

Morning sjorge,

do you get any error messages at /var/log/system.log or /var/log/kernel.log regarding either one of your 3G modems?

Cheers,
Cristof
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 sjorge over 13 years ago in reply to cziel

More bad news... after a reboot... one of the entries is back to being called unknown!

And I can reproduce the error [:(] I did it 3x in a row.
Boot system, configure the non unknown one.
Turn it on... after a few minutes I have a connections.
I don't want to it so I turn it off being satisfied it works.
... stays connected according to web interface.

I now want to rename the interface... I click edit, change the name and hit save.

I get the same message about the pin as in the previous post. [:S]

PS: access to the system can be provided if that would be handy. (see da_merlin)

Rebooting the system will get you the stick back after it has crashed, I (you) cam reboot it during the day if needed.

kernel.log

2012:05:08-23:03:15 inertia kernel: [13259.638973] PPP BSD Compression module registered

2012:05:08-23:03:15 inertia kernel: [13259.640690] PPP Deflate Compression module registered

2012:05:08-23:04:58 inertia kernel: [13362.215053] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.298049] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.391046] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.486374] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.571421] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.662042] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.748050] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.825925] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.914054] option: option_instat_callback: error -71

2012:05:08-23:04:58 inertia kernel: [13362.999051] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.073830] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.149452] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.239595] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.324710] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.420803] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.516355] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.611080] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.704192] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.789558] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.874731] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13363.963904] option: option_instat_callback: error -71

2012:05:08-23:04:59 inertia kernel: [13364.045168] option: option_instat_callback: error -71

2012:05:08-23:05:00 inertia kernel: [13364.129122] option: option_instat_callback: error -71

2012:05:08-23:05:00 inertia kernel: [13364.143789] option: option_instat_callback: error -108

2012:05:08-23:05:00 inertia kernel: [13364.144023] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0

2012:05:08-23:05:00 inertia kernel: [13364.144041] option 1-1:1.0: device disconnected

2012:05:08-23:05:00 inertia kernel: [13364.144115] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1

2012:05:08-23:05:00 inertia kernel: [13364.144128] option 1-1:1.1: device disconnected

2012:05:08-23:05:00 inertia kernel: [13364.144192] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2

2012:05:08-23:05:00 inertia kernel: [13364.144214] option 1-1:1.2: device disconnected

2012:05:08-23:05:00 inertia kernel: [13364.246152] usb 1-1: reset high-speed USB device number 2 using ehci_hcd

2012:05:08-23:05:11 inertia kernel: [13375.648142] usb 1-1: device descriptor read/64, error -71

2012:05:08-23:05:23 inertia kernel: [13387.451056] usb 1-1: device descriptor read/64, error -71

2012:05:08-23:05:23 inertia kernel: [13387.654033] usb 1-1: reset high-speed USB device number 2 using ehci_hcd

2012:05:08-23:05:35 inertia kernel: [13399.357150] usb 1-1: device descriptor read/64, error -71

system.log

2012:05:08-23:03:20 inertia ntpd[5915]: Listen normally on 25 ppp2 188.5.170.170 UDP 123

2012:05:08-23:03:20 inertia ntpd[5915]: peers refreshed

2012:05:08-23:03:20 inertia ntpd[5915]: new interface(s) found: waking up resolver

2012:05:08-23:04:59 inertia ntpd[5915]: Deleting interface #25 ppp2, 188.5.170.170#123, interface stats: received=0, sent=0, dropped=0, active_time=99 secs

2012:05:08-23:04:59 inertia ntpd[5915]: peers refreshed

2012:05:08-23:05:01 inertia /usr/sbin/cron[20221]: (root) CMD (   /usr/local/bin/reporter/system-reporter.pl)

[8.930][CLOSED] 3G Modem - Huawai K3715

Submitted a Tech Support Case lately from the Support Portal?