Open UsmanTariq2 opened 4 months ago
Can you provide some logs?
I don't think it is possible to bind to a completely different subnet other than what is actually used on a host, that just doesn't make any sense.
Are you using some kind of virtual machine for the server?
Also ULA issue, that is not an issue, as it will bind whatever IPv6 address will find. you can disable to +set net_ip6 ::01
Hello,
Will look into this in the future. Currently busy.
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.