Hi. I recently purchased a rugged SOM (emmc variant) and switchblox rugged and have been having some trouble configuring the network on the SOM. I installed the OS following the steps in the getting started guide and am using the 3.3V uart console. However after running the commands listed to set up the ethernet bridge I can’t seem to get the SOM to connect to anything.
I have tried to configure a static IP on the eth0 and lanx interfaces, but the SOM can’t ping anything else that it should be connected to.
The switchblox rugged works as expected while standalone, but when connected to the SOM I can’t get any response between anything connected to it.
I think I followed the guide correctly for placement of the 16 pin connector on the 18 pin header, but I haven’t tried it in the other position.
I am hoping I have just missed a simple step in the configuration.
Hi, just to clarify: do you mean pinging between devices that are connected on the SwitchBloxRugged with Rugged SOM is not working or that trying to ping the RuggedSOM itself from a device not working?
In the latter case, we wouldn’t expect that to work. Whilst the RuggedSOM transmits and receives management frames between SwitchBloxRugged to set up multicast groups, STP, etc, it won’t itself be directly pingable.
In the former case of devices being unable to ping each other on the SwitchBloxRugged when RuggedSOM is connected, we’ve noticed some connectivity issues. I’ve isolated the issue and am hoping to get a fix out in the coming weeks.
Unfortunately I was referring to both cases you listed. I can’t ping between devices on the SwitchBloxRugged when RuggedSOM is connected and I was expecting the RuggedSOM itself to be pingable.
I realize that this isn’t an advertised feature but I was hoping that it would be possible to run some services on the RuggedSOM such as wireguard or potentially mavlink-router.
I see that openWRT integration is listed in the future developments but I understand that this is likely a long way off. Is this functionality completely off the table right now?
Gotcha, that’s very understandable. At the moment, our priority for Q4 2024 is the resolution of the outstanding issues on RuggedSOM + SwitchBlox Rugged, developing upgraded module boards, and adding router capability to the existing Dronenet board. Whilst adding router capability to Dronenet will allow typical layer 3 routing features, this won’t be OpenWrt and/or Linux-based. However, adding a Linux-based router board is still part of our longer-term roadmap.