-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DHCP Client not running with USB-OTG ethernet #91
Comments
I can confirm you observation if I plug a USB Ethernet adapter without a connection to a DHCP enabled network.
However in case the USB Ethernet adapter is connected to a network. PlutoSDR firmware uses a very lightweight mdev hotplug manager.
|
Things seem to work for me... I have a windows machine with a pluto attached to ethernet (cross over cable plus Ethernet/USB dongle), and another pluto connected to the normal network (wifi on my laptop), and a zed board with an FMCOMMS2 attached on the network attached to wifi. I plug them in - they all show up on my windows machine.
the only problem is that the two plutos are on two different networks, and therefor don't see a name conflict when like this - so they show up on the windows machine as ip:pluto.local and ip:pluto.local (identical). You must use the ip number to differentiate them when you want to... with ipv6 - it should be better... But - it totally works for me now. |
And can confirm - However - I think that is because we don't have an I think |
I’m trying to use my Pluto with a rtl8153 usb ethernet dongle, but is seems the DHCP client is broken.
I logged in using the UART on the power USB port, and the link gets up, but the pluto seems not run a DHCP client:
After a short while avahi assigns a link-local address:
When I run
ifup usb0
(afterifdown usb0
, if avahi already assigned an address), the interface immediately gets an IP assigned via DHCP and everything works as it should:my config.txt:
The generated config seems fine:
log output:
I can provide necessary debug logs if you tell me where i can find them as I’m not familiar with the system layout.
The text was updated successfully, but these errors were encountered: