Re: Mbim device umb0 - no authentification?

[Kapfhammer, Stefan]

Thank you Theo,

that's what I wanted to know. No magic!
So I will write a little script, which catches
the DNS's and the IP's from ifconfig's
output and writes it to the correct files/
launches the correct commands

Will be no magic anyway ;)

Thank you for answering.


Freundliche Grüße / Regards
-stefan kapfhammer
  Originalnachricht
Von: Theo de Raadt
Gesendet: Montag, 5. September 2016 10:34
An: Kapfhammer, Stefan
Cc: Stuart Henderson; misc@openbsd.org
Betreff: Re: Mbim device umb0 - no authentification?


> Other question: In case the nameservers from the provider
> change, do I have to change them myself in resolv.conf or
> is there some magic with umb0, that the nameservers
> find there way to the resolv.conf (like with dhclient)?
>
> Even with default gateway 

We do not have magic to do this at the moment.

The driver was provided to us with a bunch of that magic, but it
interferes with the network smp effort (flippingroutes from an
uncomfortable place), as well as hard-wired semantics different from
other networks.

So we pulled out those parts when integrating the driver. Will revisit
such magic when the network stack is more ready.

For now, static configuration.

Re: Mbim device umb0 - no authentification?

[Theo de Raadt]

> Other question: In case the nameservers from the provider
> change, do I have to change them myself in resolv.conf or
> is there some magic with umb0, that the nameservers
> find there way to the resolv.conf (like with dhclient)?
> 
> Even with default gateway 

We do not have magic to do this at the moment.

The driver was provided to us with a bunch of that magic, but it
interferes with the network smp effort (flippingroutes from an
uncomfortable place), as well as hard-wired semantics different from
other networks.

So we pulled out those parts when integrating the driver. Will revisit
such magic when the network stack is more ready.

For now, static configuration.

Re: Mbim device umb0 - no authentification?

[Kapfhammer, Stefan]

Um 0
1 32768 4 lo0


ifconfig -A


after doing ifconfig umb0 -apn down

umb0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
index 5 priority 0 llprio 3
roaming disabled registration not registered
state open cell-class none
SIM initialized PIN valid (3 attempts left)
subscriber-id 26201120 ICC-id 894902
device KRD 131 21/141  IMEI 358749040 firmware CXP 901 8700/1
*phone# ++49171000
status: down

relevant dmesg:
===

umodem0 at uhub4 port 6 configuration 1 interface 1 "TOSHIBA H5321 gw" rev
2.00/0.00 addr 4
umodem0: data interface 2, has CM over data, has break
umodem0: status change notification available
ucom0 at umodem0
umodem1 at uhub4 port 6 configuration 1 interface 3 "TOSHIBA H5321 gw" rev
2.00/0.00 addr 4
umodem1: data interface 4, has CM over data, has break
umodem1: status change notification available
ucom1 at umodem1
umb0 at uhub4 port 6 configuration 1 interface 6 "TOSHIBA H5321 gw" rev
2.00/0.00 addr 4
umodem2 at uhub4 port 6 configuration 1 interface 9 "TOSHIBA H5321 gw" rev
2.00/0.00 addr 4
umodem2: data interface 10, has CM over data, has break
umodem2: status change notification available
ucom2 at umodem2
ugen1 at uhub4 port 6 configuration 1 "TOSHIBA H5321 gw" rev 2.00/0.00 addr 4


From: owner-m...@openbsd.org [owner-m...@openbsd.org] on behalf of Stuart
Henderson [s...@spacehopper.org]
Sent: Friday, September 2, 2016 12:21 PM
To: misc@openbsd.org
Subject: Re: Mbim device umb0 - no authentification?

On 2016-09-01, Kapfhammer, Stefan <sk...@skapf.de> wrote:
> What I have to give‎, but still missing in the manpage
> is the username telekom, the password telekom
> and the authentication protocol pap.

That is for PPP and is only used for the connection to the dongle itself, it
is
not passed to the network. It should be irrelevant for use with umb(4).

> Is this work-in-progress and I missed some reading
> or what did I wrong? With Telekom DE no packets pass
> without authentication.

Did you add a default route pointing to the umb interface?

It would be useful to show 'ifconfig -A' and 'netstat -rn'.

Re: Mbim device umb0 - no authentification?

[Stuart Henderson]

On 2016-09-01, Kapfhammer, Stefan  wrote:
> What I have to give‎, but still missing in the manpage
> is the username telekom, the password telekom
> and the authentication protocol pap.

That is for PPP and is only used for the connection to the dongle itself, it is
not passed to the network. It should be irrelevant for use with umb(4).

> Is this work-in-progress and I missed some reading
> or what did I wrong? With Telekom DE no packets pass
> without authentication.

Did you add a default route pointing to the umb interface?

It would be useful to show 'ifconfig -A' and 'netstat -rn'.

Mbim device umb0 - no authentification?

[Kapfhammer, Stefan]

Hello misc,
hello developers,

‎first of all thank you for the stunning release
of OpenBSD 6.0.
Well, so much improvements. WOW!

I have a builtin UMTS card Ericsson H5321gw.
Until 5.9 I used pppd(1) together with chat(1)
to connect to my mobile provider. Devices
/dev/cuaU0 - /dev/cuaU2

To my surprise I could see today, that this
card is registered as MBIM device umb0.
I created a hostname.umb0 file in /etc
with:

apn internet.telekom
pin 

after 'ifconfig umb0 up'

the blue light at the frontpanel, indicating
UMTS connection, turned on.

'ifconfig umb0' showed up the correct apn,
‎the entered pin as valid, 2 provider given dns servers
as well as a remote and a local ip address.

What I have to give‎, but still missing in the manpage
is the username telekom, the password telekom
and the authentication protocol pap.

Is this work-in-progress and I missed some reading
or what did I wrong? With Telekom DE no packets pass
without authentication.

Have you any advice for me?

Freundliche Grüße / Regards
-stefan kapfhammer