I have unrealiable WiFi connection in the garage where the machine is located.
I’ve previously been able to connect to the wifi network on the machine, but it does drop, as well as often does not connect on startup.
Instead, I’m trying to connect via an ethernet cable, but having difficulties. I’ve plugged in the network cable, and booted the machine, but it doesn’t seem to connect to the network.
I’m connecting via a mesh network system, and hardwired to one of the access ports.
I have other devices that can connect, laptops, and a 3d printer via this network cable, so I’m certain it’s not a cable/AP issue.
Yet the onefinity machine doesn’t seem to connect to the network.
Is there some else I need to do to get the machine to connect to my local network?
There shouldn’t be anything you need to do to enable the ethernet connection on the Onefinity controller. I’d suggest testing the connection by unplugging the cable from the Onefinity controller and plugging it into a laptop or other device if you have one. Also you can test the Onefinity controller by plugging it in back to back to with a laptop as well.
I assume your mentioning “hardwired to one of the access ports” as being one of the half dozen (or so) ports on the back of your Internet modem. If so, then one thing I can suggest here is to try swapping ports with something else.
Confirm you cannot see an IP address on the top of the Onefinity control webpage when powered on and idle
Do any of the lights on the network cable JACK on the Raspberry Pi (or on your modem/device) either blink, or even briefly flash at all when power is first applied? Sometimes there may be lights without having turned on the Onefinity, but make sure it is on and idle
If you know how, try logging into your modem’s web interface (e.g. 192.168.1.1 is default for many networks) and see if you can identify the Onefinity as being recognized and/or what its IP address is showing
Try opening a terminal window by plugging in a keyboard to the controller then hold the Ctrl key, press T then C and let go of the Ctrl key.
Next type "ping 127.0.0.1” this called the loopback address and will test the ethernet port of the raspberry pi to make sure it is working, this should work with or without a cable plugged in. It should look like this.
It sends test data to the destination IP and lists the response. I think it says something like destination unreachable or something when it fails. Hold the Ctrl key and press C to stop the ping. If this works the ethernet port of the controller is good.
Next make sure the cable is plugged in and use the ping command again but this time use your router IP instead of the loopback. The router should respond the same way with no lost/dropped packets. If it can’t ping the router it’s probably a physical connection issue at the ports or in the wire. If it can ping the router it’s usually a software issue like a firewall or some setting in the router blocking the controllers access.
To get back to the controller display hold Ctrl, press T twice and let go of Ctrl.
but 127.0.0.1 is the localhost, which means, it pings itself with this command. Using the loopback interface bypasses any local network interface hardware. I would rather type “ifconfig” to see to what ip address the network hardware is configured, and “netstat -r”.
Yes the loopback address is a self test to check for faulty local ethernet adapter hardware . They rarely go bad but if it fails there’s no chance of talking to anything else on the network and the raspberry pi would have to be replaced.
Yes ifconfig would work too. It would also have the added benefit of showing the ethernet adapter network settings. If the ethernet adapter/hardware was the issue the ifconfig should fail too.
As Aiph5u said, pinging 127.0.0.1 hits the software based loopback interface not any physical interface. Fun fact - you can ping any address beginning with 127.x.x.x and it hits the loopback interface.
If the wired connection gives you too much trouble you could try using a small travel router mounted on the onefinity in repeater bridge mode too. In repeater mode it would recieve the signal from your network routers wifi amplify and resend any signals. There are many different models and prices but they are all small, slightly larger than a deck of cards. They would need to have the repeater mode though. Here is a link to the first one I found on Amazon.
GL.iNet GL-SFT1200 (Opal) Secure Travel WiFi Router – AC1200 Dual Band Gigabit Ethernet Wireless Internet Router | IPv6 | USB 2.0 | MU-MIMO | DDR3 |128MB Ram | Repeater Bridge | Access Point Mode https://a.co/d/fMhRTpg
when you connect a HDMI monitor to the Onefinity Controller (and there is an ethernet cable between Onefinity Controller and remote computer), are you seeing an IP address on top of the page, like this?
The method described in the video uses will automatically establish a ‘link-local’ IP address with the zero-configuration networking that is installed on Onefinity Controller. This means, you would see a 169.254.x.x address on top of the display (or when typing ‘ifconfig’ on the CLI), as shown in the image above. Is this the case when you connect with an Ethernet cable?
If so, you can type this IP address into the address bar of your web browser on the remote computer, and you should see the Onefinity Controller User Interface (UI) and everythings works then.
Additionally, the Onefinity Controller offers Name Service Discovery to resolve addressing with the name ‘onefinity.local’. It does this with the Linux common implementation “Avahi” that uses mDNS. However this is not supported on older Windows OS.