From: driusan@gmail.com
To: "cinap_lenrek@felloff.net" <9front@9front.org>, 9front@9front.org
Subject: Re: [9front] DHCP not working on usb ethernet dongle
Date: Thu, 29 Dec 2016 20:02:13 -0500 [thread overview]
Message-ID: <20161230010213.4857936.7083.14772@gmail.com> (raw)
In-Reply-To: <adb29a07627bc666d07050079069a3b6@felloff.net>
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.
When I watch the traffic with snoopy, and I try to get a lease it sends out a bunch of packets of the form:
ether(s=<mac addr> d=ffffffffffff pr=0800 ln=590)
Ip(s=0.0.0.0 d=255.255.255.255 id=n frag=0000 ttl=255 pr=17 ln=576)
udp(s=68 d=67 ck=a3a3 ln= 556)
bootp(t=Req ht=1 hl=6 hp=0 xid=75d7f49b sec=n fl=0000 ca=0.0.0.0 ya=0.0.0.0 sa=0.0.0.0 ga=0.0.0.0 cha=<mac addr> magic=63825363)
dhcp(t=Discover clientid=01<mac addr> vendorclass=plan9_386 requested=(1 3 6 12 15 42))
But as far as I can see, gets no response.
When I manually configure it and ping the gateway I get packets sent that look like:
ether(s=<mac> d=fffffffff pr=0806 ln=60)
arp(op=1 len=4/6 spa=<manual ip> sha=<mac addr> tpa=<gateway ip> tha=000000)
When I ping my own manual IP, I'm getting icmp(t=EchoReq) and EchoRep lines that aren't in the output of pinging the gateway. (For the manual ip address, I'm using the IP that the router has associated with the MAC address from when I tested it under Dfly.)
I'm not really sure where to go from here.
Original Message
From: cinap_lenrek@felloff.net
Sent: jeudi 29 décembre 2016 17:37
To: 9front@9front.org
Reply To: 9front@9front.org
Subject: Re: [9front] DHCP not working on usb ethernet dongle
have you actually passed the usb ethernet interface to ipconfig? when
you leave the interface out ipcofig will just use the first ethernet
it finds on /net. it might have just configured your built in ethernet.
you do that like:
ip/ipconfig ether /net/etherUwhatever
if that doesnt work, start troubleshooting systematically:
figure out if usb ethernet works at all, run snoopy /net/etherUwhatever
and look if you see broadcast packets on the network. setup static
ip for that, so you can ping your host or send out pings and see if
both directions work.
--
cinap
next prev parent reply other threads:[~2016-12-30 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 21:19 Dave MacFarlane
2016-12-29 22:23 ` [9front] " sl
2016-12-29 22:31 ` Dave MacFarlane
2016-12-29 22:37 ` cinap_lenrek
2016-12-30 1:02 ` driusan [this message]
2016-12-30 4:13 ` cinap_lenrek
2016-12-31 1:49 ` Dave MacFarlane
2017-01-02 3:21 ` cinap_lenrek
2017-01-04 23:20 ` Steve Simon
2017-01-05 14:06 ` Dave MacFarlane
2017-01-02 3:35 ` mveety
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161230010213.4857936.7083.14772@gmail.com \
--to=driusan@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).