VOXL2 has two network interfaces for microhard modem
-
Hello,
I am flashing some newly purchased VOXL2 development kits when I ran into this issue when using a microhard. When voxl-configure-modem is run, it creates two interfaces that connect to the microhard: eth0 and usb0. The IPs that are set on both interfaces are random, and are not consistent between reboots of the voxl2 board. Additionally, when both are active, any connections to QGC from the board through the microhard is greatly slowed down. I would like to permanently set the ip address of one of the interfaces to be something that I can control, like how voxl-configure-modem used to do, as well as permanently delete the other interface since it is not required.
Things I have tried:
Editing /etc/network/interfaces and removing an interface. This does not prevent both interfaces from reappearing upon reboot
ifconfig eth0 down.eth0 sets itself back to "up" automatically within a few minutes, even without reboot.
ifconfig usb0 down.usb0 stays down when this command is run, but returns as up again upon the voxl2 board's reboot
ip addr del dev eth0.It returns the error:
sudo iw dev eth0 del.It returns the error
Here is what VOXL2 Version I'm running:
I did already try running apt-get update && apt-get upgrade
-
This post is deleted!
-
You must be using an older version of the Microhard add-on that had the LAN7500 Ethernet to USB chip installed.
It seems you could check if eth0 was there and run
ifconfig usb0 downin a startup service if eth0 is present? -
You must be using an older version of the Microhard add-on that had the LAN7500 Ethernet to USB chip installed.
It seems you could check if eth0 was there and run
ifconfig usb0 downin a startup service if eth0 is present?@Chad-Sweet I think that would work. Do you know if the same type of Microhard add-on would have exhibit the same symptoms with a VOXL1?
-
No, I do not know. VOXL 2 is a much newer kernel and OS and it may not behave identically
-
No, I do not know. VOXL 2 is a much newer kernel and OS and it may not behave identically
@Chad-Sweet Got it, thanks!
-
General QOL update: I automated a script using cron to
ifconfig usb0 downand change the eth0 ip address to what I wanted usingifconfig eth0 <ip>. This only works if the script is run using sudo -
General QOL update: I automated a script using cron to
ifconfig usb0 downand change the eth0 ip address to what I wanted usingifconfig eth0 <ip>. This only works if the script is run using sudo@Daniel-Ryu I have a VOX2 with a microhard modem, but I only get a USB0 and no ETH0. Putting USB0 down and trying to bring up ETH0 doesn't work as the system does not detect it. Just curious if this was your issue as well?
-
@Daniel-Ryu I have a VOX2 with a microhard modem, but I only get a USB0 and no ETH0. Putting USB0 down and trying to bring up ETH0 doesn't work as the system does not detect it. Just curious if this was your issue as well?
@Mastermind USB0 is the interface the VOXL2 + newer Microhard add-on boards use for communication, so eth0 may not show up if you're used to using that from VOXL1
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login