Great Explanations. Very though job explaining all this complex stuff.You are a really good teacher. Now i see why i cant make POST requests from my localhost to a service API. Thank you so much.
Adam Zerner, thanks, but I installed ngrok and can't figure out how to share the link of the site I'm building on the localhost on my Mac with MAMP! When I open the ngrok exec file it opens in Terminal and says "logout" at the bottom and below that it says [Process Completed]. When I open Terminal and type ngrok http 8888/wordpress it says: -bash: http: command not found. I have looked at every video on YT on how to do this and they all assume I know certain things that I don't know so I hit a wall every time. Same with the "instructions" at the ngrok website. Any suggestions? Thank you.
You have the vast amount right, I think. Your idea of "private addresses" is simply called an "non routable IP address" and there are three standard ranges. Anything in the ranges 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 will not be forwarded by any Internet router - they are intended for internal use only and are not routed. Your average home network is 192.168.0.*, for example. This has two key safeties: your home network doesn't get out so a bad network card won't take down your ISP, and no one outside can address your home computer since the router won't forward the packets. NAT is the process of "network address translation" on a connection from one side of the router to the other. A computer connection is generally 4 numbers: my IP and a port, and a remote IP and port. The router/firewall uses 8 numbers... 4 inside and 4 outside your network. As traffic crosses the router, it replaced the non-routable address with a public IP (routable). Generally, the other end of the connection will also pass through another router or firewall, too. So it all works to make private IP services safer, just like it does for home. The FROM port used for requests are pretty random, but generally more than 1024 (of 65,000 available). The TO port is usually a "well known" port (less than 1024) either specific to an application, or issued by "Internet Assigned Number Authority" (IANA). That's why normal web servers use port 80, and ssl uses port 443... If I know the public IP address of Google, I can reach their web server running on normal ports, and their email has a standard port. So, a request starts on a private address and random port, to a public address and common port and my firewall translates my address from private to public. On the other end, the firewall forwards/translates to a private IP and an internal port (maybe not the common one). This let's the server provide more websites as a hosting service, or load balancing, or what have you. But that's all just the jargon... you've got it right in you explanation.
I'm not what you call an expert, just a little less lost, or under the delusion I am :-). Being able to name things is useful to understand and discuss complicated stuff. Like being able to ask for meat or gravy rather than growling "food...!" :-) The ngrok tunnel is simply an outward connection to a streaming server, too. Your firewall generally allows any connection to leave, and only port-forwarded connections inward; by keeping the connection open, you're opening a "tunnel" through the wall, and allowing traffic from ngrok to use that connection. The only difference between a "request" and a "tunnel" is duration. A request is usually a brief transaction, and a tunnel is more durable, no different than watching TH-cam or Netflix. Once you get over the hurdles of firewalls and routers, you dig into protocols and the abstract stuff in the network stack :-) thence comes the rabbit hole and many multicolored rabbits.
> Being able to name things is useful to understand and discuss complicated stuff. Like being able to ask for meat or gravy rather than growling "food...!" :-) For sure! > The only difference between a "request" and a "tunnel" is duration. A request is usually a brief transaction, and a tunnel is more durable, no different than watching TH-cam or Netflix. Huh, that's a great insight! That definitely clears things up for me. One less black box that I take for granted. - - - I appreciate your contribution. Most people with my level of understanding wouldn't make videos or write blog posts, because they fear that they don't know enough. The way I see it, you don't necessarily have to know _that_ much in order to help others. As long as you can contribute something, it's better than nothing. And often times beginners do a good job of teaching other beginners because they know what the likely points of confusion are. But it is great when more experienced people like you contribute and clarify things. That way, you kinda get the best of both worlds (the friendly perspective of the less experienced person, and then the more experienced person to fill in the gaps). That was a little rambly, I hope it made sense. Just wanted to reflect on a good experience on the internet and express my thanks :)
As I said, pretty much on the money without the jargon :-). Nothing worth building a fire or putting you down. When I went to college, I learned the real value of writing papers was to clearly "connect the dots" of and idea (aka support the thesis). I see your video the same way, just more animated... connecting the dots. Getting the terms right helps, but if the dots don't make a cat video/gif ... Terms don't help. Jargon without the rest is just BS and usually accompanied by bragging and bullying. I'd rather see understanding how it works in simpler terms than a boat of jargon without a clue :-) and you know you've seen it.
This was actually very helpful! I knew what ngrok was but I didn’t really get how it worked without port forwarding.
Great Explanations. Very though job explaining all this complex stuff.You are a really good teacher. Now i see why i cant make POST requests from my localhost to a service API. Thank you so much.
This was amazing! Thank you so much! Wish you were making more content, you've got a gift!
Superb explanation. It doesn't get simpler than this. Thanks bro.
This was very helpful. Thanks bud.
Adam Zerner, thanks, but I installed ngrok and can't figure out how to share the link of the site I'm building on the localhost on my Mac with MAMP! When I open the ngrok exec file it opens in Terminal and says "logout" at the bottom and below that it says [Process Completed]. When I open Terminal and type ngrok http 8888/wordpress it says: -bash: http: command not found. I have looked at every video on YT on how to do this and they all assume I know certain things that I don't know so I hit a wall every time. Same with the "instructions" at the ngrok website. Any suggestions? Thank you.
Very helpful me to understand ngrok. Thanks Adam
Now what is the node that lets me connect to ngrok ? Does it my router ?
i think so. probably
Thanks a lot, good work. Your teaching skills are outstanding. Keep doing more videos on angular 🙂
COOL TUTORIAL. GOOD LUCK ALWAYS....💯👍👍👍👍👍👍👍
Great video with clear and detailed analysis
It was a great and clear explanation, thanks a lot, you deserve more and more subscribers ❤
You have the vast amount right, I think. Your idea of "private addresses" is simply called an "non routable IP address" and there are three standard ranges. Anything in the ranges
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
will not be forwarded by any Internet router - they are intended for internal use only and are not routed. Your average home network is 192.168.0.*, for example.
This has two key safeties: your home network doesn't get out so a bad network card won't take down your ISP, and no one outside can address your home computer since the router won't forward the packets.
NAT is the process of "network address translation" on a connection from one side of the router to the other. A computer connection is generally 4 numbers: my IP and a port, and a remote IP and port. The router/firewall uses 8 numbers... 4 inside and 4 outside your network. As traffic crosses the router, it replaced the non-routable address with a public IP (routable). Generally, the other end of the connection will also pass through another router or firewall, too. So it all works to make private IP services safer, just like it does for home. The FROM port used for requests are pretty random, but generally more than 1024 (of 65,000 available). The TO port is usually a "well known" port (less than 1024) either specific to an application, or issued by "Internet Assigned Number Authority" (IANA). That's why normal web servers use port 80, and ssl uses port 443... If I know the public IP address of Google, I can reach their web server running on normal ports, and their email has a standard port.
So, a request starts on a private address and random port, to a public address and common port and my firewall translates my address from private to public. On the other end, the firewall forwards/translates to a private IP and an internal port (maybe not the common one). This let's the server provide more websites as a hosting service, or load balancing, or what have you.
But that's all just the jargon... you've got it right in you explanation.
Thanks for the information! To be clear, I'm no networking expert, so it's good to get the thoughts of someone more knowledgeable.
I'm not what you call an expert, just a little less lost, or under the delusion I am :-). Being able to name things is useful to understand and discuss complicated stuff. Like being able to ask for meat or gravy rather than growling "food...!" :-)
The ngrok tunnel is simply an outward connection to a streaming server, too. Your firewall generally allows any connection to leave, and only port-forwarded connections inward; by keeping the connection open, you're opening a "tunnel" through the wall, and allowing traffic from ngrok to use that connection. The only difference between a "request" and a "tunnel" is duration. A request is usually a brief transaction, and a tunnel is more durable, no different than watching TH-cam or Netflix.
Once you get over the hurdles of firewalls and routers, you dig into protocols and the abstract stuff in the network stack :-) thence comes the rabbit hole and many multicolored rabbits.
> Being able to name things is useful to understand and discuss complicated stuff. Like being able to ask for meat or gravy rather than growling "food...!" :-)
For sure!
> The only difference between a "request" and a "tunnel" is duration. A request is usually a brief transaction, and a tunnel is more durable, no different than watching TH-cam or Netflix.
Huh, that's a great insight! That definitely clears things up for me. One less black box that I take for granted.
- - -
I appreciate your contribution. Most people with my level of understanding wouldn't make videos or write blog posts, because they fear that they don't know enough. The way I see it, you don't necessarily have to know _that_ much in order to help others. As long as you can contribute something, it's better than nothing. And often times beginners do a good job of teaching other beginners because they know what the likely points of confusion are.
But it is great when more experienced people like you contribute and clarify things. That way, you kinda get the best of both worlds (the friendly perspective of the less experienced person, and then the more experienced person to fill in the gaps).
That was a little rambly, I hope it made sense. Just wanted to reflect on a good experience on the internet and express my thanks :)
As I said, pretty much on the money without the jargon :-). Nothing worth building a fire or putting you down. When I went to college, I learned the real value of writing papers was to clearly "connect the dots" of and idea (aka support the thesis). I see your video the same way, just more animated... connecting the dots. Getting the terms right helps, but if the dots don't make a cat video/gif ... Terms don't help. Jargon without the rest is just BS and usually accompanied by bragging and bullying. I'd rather see understanding how it works in simpler terms than a boat of jargon without a clue :-) and you know you've seen it.
Great Explanations. Very thorough. Thanks.
john j kkk
Good Explanation there thanks man
Thank you so much Adam for this video. Thats great video. Respect ++
Nicely explained. Thanks
Excellent explanation... Thanks adam
Very Helpful...thanks buddy!
awesome work
Great explanation.. keep posting videos about networking
Superb! Thank you for a very clear tutorial A*****
Thanks Buddy! :)
Great explanation
great explanation. Thank you.
It's awesome! Thanks for sharing it man
Thanks for the educational vid : )
very helpful bro thank you so much : )
Ur very clear
Very Helpful!
Best explanation ever
A doubt brother. If our router can remember who requested what, then why can't ESPN remember?
The Router DOES "remember" (hence the name Router). ESPN is not the router in this case.
Okay bro. Got it. Thanks bro.
Thank You
thanks!
Very helpful, Thanks Adam!
Helpful for me to understand NGrok
Thank you