ok then most likely GRIDNET Core is attempting to bind a UDT (UDP) socket to your Public IP address which ultimately fails, since the auto-detected IP address, it attempts to bind to - it is not available from the scope of the local machine.
@MrUnHappy check if you can switch to Operator’s View (CTRL+E).
Then type sct testnet and try to execute ifconfig
Operator! Do know that the issue in a network scenario similar to yours in pending investigation which should be concluded in hours to follow
Have same issue I am under NAT, needed port open and if i run ifconfig I see this
[Auto-Detected settings]:
Local IP: 192.168.5.22Public IP: 109.121.61.25
NAT: you are behind a NAT (109.121.61.25)
[Virtual Interfaces]:
lo:
flags = 73<UP, LOOPBACK, RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX bytes 12878 RX errors 0 dropped 0 overruns 0 frame 0
TX bytes 0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0:
flags = 4163<UP, BROADCAST, RUNNING, MULTICAST> mtu 1500
inet 109.121.61.25 netmask 255.255.255.0 broadcast [Kademlia]
RX bytes 0 RX errors 0 dropped 0 overruns 0 frame 0
TX bytes 0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth1:
flags = 4163<UP, BROADCAST, RUNNING, MULTICAST> mtu 1500
inet 0.0.0.0 netmask 255.255.255.0 broadcast [disabled]
RX bytes 0 RX errors 0 dropped 0 overruns 0 frame 0
TX bytes 0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Looks like im behind NAT
and eth0 is bound to my public IP. Dont know if this should be like that
Since GRIDNET Core reports you being behind a NAT, it would attempt to bind the UDT (UDP) socket to 192.168.178.22.
Is 192.168.178.22 a valid address from the perspective of your local computer?
yes 192.168.178.22 is its local IP adress with 192.168.178.1 being the router adress
Should updating to Win 11 prevent this issue?
ok updating to windows 11 22H2 led to the same error
the issue is strange in that well, some people (including us) run on such configurations (…) the are configurations everything has been tested on and yet we’ve already verified this on internal VMs after fresh installs of Win10 22H2, let us see how it goes further (…)
that’s the config we use on some of our development machines.
This update should have resolved.
Thank you for your reports, Operators.