Re: Porting umb(4) from OpenBSD

[Pierre Pronchery <khorben%defora.org@localhost>]

			Hi tech-net@,

some progress:

> umb0 at uhub1 port 4 configuration 1 interface 0
> umb0: Sierra Wireless Inc. (0x1199) Sierra Wireless EM7345 4G LTE (0xa001), rev 2.00/17.29, addr 4
> umb0: version 1.0

The next step probably has to do with ifconfig(8) indeed:

> # ifconfig umb0 
> ifconfig: SIOCGIFFLAGS umb0: Inappropriate ioctl for device
> # ifconfig umb0 up
> ifconfig: exec_matches: Inappropriate ioctl for device

You can obtain the fix(es) and follow my changes as I go here:
https://git.edgebsd.org/gitweb/?p=src.git;a=shortlog;h=refs/heads/khorben/umb

Cheers,
-- khorben

On 03/05/2018 04:29, Pierre Pronchery wrote:
> 		Hi tech-net@, (Taylor, Robert)
> 
> On 02/05/2018 14:59, Taylor R Campbell wrote:
>>> Date: Mon, 30 Apr 2018 15:26:37 +0200
>>> From: Pierre Pronchery <khorben%defora.org@localhost>
>>>
>>> It does not build yet (therefore also not tested) but I am getting
>>> there. If anyone feels like reviewing it already, it could save me some
>>> trouble and help getting it to work faster.
>>
>> First thing that jumps out at me is that our usb_task is still broken.
>> Ugh!  We need to fix that, but it likely requires a kernel API change,
>> so maybe it's too late for netbsd-8 at this point.
> 
> Is there something I should know? ie any workaround I should apply, or
> unexpected behaviour I should keep in mind?
> 
>>> This is probably also missing changes to ifconfig(8), if only to set the
>>> PIN code; this is the user interface that OpenBSD developers have chosen
>>> for this. Alternative suggestions are welcome! (sysctl...)
>>
>> ifconfig linkstr?
> 
> I think Robert is right, we need to be able to provide at least two, if
> not four parameters there: the PIN, APN, but also the username and password.
> 
> Additionally, the PIN and the password should probably not be printed
> back in the clear, whereas the APN should be totally fine.
> 
> Cheers,
-- 
khorben