[riot-notifications] [RIOT-OS/RIOT] usb: fails to respond ro ping when used with 802.15.4 (#12002)
notifications at github.com
Wed Sep 18 15:21:32 CEST 2019
> However, I'm confused. This issue is about pinging a node. So just to
> clarify: Pinging a node interface's link-local address through the
> another interface of that node should not be possible, as a link-local
> address is _per definition_ only local (and thus valid) to the link
> (i.e. also the interface).
This is about being able to ping the USB-attached node on its link-local
address on the USB interface from the host. When nimble or 802154 are
added, these addresses are the same, but they stay in `TNT`
indefinitely (ok, at least 5') rather than being VAL.
> Is the start of the USB interface maybe delayed? It might be that in
> that case the initial messages might not be sent because they are try
> to be sent before the interface was really up.
That'd be a plausible explanation, given that unlike the others it does
need to wait for the host. (And I don't have a setup where I can hotplug
that w/o power cycling the whole device). I tried `ifconfig 11 set state
reset`, but `unable to set status`.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications