ossible.
> On OpenBSD and Android 13 there is an issue with the URNDIS connection
> dropping packets as soon as you try to do anything beyond basic pinging.
> I've attached an email I found to b...@openbsd.org. The issue does not occur
> with the same phone and laptop running Alp
Good evening,
I'm new to OpenBSD and would like some help debugging this issue if possible.
On OpenBSD and Android 13 there is an issue with the URNDIS connection dropping
packets as soon as you try to do anything beyond basic pinging. I've attached
an email I found to b...@openbsd
Hi misc@,
I am currently testing OpenBSD 6.8 (GENERIC.MP) #98 on an APU2c4 together with
a u-blox mPCIe LTE modem (MPCI-L210-03S-00) which can be configured to present
itself to the system either as a cdce(4) device or as a urndis(4) device. In
both modes, the modem is attached by the kernel
On Sep 02 18:46:41, h...@stare.cz wrote:
> On my amd64 workstation (see dmesg below), my android appears
> as an urndis(4) device a can provide the box with a network conection.
>
> urndis0 at uhub0 port 3 configuration 1 interface 0 "SAMSUNG Electronics Co.,
> Ltd. Samsun
On Sun, Sep 02, 2012 at 18:46, Jan Stary wrote:
> What could be the reason for that?
>
> The apparent difference between the two, USB-wise, is
> (amd64 box) uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> (i386 laptop) uhub0 at usb0 "VIA UHCI root hub" rev 1.00/1.00 addr 1
>
> i.e.
file in
/sdcard, and copy it to your computer to easier reading.
I ended up doing a hotplug script for my phone. No ip forwarding, just peer
to peer, mainly for ssh and scp.
On Sun, Sep 2, 2012 at 9:46 AM, Jan Stary wrote:
> On my amd64 workstation (see dmesg below), my android appears
> a
On my amd64 workstation (see dmesg below), my android appears
as an urndis(4) device a can provide the box with a network conection.
urndis0 at uhub0 port 3 configuration 1 interface 0 "SAMSUNG Electronics Co.,
Ltd. Samsung Android USB Device" rev 2.00/4.00 addr 3
urndis0: address b
I tested it on my loongson with my HTC Legend and it works well :)
[...]
umass1 at uhub1 port 3 configuration 1 interface 0 "HTC Android Phone"
rev 2.00/2.26 addr 4
umass1: using SCSI over Bulk-Only
scsibus3 at umass1: 1 targets
sd1 at scsibus3 targ 0 lun 0: SCSI2
0/direct removable serial.0bb40f
tested on amd64 w/ my HTC tattoo
[...]
umass0 at uhub0 port 3 configuration 1 interface 0 "HTC Android Phone"
rev 2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus2 at umass0: 2 targets, initiator 0
sd0 at scsibus2 targ 1 lun 0: SCSI2
0/direct removable
sd0: drive offline
sd0 detached
sc
9 matches
Mail list logo
