You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running an OSC query application on another computer in the same LAN which announces its loopback address as server address VRChat tries to connect to it and fails.
To Reproduce
Start some OSC Query application on another PC in the same network that announces its loopback address for the service it provides.
Then start VRC on a different PC and you will get an error in the logs:
Log example from the second PC trying to connect to a service running on the loopback interface of 172.16.1.170.
2025.03.07 00:22:24 Debug - no SRV Records found in not parse answer from 172.16.1.170:5353
2025.03.07 00:22:24 Debug - Found new OSC Service: VRCFT-NHM5HG at 127.0.0.1:57440
2025.03.07 00:22:26 Error - Could not make new OscClient: An error occurred while sending the request
Expected behavior
VRC should either discard any OSC query packages from other machines that hold the loopback address in its information or listen on all interfaces so that the application in question can only announce zeroconf packages on the loopback which currently does not work.
Info:
Type: Desktop
Latest stable release
Additional context
I tried to announce the service on the loopback interface only to mitigate this issue but VRC only picks up services that seem to be announced on the LAN or wireless LAN connection.
The text was updated successfully, but these errors were encountered:
lcb01a
changed the title
Zeroconf OSC announcements with loopback machine from different machine.
Zeroconf OSC announcements with loopback IP from different machine.
Mar 7, 2025
When running an OSC query application on another computer in the same LAN which announces its loopback address as server address VRChat tries to connect to it and fails.
To Reproduce
Start some OSC Query application on another PC in the same network that announces its loopback address for the service it provides.
Then start VRC on a different PC and you will get an error in the logs:
Log example from the second PC trying to connect to a service running on the loopback interface of 172.16.1.170.
2025.03.07 00:22:24 Debug - no SRV Records found in not parse answer from 172.16.1.170:5353
2025.03.07 00:22:24 Debug - Found new OSC Service: VRCFT-NHM5HG at 127.0.0.1:57440
2025.03.07 00:22:26 Error - Could not make new OscClient: An error occurred while sending the request
Expected behavior
VRC should either discard any OSC query packages from other machines that hold the loopback address in its information or listen on all interfaces so that the application in question can only announce zeroconf packages on the loopback which currently does not work.
Info:
Additional context
I tried to announce the service on the loopback interface only to mitigate this issue but VRC only picks up services that seem to be announced on the LAN or wireless LAN connection.
The text was updated successfully, but these errors were encountered: