@ryan_meagher You should be able to do this using the /etc/network/interfaces approach you mentioned. voxl-modem uses that approach in order to set a static IP for Microhard on eth0. This is what the /etc/network/interfaces file looks like in that case:

# This file describes the network interfaces available on your system

# The primary network interface
auto eth0
iface eth0 inet static
	address 192.168.168.100
	netmask 255.255.255.0
	gateway 192.168.168.1

@Djalma-Ribeiro You can create a systemd service file and enable it to run on boot and have it execute the OpenVPN connection command.

Here is an example on how we have used it in the past on a VOXL:

[Unit]
After=voxl-time-sync.service
Requires=voxl-time-sync.service

[Service]
Type=forking
ExecStartPre=/bin/sleep 2
ExecStart=/usr/sbin/openvpn --script-security 2 --daemon --config /etc/openvpn/KEY_FILE

[Install]
WantedBy=default.target

Won't be exactly the same as above but that's the general idea.

@PawelJ Yep, it should be either 14550 or 14551.

Hi @jacksparkman ,

It looks as though you are running a Microhard connection. This may be interfering with your VOXL's ability to connect to the internet. You can disable the Microhard connection on startup by using systemctl disable voxl-modem and rebooting your VOXL. When you are ready to re-enable your Microhard connection you can use systemctl enable voxl-modem.

This may solve your issue. If not, are you using your VOXL's Wi-Fi in station mode and ssh'ing through your local network or in Soft AP mode and ssh'ing directly into VOXL?

You will need to have your VOXL in Station mode in order to SSH in as well as connect to the internet.

Thanks!
Tom

I would rebuild using the master branch and do the following:

You can use the opkg server in order to install the dependencies.

In /etc/opkg/opkg.conf uncomment the line #src/gz dev http://voxl-packages.modalai.com/dev.

Then, call opkg update

• Install libmodal_json with opkg install libmodal_json
• Install voxl-mpa-tools with opkg install voxl-mpa-tools
• Back on your host pc, run ./install-on-voxl.sh

@PawelJ It looks as though you are using the correct IP in your config file and voxl-vision-px4 is running correctly. Is it possible that you have some custom firewall setup on your host PC that is blocking traffic on that port?

@Alex123 You should be able to mount the sdcard directory using the following param
docker run -v /sdcard:/sdcard

@Daniel-Ryu Check out the documentation here: https://docs.modalai.com/docker-on-voxl/

Try running voxl-configure-docker-support.sh

@PawelJ There isn't an exact way to do that, if you want you could edit your initial question and add a [SOLVED] section at the top and describe the solution.

@Gaurav-Borade You don’t need to be in any specific directory to use opkg update

@Ed-Sutter And to be safe if you're in station mode I would set your ssid and pass to dummy values, i.e voxl-wifi station tmp tmp because I've seen in the past where wlan0 will try to bring itself back up after you manually force it down.

@Ed-Sutter Does it work if you only have one of the network interfaces up at once? For example, only having wwan0 up or only having wlan0 up? I'm wondering if some weird routing issue happens

@Anton-Gereles If you have a specific question that we can help you with please open a new forum post and we'd be more that happy to help get you going.

@Dekra-Lab Okay so the RB5 is not being seen at all by the VM but is seen by the Windows machine running the VM. It sounds like you'll need to enable USB pass-through in your VM to allow it to access USB devices connected to your host machine.

@tangotoo Awesome, thanks for the feedback.

@Ed-Sutter Not that I know of at the moment. Is there a specific reason why you're choosing to go with this card as opposed to others? I know you mentioned earlier that it supports certain bands you need.

@Tamas-Pal-0 We have observed this issue a few times and the solution is always to either swap out the MCBL-0001: https://docs.modalai.com/cable-datasheets/#mcbl-00001 (power module to VOXL2 cable) or insepct the cable closely and push the wires back into the connector if they have come loose. It seems as though after time if these cables are unplugged and re-plugged often that there is enough degradation that the VOXL2 isn't able to pull the current necessary on boot and thus enters the boot cycle. We are actively looking into this issue to determine the root cause. If you aren't able to fix the issue based off this info we can get you a new MCBL-0001.

@Ed-Sutter Beautiful! Glad to hear that

@tangotoo It depends on what kind of Android device you're using. Not all android hardware / builds support the same LAN chips.

@Ed-Sutter You'll actually have the jumper on the USB PWR side as seen in this photo:
but otherwise yes you've got the right idea