Comments on Do shells have anything to do with port forwarding or port triggering?
Parent
Do shells have anything to do with port forwarding or port triggering?
I find port forwarding and port triggering as advanced sub-topics of the topic of network protocols which include the "port" concept such as TCP and UDP.
I am wondering if shells in general and Bash in particular has anything to do with port forwarding or port triggering? That's to ask, do shells typically suffice any tools to do such actions or are such actions generally reserved to programs which come above the shell layer?
Post
Port forwarding is something a router does.
Port triggering is basically port forwarding that's enabled when a connection attempt is detected and then automatically disabled. That's also handled on a router.
A shell is simply a program that takes interactive or batch command input and is used to start other programs, or run small scripts that usually end up invoking other programs to do something.
So shells are really not related to port forwarding or port triggering. You can tell your shell to start a program to generate traffic on a specific IP and port, which may enable some port triggering, but that's about it.
0 comment threads