I have an issue with the reliability of ethernet on the Pi3 version of Stellarmate.
I create a new network connection either using a static hard coded IP address OR setting the interface to "share" (aka be a DHCP server). Neither of these are working correctly.
This initially works, but at intermittent but regular intervals it simply stops working for some reason. To re-enable I just click on the network name in the network icon dropdown in the top bar and it immediately restarts.
This has made it unusable.
I need to use ethernet ideally, because it drastically increases the download time of images from 15-20secs down to 4-5seconds. This is critical because I am often using hyperstar and length of images are regularly between 30-90seconds. Long download times means I lose stupid amounts of time each hour simply downloading images.
In the three screen shots
- One shows the before an after of the ifconfig command - in one you can see the interface is there with an IP address; then in the next execution you still see the interface, but stellarmate is executing something to disable this interface
- Next screen shot is from a "tail -f /var/log/messages" running to show how its running something to mess with the ethernet interface
- the third is a simple ping command running from my Mac and its shows how unreliable this connection is
This is new to me. I did not witness this behaviour on v1.4x firmware.
How can I "lock" an ethernet interface so that it stays active. This should be super easy, especially for something like Linux, but this is clearly not the case with this new firmware.