Describes how packets are sent and delivered through firewalls from one application to a remote service over the Internet. Explains the necessity of port addresses, used with IP information.
I've watched at least five or six videos in an effort to understand this concept and this is the first video that describes what the port actually IS! It's an opening in a firewall designated for certain types of traffic. THANK YOU DAVE!
I know very little about internet and I am a non-native speaker, but I am still able to fully understand what you said. You explained everything very clearly. Thank you very much!
Great video! Perhaps one detail mussed is that port 80 is the default HTTP port. HTTP is a protocol which can use any port number. There should be a service listening on that port in the server.
This is great, but how does a local OS firewall know what to allow back into the client? does the firewall open an outgoing port automatically in stateful manner and allows the local OS to listen on that port?
Thank you for the video. If a firewall generally allows outgoing traffic, will it allow spyware to send out info if the spyware was installed before the fire wall? does spyware create its own special ports?
yup.. that is why if you have a trojan on your computer. It makes an 'outgoing' connection to a hacker site and they can then find their way back into through the firewall to control your machine, because it is now 'solicited' traffic. (Basically, that is true.. some firewalls now attempt to look into the message further to see what is happening and potentially block it)
Hi! Awesome video! Thanks a lot. I would like to ask something: So you said port 80 is for http protocol and 110 is for POP protocol. So whey doesn't John uses those instead of 1000 and 1100 respectively?
Thanks for the video. What limitations does the max number of allowed port numbers set for the system? Does it set max number of processes allowed to run at a time?
Hi! I understood the port concept! But I need a small clarification, when we open a web browser and an e-mail on our desktop, on what ports does the data move out, is it something like what I have read on different books, our desktop randomly chooses a port number from 1024 to 65535 and send the data out, but while coming back the data actually goes to the designated port? Is it like this? Or have I gone wrong somewhere? Please clarify.
you open a web browser.. you request a page using a packet. The packet sent out has a Destination port address of 80 because it is going to a web service.. the packet has a Source port address of.. say.. 48000. The firewall on the web server allows Destination port 80 traffic so the packet passes. The Destination port address of 80 routes the packet to the Web service. The web service sees this comes from port 48000 so the return traffic from the web server has a Source port address of 80 and a Destination port address of 48000.. The packet enters the client machine and the software see.. ahh.. this has a destination port address of 48000 and I know that the browser which is open has registered that port.. so I'm going to send the packet to the browser application
Nice explanation. Do you have any videos regarding the TCP/IP and TLS protocols? Or source recommendation where I could read more about these topics? I have some basic knowledge of how they work but not quite sure if it's correct.
With a firewall, any unsolicited traffic is blocked. However, Port Forwarding allows some inbound unsolicited traffic. For instance: you can setup a rule so that anything inbound for port 60 will be directed to internal machine IP address of X. So any unsolicited packet received that has a destination of port 60 will be forwarded to Machine X which is in the internal network. This is the only way unsolicited traffic enters the internal network.
Dear Sir, I need some clarification regarding ports number used. why did u used 1000 for web and 1100 for email instead of their own 80/443 and 23 respectively. looking forward for clarification. thanks for being so informative.
There are source ports and destination ports in every 'message' that gets sent.. The SERVICES (like the web server) use port 80. The client that requests a web page uses its port address of 1000 (or some high port number). So the client sends an HTTP request with a DESTINATION port address of 80 .. this goes TO the web server. The SOURCE port address in that message is some high port number that can be relatively random as it comes from the client. All server services need to use port numbers that are known to everyone; so that everyone can send them messages. Clients don't need to use a public number, they just pick a high port number.
You've missed something here.. tell me the time in video where your question is.. The server does NOT allow a random request with a random port.. A server will allow incoming requests only from WELL KNOWN ports that it is configured to allow.. When it returns traffic to the sender, it will use a random port for its reply.
I've watched at least five or six videos in an effort to understand this concept and this is the first video that describes what the port actually IS! It's an opening in a firewall designated for certain types of traffic. THANK YOU DAVE!
10 years later, this video is still super useful, it's easy to understand the concept without any strugglings
I really appreciate it 🙏
Finally a good explanation. Thank you! Especially for the visuals, I've found I have a hard time understanding stuff if I cannot visualise it.
Really good visual details and instructions. I really appreciated your teaching style!
All these years poking around my various rigs and now that I'm studying for A+ 1001 this made some light bulbs activate. Thank you! 👍🏻
I know this is 9 years old, but you really saved my ass. Thank you.
Finally someone explained it as a whole. Its so easy to understand but others make it more complicated than necessary.
Watched multiple videos. Only one accurate enough. Good Stuff man. Subscribed .
10 year old information and its still useful to this day
Great explanation, thanks so much for this. The visuals and pacing were perfect
That is a very good ilustration of how TCP Ports and Firewalls work. Thx!
Thank you very much! This cleared up a lot of my questions that wasn’t explained well in the book I was reading.
I think you did a very solid job in this video! Thank you! It helped me understand how ports are used a lot better!
this is perfect. your explanation, the way you present difficult concept in simple way. you are really a great teacher
Brilliantly explained! I can use this in my computing lesson ...thank you!
Very well explained, i have always been intrigued as to how ports work and this was a very nice video, thanks for sharing.
I know very little about internet and I am a non-native speaker, but I am still able to fully understand what you said. You explained everything very clearly. Thank you very much!
Fantastic Dave, very well done, very clear, very practical without getting too technical, and easy to understand, thanks from Suraj, Vadodara, India
I really appreciated your teaching style! I hope to watch more.
Highly informative. Awesome sir. Thank you❤🍻
That was a great explanation! Now I get why ports are listed as established or Listening.
finally a really clear and high quality video that makes things very clear for me. thanks
this is brilliant, dave. well done! and thank you.
Very good explanation - many thanks
Thank you so much for that clear and concise explanation!
Hey @Dave, This is the great explanation!! Thanks a lot!!👏
Wow, you are a incredible teacher! Best regards
So good, so nicely explained...thank you...looking forward to more videos
Very clear explanation! hope u make more videos. Thanks!
I appreciate the visuals, teacher at school only talks and its hard to imagine everything.
Very helpful description - thank you.
Great useful video! The pictures helped in understanding.
Great video, very clear...thanks!
Thank you Nigel Mansell!
great stuff, clean and clear
nice one. thanks. i found your explanation very helpful
Thank you. this really helped me out.
easy to follow and thorough explanation, thank you!
Thank you, this helped me get a better picture of the use of IP addresses and ports, hopefully it helps me write better backend code in the future 🙏🏽
Really good explanation, finally I understand what happens ;)
Great Explanation. Thanks a lot Sir.
Thank you. Great explanation. I wish I could give you 2 thumbs up...
Very understanding video. Thank you!
Really great vid. Appreciated it!
Thank you for this beautiful explanation.
Great video! Perhaps one detail mussed is that port 80 is the default HTTP port. HTTP is a protocol which can use any port number. There should be a service listening on that port in the server.
Thanks mate, that was quite helpful..
amazing explanation! clear!
This video is amazing! Thank you!
Just awesome. Many thanks!
Thanks for that clear explanation.
ur video is helpfull so far !!
Great video, thank you!
Great tutorial and it helped me a lot. Thanks......................................
Great explanation!
Very useful , simple and good explanation . Thank you sir .
Awesome Explanation...very clear
Quality explanation. Kudos to you sir
You made it simple. Thx a lot
nicely explained!
Wonderful explanation!
beautifully explained- thank you sir
Crystal clear man
very nicely explained!
best explanation ty teacher diagram made me to understand the concept so good tyyy
perfect!!!! thanks a million
That was great bro, Thanks
awesome and visible!
Nice video Dave. Have been looking for a video on Ports and IP Addressing and did not find any good ones.
you helped me so much
cristal clear , thank you so much Sir
ports are holes in firewalls...great explaination
Many many thanks.
very well explained.
Thank You, Sir
sir you nailed it
Can you share more of your lectures ?
very helpful thanks
thank you
Very well explained
This is great, but how does a local OS firewall know what to allow back into the client? does the firewall open an outgoing port automatically in stateful manner and allows the local OS to listen on that port?
Thanks man
Thank you for the video. If a firewall generally allows outgoing traffic, will it allow spyware to send out info if the spyware was installed before the fire wall? does spyware create its own special ports?
yup.. that is why if you have a trojan on your computer. It makes an 'outgoing' connection to a hacker site and they can then find their way back into through the firewall to control your machine, because it is now 'solicited' traffic. (Basically, that is true.. some firewalls now attempt to look into the message further to see what is happening and potentially block it)
Great! But what port Fred is using to send data back to John? Is it a random one?
Well explained.
Hi! Awesome video! Thanks a lot.
I would like to ask something:
So you said port 80 is for http protocol and 110 is for POP protocol. So whey doesn't John uses those instead of 1000 and 1100 respectively?
See a few comments above.. 80 & 110 are the "well known port numbers" and used by SERVICES (server), not by clients.
Thanks for the video. What limitations does the max number of allowed port numbers set for the system? Does it set max number of processes allowed to run at a time?
I'm not sure I understand the question. There are 65000 ports available. No limitations for the system.
High quality content
nice one!
Thanks!
Thank You
Thank you sir
Thank you
Hi! I understood the port concept! But I need a small clarification, when we open a web browser and an e-mail on our desktop, on what ports does the data move out, is it something like what I have read on different books, our desktop randomly chooses a port number from 1024 to 65535 and send the data out, but while coming back the data actually goes to the designated port? Is it like this? Or have I gone wrong somewhere? Please clarify.
you open a web browser.. you request a page using a packet. The packet sent out has a Destination port address of 80 because it is going to a web service.. the packet has a Source port address of.. say.. 48000. The firewall on the web server allows Destination port 80 traffic so the packet passes. The Destination port address of 80 routes the packet to the Web service. The web service sees this comes from port 48000 so the return traffic from the web server has a Source port address of 80 and a Destination port address of 48000.. The packet enters the client machine and the software see.. ahh.. this has a destination port address of 48000 and I know that the browser which is open has registered that port.. so I'm going to send the packet to the browser application
Nice explanation. Do you have any videos regarding the TCP/IP and TLS protocols? Or source recommendation where I could read more about these topics? I have some basic knowledge of how they work but not quite sure if it's correct.
Look on my playlist "Networking". All stuff I have on TCP is there.
I understood solicited inbound traffic here. But can some one explain how port forwarding and unsolicited inbound traffic.
With a firewall, any unsolicited traffic is blocked. However, Port Forwarding allows some inbound unsolicited traffic. For instance: you can setup a rule so that anything inbound for port 60 will be directed to internal machine IP address of X. So any unsolicited packet received that has a destination of port 60 will be forwarded to Machine X which is in the internal network. This is the only way unsolicited traffic enters the internal network.
Dear Sir,
I need some clarification regarding ports number used. why did u used 1000 for web and 1100 for email instead of their own 80/443 and 23 respectively. looking forward for clarification. thanks for being so informative.
There are source ports and destination ports in every 'message' that gets sent.. The SERVICES (like the web server) use port 80. The client that requests a web page uses its port address of 1000 (or some high port number). So the client sends an HTTP request with a DESTINATION port address of 80 .. this goes TO the web server. The SOURCE port address in that message is some high port number that can be relatively random as it comes from the client. All server services need to use port numbers that are known to everyone; so that everyone can send them messages. Clients don't need to use a public number, they just pick a high port number.
Thanks alot i 've a clear answer to my doubts now
hey, i don't get it, why does the server's firewall allow a random request with a random port
You've missed something here.. tell me the time in video where your question is.. The server does NOT allow a random request with a random port.. A server will allow incoming requests only from WELL KNOWN ports that it is configured to allow.. When it returns traffic to the sender, it will use a random port for its reply.
Very helpful
yes it is. Are you a computer science student?