From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qk0-f196.google.com ([209.85.220.196]) by ur; Fri Dec 30 20:50:00 EST 2016 Received: by mail-qk0-f196.google.com with SMTP id n21so40567831qka.0 for <9front@9front.org>; Fri, 30 Dec 2016 17:49:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=dKf7WkyeH1MgzO2b2bb61oqIUIRTmw4a+MxdY9zzInI=; b=E1R3vLL5GxdIOPSDxMT8bvPS5ndD++0JU9tjm8n4aR5hQq4eCsXKYzUJcxSB5fRX6C vhdOCNQRhNa8dH5CWygSrEcWXSE3jYBhijt/p9oGutGTNmc8Fyyl/wPSSrOYgAU8kRSt dpQbHmLhimTW2jqjF8c2+HCqcEzEfrUfggW66ziAE0TyHa3hw596d3s/nDAtG0N6V/Cn 4rbxqVMloquzn0gs7p8b8y9VAwL/GC5MDEbywVaLVrlXLXhcfOm+48bjUOXQbO1fe19N CfthEFbKAXSihOEmV86EuNAx8fAGcBUUytiumcvwQs6qoiYoonTRcjiZRlg5Ro1oawbO giYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=dKf7WkyeH1MgzO2b2bb61oqIUIRTmw4a+MxdY9zzInI=; b=tlE4Ij4pGPDP50WzjAOYP4JXoWZkcztPLnaJNf2L3vrfHrLYhTxkI8DejaKTc1OLJ4 cyVLegmaAkF9SkAmf/BEOMABkEelC55UPKQS0POAbJEDmALIXA4QeahcDB470bpBeqyn q2DFVvmn79nKGhn9U6H1Pmrykif9xCuRUBxPmRf5E0S9F9e9hBLYi6qFTls9vw+Gr7VS GAKk7GxklJ8VWIPLjFdXJETLhUwzogdwBrTYVGNLI7kL0c7CcoGzJF82nABp9lkXZn2y tP+NXYEJc79F+shjn4DbAhzN+AjFvJvbO+ybkWMgoW3XfnLfKxFJuMVl0lGVcoQa2PnS KPXw== X-Gm-Message-State: AIkVDXIuOQaAWB/X43Y2B0y0VuxkVO9LwHwAW4GBESARCx/y8Ya7Elg6hSKQdjGpFsmWgV4ucqOJ5Y68RD6auw== X-Received: by 10.55.148.199 with SMTP id w190mr34795118qkd.9.1483148998171; Fri, 30 Dec 2016 17:49:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.33.12 with HTTP; Fri, 30 Dec 2016 17:49:27 -0800 (PST) In-Reply-To: References: <20161230010213.4857936.7083.14772@gmail.com> From: Dave MacFarlane Date: Fri, 30 Dec 2016 20:49:27 -0500 Message-ID: Subject: Re: [9front] DHCP not working on usb ethernet dongle To: "cinap_lenrek@felloff.net" <9front@9front.org> Content-Type: text/plain; charset=UTF-8 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: cloud SQL over XML template property controller 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: '#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, 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