Re: [9front] DHCP not working on usb ethernet dongle

[Dave MacFarlane <driusan@gmail.com>]

I'm not certain that it's hitting the wire, but I don't have any
techniques more advanced than looking for blinking lights on the
router or dongle while running ip/ipconfig either.

Is there anything special I need to do to unbind the usb device? I'm
unbinding the ip interface with 'ip/ipconfig ether /net/etherwhatever
unbind', and then killing nusb/ether with 'slay ether | rc', but when
I try and restart nusb/ether I'm getting an error "nusb/ether: sharefd
usbnet: '#<symbol I don't know how to type on a Mac>c/usbnet/3.ether'
already exists", where 3. matches the usb bus from step 0.

I'm a little suspicious that it's not using the right driver, because
when I run ps -aux there's no arguments displayed, but I think it
should have at least "-t a88178". /rc/bin/nusbrc says nusb/ether is
handled by /sys/src/9/boot/nusbrc, and the vendor/device id from
/dev/usb/ctl are the first one in the case statement for that type
there. But I can't manually run it with the right arguments either,
because of the above error.


On Thu, Dec 29, 2016 at 11:13 PM,  <cinap_lenrek@felloff.net> wrote:
>> There is no built in ethernet, but I just tried explicitly passing it and still
>> no luck. It looks like it's sending out packets, but not reading any responses back.
>
> check on the other side if it is really sending packets. snoopy sees the
> packets that go out because the kernel just loops back what gets send on
> the interface. but that doesnt mean these packets actually hit the wire.
>
> otherwise it looks like the driver isnt working, so you'd have to debug
> the driver.
>
> 0) figure out what device this is, cat /dev/usb/ctl...
>
> 1) run ps aux and find the nusb/ether processed and notice the program
> arguments if any. we need the -t parameter and the device id.
>
> 2) unbind the ip interface and kill the nusb/ether processes
>
> 3) locate the driver for your specific type in /sys/src/cmd/nusb/ether
> and add debug prints. you can then rebuild and start a fresh driver
> process with the program arguments from (1).
>
> 4) look up the dragonflybsd driver from the info from (0) and see if
> we need todo some special magic to get that device working.
>
> --
> cinap



-- 
- Dave