On Sun, Dec 20, 2015 at 01:13:10PM +0000, Stuart Henderson wrote:
On 2015-12-19, Read, James C <jcr...@essex.ac.uk> wrote:
Hi,
my device Huawei Mobile E353 is listed as known to be supported in the umsm
man 4 page
http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man4/umsm.4?query=umsm
&sec=4
Does anybody know what the steps are to get a umsm supported device up and
running. We are talking basics here. I really don't know where to start. What
should I be looking at? PPP?
If it's in a mode which attaches as umsm, yes you need to look at ppp(4)
and pppd(8), there are also some examples in umsm(4)'s own manual.
I don't know this particular device, but in general these devices
have several modes - the modem-like mode used by umsm, and a mode
that presents as an ethernet interface (cdce or urndis), if it's
in that mode then it would show in ifconfig and you would just use
dhclient. It looks like you can switch modes on/off on a Huawei with
an AT^U2DIAG=(something) command on the serial port (takes effect
after replugging the device) but there doesn't seem to be much good
documentation of the values to use. From ethernet mode it looks like the
Huawei dongles have an internal web page that allows switching back to
'modem' mode.
The values for AT^U2DIAG and the other configuration commands are not
completely standardised between different Huawei devices, and each device
tends to implement a subset of the full functionality available. As such
any guides to using and re-configuring them via AT commands that you may
find, will not necessarily be applicable to the device you have to hand.
I used several of these dongles over a number of years between 5.0-release
and about 5.5, when the last hardware I had failed.
The older ones did not have the ethernet interface, that was introduced
with what Huawei call, 'hi-link', which was advertised as the device
being capable of bringing up the link quickly. Infact, the difference is
that the older devices were, 'dumb', and needed the host to use ppp to
bring up and maintain the connection, (which gave much more flexibility and
allowed the easy sending of SMS as well).
The first generation of, 'hi-link', devices were a nightmare, at least for
me, I never got them working on the current OpenBSD at that time. The
more recent ones seem to be better.
If you look in the kernel source, you will see that there are all sorts of
work-arounds to accomodate the strange things that these devices do on
their initial USB connection.
Since the OP has used the device on other operating systems, other than
Windows which it is intended for, various configuration changes may already
have been issued to it, especially if he has been following various guides
and trying out commands at random. As such, even if the device IS supported
natively by OpenBSD, it may not be recognised as such, because the changes
to it's internal configuration are causing it to present itself as a
completely different device, (seen this several times before).
Of course, a full dmesg, instead of selected extracts would help.
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
