[Beta Verification] MetaGrid Pro shows incorrect Wi-Fi IPv4 address

1. Windows 11 Home Build 26200, app version 6.0.2

2. Steps to Reproduce
Ensure WIFI on PC is on - use command prompt and command ipConfig to confirm the wifi adapter ivp4 address .

Go to MetaServer app - under interfaces, look at wifi connection. This will display the ivp4 address of the ethernet connection, not the wifi connection ivp4 address

Thanks for reporting this. We have confirmed that MetaServer can display the first available network address under the WiFi label, which means an Ethernet address may be shown when both adapters are active.

We are correcting the interface labeling and address selection in the next MetaServer for Windows hotfix. I will update this thread when the corrected build is available for verification.

Status update: this correction has been implemented and is currently included in the MetaServer Windows 6.0.4 Beta 1 and MetaGrid Pro 1.7.4 Hot Fix beta.

This post is primarily an informational update for everyone following this issue. If you are already a member of the beta program, you are welcome to verify the correction and report the result here. If you are not a beta tester, no action is required—the correction is planned for the upcoming production hotfix.

The beta downloads and TestFlight build are available only to authorized beta testers, so the linked beta resources may show “Access denied” for other forum members.

Beta testers can download the server beta from https://forum.metagrid.app/t/latest-metaserver-beta-builds. Please verify the displayed Wi-Fi and Ethernet IPv4 addresses with both adapters enabled and report whether each label now matches the actual interface.