-
Notifications
You must be signed in to change notification settings - Fork 130
Description
Hello,
i have a simple server setup with my LAN subnet 192.168.1.100:28965 . "in CMD +set net_ip 192.168.1.100"
Using the same PC ( windows ) i go to the LAN tab in my section but i cannot see my server
Now i set server with "+set net_ip". Now the server binds to 0.0.0.0
Now i go to client and i can see my server in the local tab.
When i connect, it is using a different subnet to my LAN, something like 192.168.56.1:28961
Not sure this is a client or serverside issue.
Secondly, i would like ipv6 ULA to come into play here . If additionally binded to a ULA address, the server prefers ULA over ipv4 LAN
I would in general like ULA support extended, such as server awareness that ULA cant be routed outside LAN. Server should not send ULA pings to the codx master server for example.