What The Heck Is Port Forwarding?

Awesome video!

THANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOU

Assetto Corsa server struggles united us here folks

Thanks! Good video.

Does all routers allow port fowarding?

you want to dislike

So what’s it good for does it make connection better for gaming?

my router is so bad that i have to use upnp to open ports with a tool bexause it cant open ports on its website.

Is port forwarding safe for port 25565(minecraft).

LOL I’m Here for mc and he says the port.

Man I just wanted to store media on a NAS and let my family access it. Didn't know it got so complicated with security

port forwarding isn't an option in my router's site

brings me back to my torrenting days

I port forwarded a couple ports for a game and when I open my internet tab a unidentified network appears is this ok or is something wrong?

My router's port forwarding settings are so weird

so does it skip firewalls or like how does it actually help?.... kinda pointless video when all it does is overview a 10 minute process in 5 minutes and just be like "bc its more gooder, bro"

All is good until you get a CGN ip

You forgot to mention CGNAT

Excellent explanation. Well developed; succinct; comprehensive !! Thanks !!!

NICE AWES0ME KEEP_IT_UP! ✨🎉✨🎉✨🎉🎉🎎🎭🎎🎭🎎🎭🎗🎗🎗🎑🎑🎑🎑🎑🎑🎑✨🎆🎆🎆🎆🎆🎆🎀🎀🎀🎀

Someone forgot to mention NAT and GNAT smh

Thanks for the video!

That one piece of glitter on Riley's shoulder was so distracting.

👍👍

Can't stop focussing on white dot on his left shoulder what is it??

Watching this after setting up tonnes of srv port forwarding on my domain lol plus onto my server

Oh my gosh.. The thumbnail. 😂

Cloudflare and Tunneling is the way to Go :D

I port forward the f*ck out of my routers. Interestingly I did a port forward to an external IP once just to bypass a bad path. It worked.

nice info

Always wondered the same with uTorrent.

Why didn't you mention UPnP? surely its relation to port forwarding would be relevant

@Techquickie, you got it wrong.

The "Network Address Translation" (or NAT) functionality on your router was never meant to be a security feature, but rather, a means of sharing a single public IPv4 address assigned by your ISP with multiple devices by assigning them private IPv4 addresses.

The reason we need this for IPv4 is because IPv4 can only provide up to 4,294,967,296 unique addresses, which seemed like plenty at the time IPv4 was ratified--back in the early 1980s--but now, with how popular the internet has become, 4,294,967,296 unique addresses for every device connected simply isn't enough. NAT was developed as a temporary solution to this problem while we transition to IPv6--which can provide over 340 undecillion unique addresses. This is also why NAT is almost never used in consumer IPv6 implementations--because 340 undecillion unique addresses is more than enough for every single grain of sand on earth to have it's own IP address.

Here is a simple description of how NAT works:
When a device on your local network wants to connect to a server, the device will issue a request to that server. The device will write a "source port"--where the device listens for replies from the server--in the packet header. What your router does is creates a temporary port mapping for that source port, and then replaces your device's private IP address with your router's public IP address in the "source IP" portion of the packet header, and then forwards the packet to the destination server residing on the public internet. The server then sends a reply to your router on that source port, and from that, your router knows to forward the reply to your device.

If you just have client devices contacting servers via the internet, this setup works perfectly fine, and your ISP doesn't have to assign a public IP address to every single device you own. However, this completely falls apart the moment you try to run a server on the public internet. When an outside device tries to contact your server using your router's public IP address, your router has no way of knowing which inside device to forward that request to. Consequently, your router simply discards the request, your server never receives it--because it was discarded by your router--and the outside device never gets a response from your server.

As a side effect, this actually improves the security of your local network, since outside devices can't contact any of your inside devices by default.

What a port forwarding rule does is creates a static port mapping to your inside server. When an outside device tries to contact your server, the router knows to forward that request to your inside server, which then establishes a connection over the internet with the outside device.

In short, the NAT functionality of your router has one job, and one job only. To share a single public IP address assigned by your ISP among all your devices. THAT'S IT! NAT is NOT a firewall!

Ports are part of the Application layers of the TCP/IP or OSI model.

LUL Teamspeak.

A POE Texas ad is linked to this video oh the irony

My local IP starts with 10.199...

I suppose it's fine in a layman speak way. 99% of viewers have literally only one router box between them and the net. However "port forwarding" has nothing to do with firewalls. All ports for UDP and TCP will happily forward through routers. It's how the internet works at the IP level.
"Port forwarding" is part of address translation and masquerading. (NAT) Your ISP gives you 1 IP. You have a dozen machines. So your router masquerades as all dozen of them. With this in place there is no logical route to any of them, so connection tracking is added to allow "established and related" replies to connections initiated inside. Port forwarding is usually a static desintation mapping in NAT and a masqueraded reply path.
Compare that to having a block of IPs from your ISP and it's entirely up to you to set up the routing for this. If you simply enable forwarding on the router, it will route ALL IP traffic to those boxes.
Finally this ^^^ is were firewalls come into play. In combo or in addition to the router the filter, reject, drop, modify, mangle and log traffic.
It get debatable when you start considering port redirected traffic. Firewall or layer 3 router?

so can someone explain to me in layman's terms, how i can get an open nat type on my console's? (Xbox, switch)

Is there any port 69420? Or port 69666? Or 420666?

This video conflates opening ports in the firewall (bypassing security) with port forwarding (bypassing NAT). While there can be some overlap, those are two different things.

I never have to port forward for modern games, just things like openttd multilayer.

Brings back memories of dedicated servers for counter strike source

i love this thank you for this great explanation

Me: laughs in /24 block of IPv4

There are many port forwarding videos yet none talk about CG NAT or carrier grade NAT. CG NAT will make port forwarding a hell for you. It's basically sharing your global ip adress with multiple people. Call ypur ISP and tell them to remove you from CG NAT and port forwarding will start working. I had to do that in my case idk about you other people.

Great video, i love you technology ned flanders