Skip to content

Conversation

@PaulZC
Copy link
Contributor

@PaulZC PaulZC commented Dec 8, 2025

I'm still seeing the EVK default to WiFi when selecting web config, even if Ethernet is connected
This change forces NETWORK_ETHERNET - if Ethernet is connected and has Internet

I'm still seeing the EVK default to WiFi when selecting web config, even if Ethernet is connected
This change forces NETWORK_ETHERNET - if Ethernet is connected and has Internet
@PaulZC
Copy link
Contributor Author

PaulZC commented Dec 8, 2025

Related to #801

@LeeLeahy2
Copy link
Collaborator

Hi Paul,

This change should not be needed. Without this change, I am able to connect to the web server using the Ethernet IP address and also rtk.local.

Would you please describe the process that you are using to get the system to fail?

Thanks for your help,
Lee

@PaulZC
Copy link
Contributor Author

PaulZC commented Dec 9, 2025

Hi Lee (@LeeLeahy2 ),

I agree, it should not be needed. But unfortunately the EVK still seemed to want to default to WiFi even if Ethernet was connected.

I had been using BaseCast mode though, before going into web config. So, maybe when BaseCast starts WiFi - as it should - that then takes priority over Ethernet?

Leave it with me. I'll come up with a list of steps to replicate what I saw.

All the best,
Paul

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants