Cannot log onto web interface when using direct ethernet connection

[Aiph5u (Aiph5u (not affiliated with Onefinity))]

Hey Matticustard, Gerald @sigung,

@Matticustard

the controller should have no issue obtaining an IP address within the 10.0.0.0/8 subnet using DHCP, so a static IP is not a requirement.

true.

@Matticustard

---

Why Do I Have the 169.254 IP Address?.

What is said in this article is true if you connect to an usual network with router etc.: It is a bad sign to get an 169.254.0.0/16 address if you have a DHCP server in your network.

But using a link-local address (169.254.0.0/16), which means using Zero-configuration networking (provided by the avahi package installed in the Onefinity controller) to get a link-local address automatically assigned works absolutely nicely if you just connect a laptop (that may have no DHCP server installed) to the Onefinity Controller, and also with zero-config name resolution so you can call it with http://onefinity.local. Most of the time, I used the ethernet connection this way. And as was tried to make it work the other day on older windows versions, the latter needed an additional software package that you pointed us to, for having Service Discovery

The limitation is that link-local addresses always stay local, they are not forwarded to another network (as per the standard). So you can’t use a link-local address to use an internet router to browse the web.

[Matticustard]

I am not attempting to debate the finer points of link-local.

I could absolutely be wrong — it would not be the first time. But I feel the most likely reason he is not receiving a valid IP address from the router over DHCP is because there is not a working link between the controller and the router and that we should start by attempting to verify and diagnose the connection, as opposed to burying him in technical jargon.

For reference, here is a photo of my controller interface when I plug the Ethernet cable into an empty switch.

All I have to do to get a valid IP is to provide a working connection to the DHCP server.

[Aiph5u (Aiph5u (not affiliated with Onefinity))]

Hey Matticustard,

@Matticustard

But I feel the most likely reason he is not receiving a valid IP address from the router over DHCP is because there is not a working link between the controller and the router (despite what he believes) and that we should start by attempting to verify and diagnose the connection

absolutely. We don’t disagree at all in any of these points. See my first paragraph in my last post.

I just wrote that because the article you linked seems to say that link-local is always a bad thing.

[Matticustard]

@Aiph5u

I just wrote that because the article you linked seems to say that link-local is always a bad thing.

My apologies. I was attempting to highlight the quoted passage which indicated a failure to get a response from the DHCP server as a potential cause, and felt it proper to include the original source. It was not my intention to demonstrate support for the entirety of the article. I will be more careful in the future.

[sigung (GERALD L HUNSUCKER)]

Hey everybody, there is some news. It appears that the reason I got the 169. series ip address is for exactly the reason Matticustard said.

So, here’s what happened.

I plugged the powerline connector into several different plugs in my garage, and I eventually found one that connected the Onefinity controller at 10.0.0.154.

There is only ONE plug in the garage that does this.

Now for the weird part… If I have WiFi disabled when I plug into this one “good” plug, the controller defaults back to 169.254.193.91, but if I enable WiFi, even though the controller is not connecting via WiFi, it chooses a good 10. series address, and it works.

I’ll take it, I don’t have to understand it, as long as it works.

[tmuka]

Plenty of generous IT support in the thread already, but I wanted to chime in to mention that I exclusively use wired eth with my x50 journeyman without issue. I’m on the latest stable firmware…