Video Game Server - Port Forwarding Service Type
Video Game Server - Port Forwarding Service Type
What model of router are you using? I encountered a similar problem with port forwards not working on my older device. Consider these steps first: Check if the router's firewall is active. If it is, try placing your computer's local IP in a DMZ (if supported) or adjust the firewall settings on the router. It could also relate to your computer's firewall.
It works thanks to the NAT capability. The loopback doesn’t send him past the router—it just sends him back to himself. When using a public IP, he’ll be sent from the router straight to the loopback. This lets him reach the server he created. Having this functionality is essential since you can always connect to yourself via the loopback or your assigned IPv4 address.
It doesn't function properly. Hairpinning requires a specialized enterprise router with extensive configuration settings. You likely don't grasp how loopback operates. If the request reached his public interface, it would loop back through his router, which would then respond with its local IP. The PC would receive the reply from that IP and might discard it due to unexpected behavior. Most routers detect packets seeking their own IP address and discard them because of hairpinning. A loopback address operates independently on its own interface with its own IP. This whole process is heavily tied to loopback functionality. So, it won't work as intended.
It's possible because of reverse lookup features. Devices can easily check their local IP against public records. This works for all computers and servers without issues. If you can't reach your own public IP, it means your setup might be problematic.
You clearly don’t understand how routing functions or why hairpinning is structured this way. What you’re describing involves NAT, where the PC communicates with the router, which masks your local IP and forwards the public address. When the packet returns, the router removes the public IP and restores your local one before sending it back. On the other end, when you try to reach a device using your own public IP from a local address, the router receives the reply and mistakenly sends it back to itself, causing the PC to detect an incorrect source and drop the packet. This is fundamentally different from what you’re explaining. To connect to your own public IP locally, you need a loopback address like 127.0.0.1—it stays on the same interface. In everyday consumer setups, this isn’t feasible.
I don't understand your tone or the details you're referring to. Let me explain it again simply. You're suggesting that if I set up a Minecraft server on my PC, I won't be able to connect using my public IP because the router might drop the data. My response is that I can still do this since the router will forward the packets to the computer requesting them. If it doesn't work, you could check your connection by visiting a nearby library or asking someone with more networking experience. It sounds like you're trying to sound confident but might need more clarity. Try being a bit more polite and test it yourself before concluding it won't work.
I added some clear explanations and included relevant images to help you better understand the setup. My PC is at 192.168.10.100, and I set up a Minecraft server with a port. You can see the connection in the attached picture. If you can't reach it using your public IP, let me know. How do you think I’m connected to Minecraft?