Anyone got the Huawei E169 3G modem working with ROS? I got a couple of Huawei E220 that works perfect, but my network-provider now deliver E169 instead of E220. I don´t want to by one if it doesn´t work.
/Johan
Anyone got the Huawei E169 3G modem working with ROS? I got a couple of Huawei E220 that works perfect, but my network-provider now deliver E169 instead of E220. I don´t want to by one if it doesn´t work.
/Johan
Currently there is no support for such device (as far as I know), if anyone owns such device. Please, plug the card into the router with MikroTik RouterOS, generate support output file and send it to support@mikrotik.com
Hello
I logged in the forum to write about the same argument.
I’ve got a couple of E169, the modem show a strange behaviour.
My setup is
ROS 3.20 on Alix 2c3
Huawey E169
I followed the example in http://wiki.mikrotik.com/wiki/Option_Globetrotter_HSDPA_USB_Modem
This is a little log from my box:
[admin@MikroTik] > /system resource
.. io irq pci usb export get monitor print
[admin@MikroTik] > /system resource usb print
# DEVICE VENDOR NAME SPEED
[admin@MikroTik] > /log
[admin@MikroTik] /log> print
01:12:13 async,ppp,info ppp-w: initializing modem...
01:12:13 async,ppp,info ppp-w: dialing out...
01:12:13 async,ppp,info ppp-w: authenticated
01:12:16 async,ppp,info ppp-w: could not determine remote address, using 10.112.112.121
01:12:16 system,info dns changed
01:12:16 async,ppp,info ppp-w: connected
[admin@MikroTik] /log> /port print
Flags: I - inactive
# NAME USED-BY BAUD-RATE
0 serial0 Serial Console 38400
1 usb1 PPP <ppp-w> 9600
2 usb2 9600
3 usb3
[admin@MikroTik] /ip address> print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK BROADCAST INTERFACE
0 172.26.26.100/24 172.26.26.0 172.26.26.255 ether1
1 D 151.80.13.255/32 10.112.112.121 0.0.0.0 ppp-w
[admin@MikroTik] /ip address> /ip route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY-STATE GATEWAY DISTANCE INTERFACE
0 S 0.0.0.0/0 reachable 172.26.26.1 3 ether1
1 ADS 0.0.0.0/0 reachable 10.112.112.121 1 ppp-w
2 ADC 10.112.112.121/32 151.80.13.255 0 ppp-w
3 ADC 172.26.26.0/24 172.26.26.100 0 ether1
[admin@MikroTik] /ip address> /ping 10.112.112.121 interface=ppp-w
10.112.112.121 ping timeout
10.112.112.121 ping timeout
10.112.112.121 ping timeout
I modified the remote-address in ppp profile to have it assigned in ppp connection,
I can connect but I can’t obtain a valid gateway, anyway connection is not working also if I hardcode the gateway in the ppp profile
I can connect trough serial /system serial-terminal
Now I’m going to try the same with an E220.
Looks like you don´t have any problems with the driver?
/Johan
It looks so, but I can’t have a correct ppp connection.
I can connect with vwdial and the same modem on various linux boxes.
I don’t know how to debug,
Anyone had success in connecting, to vodafone or wind in italy, with huawei E169 or e220?
best regards
paolo
The Huawey E169 is working.
this is my configuratio for wind in italy
the serial port is usb1
[admin@MikroTik] /interface ppp-client> print
Flags: X - disabled, R - running
0 R name="ppp-w2" max-mtu=1500 max-mru=1500 mrru=disabled port=usb1 user="" password=""
profile=ppp-w phone="*99#" dial-command="ATDT"
modem-init="AT+CGDCONT=1,"ip","internet.wind"" null-modem=no dial-on-demand=no
add-default-route=yes use-peer-dns=yes allow=pap,chap,mschap1,mschap2
De facto I’m using the default ppp profile
[admin@MikroTik] /ppp profile> print
Flags: * - default
0 * name="default" use-compression=default use-vj-compression=default use-encryption=default
only-one=default change-tcp-mss=yes
1 name="ppp-w" use-compression=default use-vj-compression=default use-encryption=default
only-one=default change-tcp-mss=default
Thank you for the update! Will buy the E169.
/Johan
Hi Guys,
I am trying to get the E169 working with v3.20 without any luck.
The ISP is Exetel.
[admin@MikroTik] /ppp profile> print
Flags: * - default
0 * name="default" use-compression=default use-vj-compression=default
use-encryption=default only-one=default change-tcp-mss=yes
1 * name="default-encryption" use-compression=default
use-vj-compression=default use-encryption=yes only-one=default
change-tcp-mss=yes
[admin@MikroTik] /interface ppp-client> print
Flags: X - disabled, R - running
0 name="ppp-1" max-mtu=1500 max-mru=1500 mrru=disabled port=usb1 user=""
password="" profile=default phone="*99#" dial-command="ATDT"
modem-init=""AT+CGDCONT=1,"ip","exetel1""" null-modem=no
dial-on-demand=no add-default-route=yes use-peer-dns=yes
allow=pap,chap,mschap1,mschap2
[admin@MikroTik] > log print
16:02:12 system,info router rebooted
16:02:13 async,ppp,info ppp-1: initializing...
16:02:13 async,ppp,info ppp-1: reseting link...
16:02:14 async,ppp,info ppp-1: initializing modem...
[admin@MikroTik] /system resource> usb print
# DEVICE VENDOR NAME SPEED
[admin@MikroTik] > port print
Flags: I - inactive
# NAME USED-BY BAUD-RATE
0 serial0 Serial Console 9600
1 serial1 9600
2 usb1 PPP <ppp-1> 9600
3 usb2 9600
4 usb3 9600
Any Ideas?
I also got problems…
The same config, with same SIM-card, works with E220. The E169 works under Windows, so it isn´t any problem with the hardware. I use ROS 3.20 on PC Engines ALIX 6b2.
This is my config (haven´t configured anything else in my router):
[admin@MikroTik] /interface ppp-client> print
Flags: X - disabled, R - running
0 name="if-ppp-tele2" max-mtu=1500 max-mru=1500 mrru=disabled port=usb1
user="" password="" profile=default phone="*99***1#"
dial-command="ATDT" modem-init="AT+CGDCONT=1,"IP","internet.tele2.se""
null-modem=no dial-on-demand=no add-default-route=yes use-peer-dns=yes
allow=pap,chap,mschap1,mschap2
01:54:18 async,ppp,info if-ppp-tele2: initializing…
01:54:18 async,ppp,info if-ppp-tele2: reseting link…
01:54:19 async,ppp,info if-ppp-tele2: initializing modem…
01:54:19 async,ppp,info if-ppp-tele2: dialing out…
01:54:20 async,ppp,info if-ppp-tele2: terminating… - modem hunged up
01:54:20 async,ppp,info if-ppp-tele2: disconnected
Could it be related to different f/w-versions of E169? I have 11.314.12.00.00.
/Johan
My problem is solved by downgrade from 3.20 to 3.17 (exactly the same config).
/Johan
Hi …
I’ve been around with a E156 some time ago, on PC Engines WRAP. At that time ROS 3.16. Today is 3.21.
I don’t know if E156 is closer to E220 or E169 but E156 have those built-in virtual CDROM (which carries win drivers) and a Mini-SD card adaptor.
Anyway, when connected E156 (may be others) creates two USB ports: in my case USB1 = modem data port and USB2 = serial data port (telemetry, AT comands, etc). This ports does not show up as separated ones at Winbox system => resources => USB tab. There will be a single Huawei 3G etc etc.
To make this guy stable (and connected all the time) I needed to disable in “system\console” the serial0 VT102 terminal. Since then, modem connected all the time. But this was 3.16.
From 3.17 afterwards, it was not necessary disable this VT102 anymore.
My initialization string is just … ATZ … because the usual [modem-init=""AT+CGDCONT=1,“ip” …] normally is stored at the modem flash. I set WCDMA only / 2100MHz using windows GUI first. Then installed the modem on Wrap (I used to know the AT command for that … long time ago).
My mobile providor uses only PAP so I disabled all the rest (CHAP/MSCHAP 1 & 2). When all enabled modem tries to conect endless.
On hardware side … 3G modems sinks a lot of current (0.5A). WRAP does provide only 0.1A so I needed to build a power injector to deliver 5V @ 1A max to this particular USB port. With marginal current there was some unstable behaviour.
(my private “home WISP” pix = http://py.qsl.br/wrap_img.htm … I use this to provide WLAN around my home at countryside)
Regards
Strange, this morning the problem is back… So downgrade didn´t help…
/Johan
Some more testing done…
Tested on a regular PC (pretty old, 450MHz Pentium) and got the same problem, so I guess it´s not power-related?
Changed the initialization-string to ATZ. It seems to work when locked to GPRS (changed settings from Windows). With autoselect or 3G only I only get the “modem hunged up”-error. Any ideas why it doesn´t work with 3G? (it works from Windows)
/Johan
Don’t know if it’s not power related. Surfin’ around Huawei 3G HW tech forum we can see several topics focusing 5V supply problems: dirty USB conn contacts, bad +5Vcc decoupling, 4.75V where it should have 5V (mine E156 stops working with 4.75V).
As fas as I remember Huawei tech staff was sniffing this topics because I guess when they designed those modems they supose that they’ll be 99% of the time as close as possible of USB ports, most of them 2.0 and at recent generation PCs. So - this is common in consummer industry - may be any extra filtering components was not part of the modem itself as - may be - the manufacturer assumes that USB supply is a well filtered 5V source.
There was a guy at this forum that added several extra electronic components at the USB port to solve modems hangs. Those components phisical size make impossible to assemble them inside those stick modems.
What normally happens is: data flowing at the “data wires” sometimes leaks to “supply wires” creating spikes or other sort of impulse over the Vcc input. If there is not enough filtering, those voltage spikes can reach some sensible part of the modem via Vcc path, hangin’ modem up, messing data integrity, reseting etc.
IF you have a Windows machine that does not freezes, try installing a demo ROS version on a pen drive and test this way (lock the modem on 3G only before to shortcut some steps). If it hungs, ROS issue. If its not, HW issue.
A Huawei forum topic abt 169 freezes and the hardware mod solution: http://forum.huawei.com/jive4/thread.jspa?threadID=323238
Regards;
P.S. Don’t worry abt PC age … I use a WRAP board 233MHz, USB 1.1 and got full 2Mbps download + 384K upload all the time.
I think everything works ok now. Have been in contact with support and they fixed the problem in 3.22.
Still have one problem. If my ppp-client is enabled when the systems reboots it never manage to connect. But if it is disabled during reboot and enabled after that it works. So I wrote this script that run after every reboot:
:delay 10;
:local dis [/interface ppp-client get if-ppp-tele2 disabled];
:if ($dis = false) do={
/interface ppp-client disable if-ppp-tele2;
/system reboot;
} else={
:delay 60;
/interface ppp-client enable if-ppp-tele2;
}
/Johan
Thanks a lot giopao, your help is still effective nowdays!!! with huge amount of E169 internet key it’s working like a charme.