Setting up Stabilizer

SudhanshuRao

I'm setting up Stabilizer (part of a Sinara crate) in my lab. Stabilizer is connected directly to my PC via two separate links: an Ethernet-to-USB adapter (network), and microUSB (serial console) — no switch in between.
I'm running Mosquitto locally on the same PC. Setup:
PC's Ethernet-to-USB adapter: 192.168.4.1/24 (static)
Stabilizer: /net/ip = 192.168.4.2/24, /net/broker = 192.168.4.1 (confirmed via serial get, both shown as [stored])
ping 192.168.4.2 from the PC succeeds with 0% loss
Mosquitto is running with -v and confirmed listening on port 1883 (verified via Test-NetConnection, and MQTT Explorer connects fine and shows $SYS topics)
Problem: no dt/sinara/... topics ever appear in MQTT Explorer, even after multiple power cycles of Stabilizer. Mosquitto's verbose log shows zero incoming connection attempts from 192.168.4.2 — nothing at all, not even a rejected/failed connection.
Network layer and broker both seem to be working correctly, but Stabilizer doesn't appear to attempt an MQTT connection at all. What firmware/config-level thing might cause this?

Tobias

I believe the default configuration of mosquitto binds to 127.0.0.1, so will only see connections from the local host. To allow external connections you'll need to specify either 0.0.0.0 or 192.168.4.1 as your actual IP.

Guest

Due to some reason, my lab had to change the entire Sinara rack with a different one. In this one, I connected the Ethernet ports and the microUSB, and set the correct IP address via the serial terminal.

Confirmed so far:

Serial console (microUSB) works fine — get shows /net/ip = 192.168.4.2/24 and /net/broker = 192.168.4.1, both [stored]
PC-side adapter is statically set to 192.168.4.1/24, confirmed via ipconfig (no IP conflicts)
Ethernet link light on the PC-side adapter behaves normally

But ping 192.168.4.2 from the PC fails — either "Request timed out" or "Destination host unreachable" (reported by my own PC, 192.168.4.1), and arp -a shows zero entry for 192.168.4.2 at all — not even an incomplete one.

This same PC + adapter + cable setup worked correctly with the previous Stabilizer/rack (I could ping successfully). So this appears specific to something on the new rack/Stabilizer unit's Ethernet side, even though its serial console and stored config are fine.

Any idea what could cause the Ethernet interface specifically not to respond at the link layer, while serial/UART works normally? Could this be a hardware issue with this unit's Ethernet PHY, or something that needs re-checking on the new rack (e.g., cabling inside the rack itself)?

SudhanshuRao

Posted as guest by mistake — replying from my actual account to keep the thread trackable