Post History
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 Ba...
#4: Post edited
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?
- 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?
#3: Post edited
- 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 port actions at all) or are such actions generally reserved to programs which come *above* the shell layer?
- 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?
#2: Post edited
I find port forwarding and port triggering as advanced sub-topics of the topic of network protocols (those 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 these actions (or port actions at all) or are such actions generally reserved to programs which come *above* the shell layer?
- 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 port actions at all) or are such actions generally reserved to programs which come *above* the shell layer?
#1: Initial revision
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 (those 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 these actions (or port actions at all) or are such actions generally reserved to programs which come *above* the shell layer?