[EVK] Web Config defaults to WiFi AP even when Ethernet is available and connected

[PaulZC]

As reported in #792

To replicate:
Running firmware 2.3 on EVK with Factory Defaults
Connect unit to Ethernet
Go into Web Config mode, either via the button or the Serial Menu
Web Config starts, but in WiFi AP mode, not Ethernet

[Ryanf55]

This also affects BaseCast. If you put the unit in BaseCast, with ethernet connected, it decides to start a wifi access point.
This may be intended...

[PaulZC]

The issue with Web Config lies here:

SparkFun_RTK_Everywhere_Firmware/Firmware/RTK_Everywhere/WebServer.ino

Lines 1131 to 1135 in 1cce7c8

	// Start the network
	if ((settings.wifiConfigOverAP == false) || networkInterfaceHasInternet(NETWORK_WIFI_STATION))
	networkConsumerAdd(NETCONSUMER_WEB_CONFIG, NETWORK_ANY, __FILE__, __LINE__);
	if (settings.wifiConfigOverAP)
	networkSoftApConsumerAdd(NETCONSUMER_WEB_CONFIG, __FILE__, __LINE__);

There is no provision for Ethernet (NETWORK_ETHERNET)

[PaulZC]

The fix for web config is in #813

[PaulZC]

@Ryanf55 : it looks like we have the same issue in BaseCast :

SparkFun_RTK_Everywhere_Firmware/Firmware/RTK_Everywhere/TcpServer.ino

Lines 701 to 704 in 1cce7c8

	if (tcpServerWiFiSoftAp)
	networkSoftApConsumerAdd(NETCONSUMER_TCP_SERVER, __FILE__, __LINE__);
	else
	networkConsumerAdd(NETCONSUMER_TCP_SERVER, NETWORK_ANY, __FILE__, __LINE__);

I'm going to open a separate issue for this

[disarticulate]

I've been trying to get the TCP/UDP configuration to make sense. The UDP Server doesn't appear to start on the ethernet.

Fixing the NTRIP Caster checkbox in #859 to enable the caster doesn't seem to do as requested.

I can only verify TCP Server mode. nmap shows only the TCP Server is open. I can't find any ntrip client that'll connect with a source table, although I think I saw it once.

My goal is to create a base station that forwards messages used in RINEX PPK or RTK and just need it to forward onto the Ethernet. Wifi would only be used for configuration if necessary.

NOTE: UDP does start, I'm just having an issue understanding how to keep the connections going. NTRIP is probably more useful for what I'm on about.

[disarticulate]

Looks like the sourcetable for the NTRIP Caster isn't setup fully. I was able to get debug info from: https://github.com/semuconsulting/pygnssutils
```response='STR;SparkBase;none;RTCM 3.0;none;none;none;none;none;none;none;none;none;none;none;B;N;none;none'``
I can start a new issue; the ntrip doesn't start correctly it seems.

[disarticulate]

Looks like the sourcetable for the NTRIP Caster isn't setup fully. I was able to get debug info from: https://github.com/semuconsulting/pygnssutils ```response='STR;SparkBase;none;RTCM 3.0;none;none;none;none;none;none;none;none;none;none;none;B;N;none;none'`` I can start a new issue; the ntrip doesn't start correctly it seems.

Documented this here: #861

So for the ethernet/wifi issue, my hotfix was to put all the connection boxes to WiFi and zero out WiFi Configuration.

Ethernet then works as expected. If you don't do this, then as stated, the AP mode starts up. My assumption would be to prioritize Ethernet, AP mode, then WiFi mode as the first two require zero configuration and physically attaching the Ethernet cord should be consider a "user input" primacy. When disconnected, it should degrade to AP mode unless it can find wifi.

[disarticulate]

There may be an uglier upstream issue with ublox & wifi. The error I'm experiencing in trying to stream data via ethernet & wifi ends up with closed socket every 30 seconds. There's nothing that I can see in the RTK_Everywhere firmware here that indicates it's locus.

However, when I went upstream to ublox, I found this (https://github.com/u-blox/ubxlib/blob/0237d5d3706ccb17419a8b9eac14bb568e80ad4c/wifi/api/u_wifi_loc.h#L54):

#ifndef U_WIFI_LOC_ANSWER_TIMEOUT_SECONDS
/** How long to wait for a location fix to be returned in seconds.
 */
# define U_WIFI_LOC_ANSWER_TIMEOUT_SECONDS 30
#endif

Is it possible leaving the wifi on but unable to connect is resetting the ethernet? This might also explain oddities in the BaseCast mode not immediately switching to the 2101 port.

Feel free to move this wherever. I can't keep a stable stream.