Configuring port forwarding for your dedicated server running Wreckfest on Virgin Media
Configuring port forwarding for your dedicated server running Wreckfest on Virgin Media
Is the wreckfest server active? If it isn't, it won't be able to connect on the ports you've set up. Is your WAN address (verify via whatsmyip.org) not protected by CG-NAT? Your WAN IP shouldn't begin with 192.168.x.x, 172.16.x.x, or 10.x.x.x. CG-NAT is typical for ISPs that have exhausted IPv4 addresses. Using CG-NAT blocks port forwarding.
Thank you for your feedback. I've tested both scenarios, and it seems the issue varies—sometimes it works and other times it doesn't. The WAN IP address shown in the command line appears to differ from what's displayed in the IP configuration tool.
Your router displays your WAN IP address, while your local network will use a private range like 192.168.x.x. CG-NAT means the router receives the WAN IP from either 10.x.x.x or 100.64.x.x through 100.127.x.x, and the public IP you see online differs from that private one.
Ensure you’re not stuck with CG-NAT, which can also accept IPs starting with 100.64-100.127. Verify that the IP you’re forwarding (your PC’s address) remains consistent and hasn’t changed. Confirm the server isn’t configured to listen on localhost. To test, run a traceroute and observe the hops after your router; if the IP falls within a CG-NAT range, you’re behind.