Hi Sean (@Sean512 ),
Apologies for the slow reply. (I missed your reply.)
We need to be a little careful here. You’re now talking about three different things.
Just to be clear, the 192.168.3.1 Ethernet-over-USB interface only applies to the “CONFIG MOSAIC” USB-C port on the RTK mosaic-X5. With the correct driver installed, that should “just work”. But I have seen it fail when my computer was already using a 192.168.3.n address - allocated by DHCP over its Ethernet interface. I’ve also seen it fail when I have a VPN Client running on my computer.
The new v4.15.1 firmware may require you to enter a username and password before you can use Ethernet-over-USB. This doesn’t apply in your case, but something to be aware of for if/when you upgrade.
Do you see the two virtual COM ports (USB1 and USB2) when you connect to CONFIG MOSAIC? If you do then USB is working and your issue must (I think) be due to network configuration. You can use RxTools to configure the X5 over either of these COM interfaces.
If you have the RTK mosaic-X5 MOSAIC ETHERNET Ethernet port connected to your local network and you can connect on 192.168.0.n, then Ethernet is enabled and working. It is possible to disable this interface but the firmware running on the ESP32 will enable it by default. But note that the Ethernet interface and Ethernet-over-USB are two completely different things, each with their own IP address etc..
The ESP32 WiFi interface needs to be enabled through the CONFIG ESP32 USB console, as described in the quick start guide. Once you have selected mode 2 (WiFi) with “set -m 2” and set the SSID and password, you need to connect the X5 Ethernet port directly to the ESP32 ETHERNET port. Once you have done that and ESP32 is connected to WiFi, you’ll be able to connect to the X5 via the ESP32’s WiFi IP address. It’s not possible to do this step through RxTools or an X5 interface. You need to configure the ESP32 directly through the CONFIG ESP32 port. Internally the ESP32 is running a promiscuous bridge from WiFi to Ethernet. All WiFi packets are passed to Ethernet and vice versa. The ESP32 doesn’t do any filtering.
Side note: it would be possible to link (cross-over) the ESP32 and X5 COM1 UART interfaces on the two green screw terminal blocks. Then you could divert the ESP32 console to that interface, daisy-chain it to the X5 and have the console appear on the X5 Ethernet as a TCP port. We do the same thing on the GNSSDO. You can then configure the ESP32 firmware and the OCXO settings over TCP. But I don’t see what you would gain by doing the same thing on RTK mosaic-X5. You would still need to connect the Ethernet ports manually when changing mode. Anyway, I just thought I would mention it.
I hope this helps,
Paul