Iptables have always been a mystery and rather complicated. Thanks for demystifying it. Thank you for all your great content delivered with such enthusiasm!
@hnasr3 жыл бұрын
Glad it helped ❤️
@DerrickHayden Жыл бұрын
I've search all over the net for exactly this. Hours of searching and you're the only one covering iptables in this manner. Thank you.
@rolandgerges9246Ай бұрын
this is the most simple yet interesting video that helped me get over iptables after a year.
@russohc10 ай бұрын
Hussein! I've been trying to understand iptables for more than three months and you explained everything in less than 35 minutes in a super happy way!!! We want more hahaha, thanks for the video!
@stolenidentity1152 Жыл бұрын
Perfect tone of voice. Funny and accurate. Kudos to you!
@Demodude1233 жыл бұрын
Thanks Hussein! This is a great tutorial! I work with docker/kubernetes and I never understood their complex iptable chains. I'll definitely keep watching this series to understand how container networks work
@m.m.45893 жыл бұрын
Wow man, I thought ip tables was complicated, but u nailed it. Great examples. Thanks for your hard work
@dacoup5955 Жыл бұрын
Thank you so much, i'm going through a Kali tutorial for pen testing studies to eventually pass my OSCP, i love your delivery and an enthusiasm, much of this was glossed over because its a vast aspect of linux's opensource firewall and you have a clear and concise way of boiling it all down so i can wrap my head around its many functions and uses, currently working on port forwarding 80 HTTP traffic to sslstripper on port 8080 and i was curious what that process actually looks like behind the curtains ... Appreciate the feedback and i just subscribed.
@Z3rgatul8 ай бұрын
This is the best format I could imagine to explain iptables. Many thanks
@90hijacked2 жыл бұрын
you're a good presenter, down to earth and seem genuinely enthusiastic. cheers :) It's always a pleasure seeing people learning and/or hacking about with the same topics as you
@matches04237 ай бұрын
Thanks for the video!! Clears a lot of things up for me. The bottleneck of using socat disappeared after I switched to iptables.
Dude, AMAZING explination. Thank you so much. I've spent hours looking for the information like this. And you made it so easy to comprehend! THANK YOU SO MUCH. Keep the awesome work!!
@totti3432 жыл бұрын
Love the storytelling. Great video!
@fujinafiul60442 жыл бұрын
Oh man, you are the life saver.. very few dare to cover such boring topics with such excitement.. love you man ❤ you just saved me hours of work...❤
@jojojojola Жыл бұрын
boring? its interesting af
@yetanother77543 жыл бұрын
My Friend ... Amazing explanation .. Loved it! gonna recommend it to my friends
@TaniaTebaldi2 жыл бұрын
Wow after hours searching iptables information, I am here, you're amazing teacher, thanks a lot! I'm working with mitmproxy in transparent mode for testing iot devices, tomorrow I will try to make my iptables. Greetings from Italy!
@leo-phiponacci2 жыл бұрын
It is really demystified like he said, thank you very much Hussein
@Kifter19832 жыл бұрын
Fantastic tutorial. I loved that you mentioned you wasted hours because of ip forwarding as exactly the same happened to me being a newb to ip tables ha!
@AntonSokolov-i5k6 ай бұрын
Thanks man!!! Topic makes sense now! Loved the way you presented, you got soul man 😎😎😎
@prophetjamz943 ай бұрын
Studying for my LFCS exam right now and I just kept getting stuck on the commands. Thanks so much for explaining this
@pging8328 Жыл бұрын
hey mate, i appreciate your videos very much which you put on the internet.
@ChristianAltamiranoAyala3 жыл бұрын
Such a insightful video, congrats Hussain
@hnasr3 жыл бұрын
Thanks 🙏
@yashas8238 Жыл бұрын
I liked how you stressed the important things, thks you saved me a lot of time!
@steamrangercomputing Жыл бұрын
Genuinely informative video. Great job!
@EddyCaffrey3 жыл бұрын
Iptables is great 👍🏾. Good explanation. Thanks 🙏🏾
@pratikdaigavane11113 жыл бұрын
sudo iptables -A OUTPUT -m statistic --mode random -p udp --probability 0.77 -j DROP Useful in an online class when professor asks you a question and you don't know the answer 😜
@hnasr3 жыл бұрын
Evil 🦹♀️ Will explain this in next episode! This is the filter table and Pratik here is dropping 77% of outgoing udp packets. So it forces video call to lag.
@pratikdaigavane11113 жыл бұрын
@@hnasr Can wait to watch next episode!!
@OfferoC3 жыл бұрын
Very nice. Thank you. Keep these videos coming!
@rightangleoverseas23913 жыл бұрын
This is pure value ! Thank you so much for this !
@mathisart3 жыл бұрын
Finally someone who understands this and explains it in a way that's understandable! Jesus bless you
@root1101 Жыл бұрын
Thanks, that was rather useful. The lack of use cases in reference materials is aggravating.
@yassirhassan20633 жыл бұрын
Great content, great person. proud of you man.
@hnasr3 жыл бұрын
❤️
@ArtusMagnificus3_2_1Ай бұрын
Awesome vid, thanks for explaining
@bun4bun3 жыл бұрын
Just sent a donation on paypal for your efforts. Thanks a lot for the video. You saved me a lot of trouble :)
@martinfurstenberg2281 Жыл бұрын
Thanks for the explanation. Awesome Job.👍
@islem12633 жыл бұрын
If you press Ctrl+F5 you can force the browser to serve you a new non cached version
@phoenixray35123 жыл бұрын
Very informative thank you for sharing, I will be waiting for more.
@shashidharnagraj8962 жыл бұрын
Thank you very much, this video has helped me learn a lot.
@romans44713 жыл бұрын
Thank You very much! And it was a great idea to lowercase everything ( 07:00 ) o it became more meaningful.
@totopops98 Жыл бұрын
nice . very clear way to explain !
@saad.833 жыл бұрын
Very interesting to watch!
@lajoskicsi69103 жыл бұрын
Aweesome! Love this IP table course. I want to see more!
@mohamedhabas73913 жыл бұрын
Yaaay finally Linux admin stuff 😍😍😍😍
@adamstrejcovsky8257 Жыл бұрын
could not have been easier. thanks a lot
@ivanramadhan51853 жыл бұрын
Thanks for the explanation, it's very helpful.
@jlxip3 жыл бұрын
This video is absolutely outstanding. Thank you
@pging8328 Жыл бұрын
hey man you saved me on the tip to to enable ip forwarding. I was literally about to smash my head against the computer
@mdshehab8947 Жыл бұрын
Absolutely amazing
@conscium2 жыл бұрын
great video, helped me a lot and it was also entertaining peace
@AshutoshKumardevx3 жыл бұрын
Bro, you are awesome.
@mohammedaris23383 жыл бұрын
Thank you @Hussein , i appreciate your video
@hnasr3 жыл бұрын
❤️
@anisht18382 жыл бұрын
Great work, great value, thank you so much.
@hnasr2 жыл бұрын
Appreciate it!
@robertphillips1247143 жыл бұрын
Great explanation. Thanks very much!!
@bharadwaz7 Жыл бұрын
one of the best video thanks a ton
@kaustubhmane82873 жыл бұрын
way too cool video !!
@okekeebube14263 жыл бұрын
Thanks for helping your viewers avoid hours of reading in just one video
@misterg45483 жыл бұрын
Informative video. But there is also another approach to start an app and let is use the restricted ports without the root permission. The tool is called authbind.
@bobsmithy3103 Жыл бұрын
informative and funny, good stuff
@uwontlikeit Жыл бұрын
The best visualization of the NAT flow I saw so far, the only thing left a bit unclear is the way back, when server responds - how does it do backwards translation?
@rahulcsaple2 жыл бұрын
Amazing explanation.
@alkklajslkdajlk2 жыл бұрын
Thank you for your video :)
@kaczuszka-dt2 жыл бұрын
damn son, I love your content.
@mohamedhabas73913 жыл бұрын
for ip forwarding #this injects the value to the kernel regardless of the destro echo 1 > /proc/sys/net/ipv4/ip_forward
@usamatahseenulhaque91253 жыл бұрын
Great video
@autohmae3 жыл бұрын
30:53 if you hate it, use the --numeric ( -n ) when listing my dear friend :-) PS You forgot to mention what to do after changing the config file.
@hnasr3 жыл бұрын
😍 nice tip that should be the default though :p
@autohmae3 жыл бұрын
@@hnasr I don't know why, but this is very common for lots of commands on Linux, Unix (thus Mac) and also Winows. -n is not the default for any of them. ping, traceroute, netstat, tcpdump, etc.
@hnasr3 жыл бұрын
What is tcpdump? ;) :p
@autohmae3 жыл бұрын
@@hnasr I feel some day you might do videos on tcpdump as well
@syedtahaaziz2668 Жыл бұрын
Please also explain ip masquerade as well.
@synchronizingsynchronize30663 жыл бұрын
creative explanation!
@azul2011ish3 жыл бұрын
Awesome, I love linux!
@francisobwogo63663 жыл бұрын
Thanks. This works.
@hsjsjssnnsjsjs16662 жыл бұрын
Holy fuck I enjoyed watching this😂😂❤️
@PauloGervilla3 жыл бұрын
Just saved my life, thanks! Do I need to do something else to make this configuration persistent?
@johnmark20143 жыл бұрын
THANK YOUUUUU SOOO MUCHH!!!!
@osamaa.h.altameemi55923 жыл бұрын
that was really smooth, thx a ton. Hussein are you aware of any implementations that do the processing thing on the NIC itself (talking about TOE NICs)?
@ehsanshadi8102 жыл бұрын
Thanks bro
@akashagarwal6390 Жыл бұрын
why do we need this exactly? what are its actual use cases in real-world as compared to delegating a request explicitly by some server to another?
@ShueFig3 жыл бұрын
In the example for DNAT & SNAT, in the response from the computer at 192.168.1.3 back to the server, how does the server determine that this response is meant for the computer at 192.168.1.2? I'm assuming the response packet will be something like (192.168.1.3:80 | 10.0.0.2:1234) (sIP | dIP)?
@brod5153 жыл бұрын
It must be using the created ip tables. when the response (192.168.1.3.:80 | 10.0.0.2:1234) is received the server should remember (lookup) that it mapped dIP from 10.0.0.2 => 192.168.1.3 and changed the mapping from sIP 192.168.1.2 to come back to 10.0.0.2. so it should know that if I get a response from 192.168.1.3 , by checking the dIP that must have been a request intended for me that I redirected to 192.168.1.3. and if I check the sIP I can see that the stuff that was supposed to come back to 10.0.0.2 was initially intended to go back to 192.168.1.2
@hnasr3 жыл бұрын
The computer at 192.168.1.3 only knows that the packet needs to go to 10.0.0.2 , its the responsibility of 10.0.0.2 to send it back to 192.168.1.2 thats the job of DNAT .. watch NAT video for more details kzbin.info/www/bejne/iHicaKWsrJaYi9E
@ShueFig3 жыл бұрын
@@hnasr Yup, I actually was asking about how 10.0.0.2 knows to forward this packet back to 192.168.1.2, which I believe @MrBrN197 answered above. Thank you so much for making these videos btw, learnt a ton of new stuff :)
@ShueFig3 жыл бұрын
@@brod515 okay, I kind of figured it was some kind of reverse lookup, thank you! Do you know if there's a name or something I can google to know more about this process?
@thierryalbareda38602 жыл бұрын
thanks, usefull.
@akashagarwal6390 Жыл бұрын
1. is 8080 an ephemeral port from server's side/PoV? 2. Also, does it make the diff between an app server running on 8080 while the web server exposed on 80? 3. is this port redirect the same as port forwarding?
@edgarlip28 ай бұрын
@Husseein - ♦it looks like after the redirect - the packet is going straight to the process - but i know that is is passing the INPUT table before ... and u have omitted this hole important part ! ♦REDIRECT example config - PREROUTING is used for incoming traffic from the out side of the machine ( which u used ) , and "-t nat -I OUTPUT" is used to handle traffic that is originated from the local machine - why did u decided to use the "PREROUTING " ?
@kallingal16627 ай бұрын
Super
@ebu72 жыл бұрын
Assalamualaikum Great channel for programming. Thanks a lot of. I want to you how you setup your raspberry pi. Plzzz tell me???
@pajeetsingh10 ай бұрын
iptables vs ip route? Do they serve same purpose? Why does changes made using ip route does not show up in iptables rules?
@fabwrld57732 жыл бұрын
When their is a reply from 192.168.1.3: 8080 to 10.0.0.2:1234, do we need to have another DNAT rule to send this packet to 192.168.1.2?
@ekaf35444 ай бұрын
❤
@michelef406Ай бұрын
So is nginx basically a wrap around iptables?
@alexbennion90873 жыл бұрын
Thanks, "babes"!
@bayliner43873 жыл бұрын
this is a great help however I'm still quite confused. I'm trying to get my RPi to RPi WireGuard tunnel to allow Access Point traffic on the Client RPi to pass to the internet on the RPi server. Is this possible? I'm assuming I only need to modify the RPi Client ipTables? The Rpi AP Clients are on 10.10.10.X and the WireGuard tunnel is 10.6.0.2 (Client) to10.6.0.1 (server).
@jakke19752 жыл бұрын
So if you have a rule for both tcp and udp (e.g. for a dns server as target), can you do that command in 1 line or do you have to create a separate rule for it?
@SuperMan-rw6iz Жыл бұрын
why nginx if we can use something like this to achieve network control?
@mnj13 жыл бұрын
Hi. In the last example, I wonder, would it also work if you defined both rules in the PREROUTING chain (or both in the POSTROUTING chain)? Why (not?)?
@CharlieArehart13 жыл бұрын
More great stuff as always, Hussein, and thanks. But I had a couple of observations/questions for you and that may help other viewers considering all this. First, you mention the need to enable ip forwarding, as it's off by default in Linux (at 21:25) . I'm a little surprised you didn't elaborate at least a bit (or offer a brief caution) on the possible implications of doing that. I'm new to the topic of iptables myself, so again thanks for the great intro, but I've been burned by making such a change too innocently. :-) A quick poke around the web found a few cautions. I fear that some viewers may not be likely to consider that without your suggesting it. Given how your goal always is to educate and share words of advice, it just seemed a missed opportunity. Or do you think any concern is perhaps overstated? Second, while you understandably picked an http example to keep things simple, it seems that such a use case could be solved at a higher level by a reverse proxy (nginx, haproxy, varnish, etc.). But I don't think you mentioned that. Given the concern above, it seems worth at least a brief mention. Of course you've covered that topic well in the past, but you produce so much great content that most people can't track it all. :-) This would have seemed another one worth offering a pop up link to such a past video. All that said, as one who also likes to share knowledge myself, I realize it's a balancing act. Just trying to help. And I appreciate that this was just a part 1, introducing the wonders and power of iptables with your inimitable style. :-) Again I share these observations here for your viewers, and perhaps also for your consideration in future videos, assuming you'd not already planned to cover them. :-)
@emmanuell892 жыл бұрын
you're funny, thanks for the explanation
@ConversationWay10 ай бұрын
is it possible to have 'any' protocol ?
@shubhamjain9433 Жыл бұрын
I am not getting ack packets when I redirect the port. Can anyone help?
@thoongchinglee49053 жыл бұрын
So my question is iptables able to replace port forwarding, reverse proxy, and as a firewall rules if we do it right?
@DamjanDimitrioski3 жыл бұрын
Same question, can we match HTTP path like /api1/ on inbound port 80/443 and redirect to some docker container on port N.
@ShamilSattarov3 жыл бұрын
@@DamjanDimitrioski nope, guys, it's completely different levels of OSI. Iptables works with 2nd to 4th and http is 7th.
@thoongchinglee49053 жыл бұрын
Sorry, I mix up the word reverse proxy. It shouldn't be there
@autohmae3 жыл бұрын
@@DamjanDimitrioski their are some possible ways to do but it gets complicated and error prone to to let iptables look inside the packet and hopefully find the URL and it only works with HTTP not HTTPS. But the Linux kernel has some crazy capabilities if you know how to use it because you can also upload code into the Linux kernel with "eBPF"
@hnasr3 жыл бұрын
As some said there are ways but very complicated and not a replacement for layer 7 proxying. But layer 4 proxying? perhaps
@codewithmubin88663 жыл бұрын
What is the equivalent tool of iptables in Windows?
@ethangender Жыл бұрын
im trying to work on that and so far not reached the solution. i have this 2 networks 10.0.0.6 (public IP) 192.168.30.254 (private) I want to enable there iptables to port map the apache server that is located at 192.168.30.2 , everything I tried not working, connection refused : here is my chain: sudo iptables -t nat -A PREROUTING -d 10.0.0.6 -p tcp --dport 80 -j DNAT --to-destination 192.168.30.2:80 sudo iptables -t nat -A POSTROUTING -j MASQUERADE sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT sudo iptables -A FORWARD -p tcp --dport 80 -j ACCEPT
@ahangk3 жыл бұрын
Can you show us how to redirect port 443 to another port, Thanks.
@gentleling9404 Жыл бұрын
how to route from to IPv6 to ipv4
@alizia21863 жыл бұрын
Brother can you recommend any books regarding Database Or Application Scale Out. I would be really grateful.😘
@aymanpatel58623 жыл бұрын
1. Designing Data Intensive Applications by Martin Klepmann 2. Database Internals