Bash script, find the next closed (not in use) port from some port range.
hi,
i would like to create a bash script that check which port in my Linux server are closed (not in use) from a specific range, port range (3000-3010).
the print output need to be only 1 port, and it will be nice if the output will be saved as a variable or in same file.
my code is:
than to run it i use: ./demo2.sh 127.0.0.1 3000 3010
sco unix 5.0.x, several weeks ago, I add a telnet-like service in inetd.conf, it runs well for 100 network terminals.
But nowdays, the terminals can connect to server successfully after booting machine, but several hours later, can not connect. "netstat -p tcp -a" can NOT find the port in... (1 Reply)
May I know what is the TCP/UCP port range for any default AIX NFS? Based on rpcinfo -p, I got the following output:
program vers proto port service
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 ... (4 Replies)
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Hello
I'm beginner in the linux scripting and i would like to get help. I want to create a script that can block one or more Port even see all the TCP port. The ports must be blocked even when starting my machine.
Of course requires a second script which will allow the ports that you want to... (0 Replies)
Hi Guys,
Please could you tell me if it is possible to have a single rule/filter to allow a certain port range instead of a separate rule for each port?
I'm sure it must be possible but I am unable to find the syntax.
Thanks
Chris (4 Replies)
I want to limit all *outbound* traffic on eth0 (or all *.*) on port 25 to a specific (allowed) range...
I.E.
192.168.1.5 (local ip) tries to connect to 1.2.3.4:25 (outside real world ip)
It can proceed because 1.2.3.0/24 is the allowed range
Now, 192.168.1.5 (local ip) tries to connect to... (1 Reply)
In my Linux system ephemeral port range is showing different ranges as follows
$ cat /proc/sys/net/ipv4/ip_local_port_range
32768 61000
cat /etc/sysctl.conf | grep net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 9000 65500
Which will be the effective ephemeral port... (5 Replies)
I'll start with I'm not an AIX expert, I inherited a lot of AIX servers to maintain.
My problem is on AIX 7.1 TL4 SP4 environments. I'm running named as a DNS forwarder only to internal DNS servers.
These AIX servers have a customized UDP ephemeral port range to avoid conflicting with the... (0 Replies)
Discussion started by: seanc
0 Replies
LEARN ABOUT SUSE
tnm::udp
udp(n) Tnm Tcl Extension udp(n)
__________________________________________________________________________________________________________________________________________________NAME
udp - Send and receive UDP datagrams.
_________________________________________________________________DESCRIPTION
The udp command allows to send and receive datagrams using the User Datagram Protocol (UDP) (RFC 768).
UDP COMMAND
udp open [port]
The udp open command opens a UDP datagram socket and returns an udp handle. The socket is bound to given port number or name. An
unused port number is used if the port argument is missing.
udp connect host port
The udp connect command opens a UDP datagram socket and connects it to a port on a remote host. A connected UDP socket only allows
to send messages to a single destination. This usually allows to shorten the code since there is no need to specify the destination
address for each udp send command on a connected UDP socket. The command returns a udp handle.
udp send handle [host port] message
The udp send command sends a datagram containing message to the destination specified by host and port. The host and port arguments
may not be used if the UDP handle is already connected to a transport endpoint. If the UDP handle is not connected, you must use
these optional arguments to specify the destination of the datagram.
udp receive handle
The udp receive command receives a datagram from the UDP socket associated with handle. This command blocks until a datagram is
ready to be received. In most cases, it might be a good idea to check for pending datagrams using the udp bind command.
udp close handle
The udp close command closes the UDP socket associated with handle.
udp bind handle readable [script]
udp bind handle writable [script]
The udp bind command allows to bind scripts to a UDP handle. A script is evaluated once the UDP handle becomes either readable or
writable, depending on the third argument of the udp bind command. The script currently bound to a UDP handle can be retrieved by
calling the udp bind command without a script argument. Bindings are removed by binding an empty string.
udp info [handle]
The udp info command without the handle argument returns a list of all existing UDP handles. Information about the state of a UDP
handle can be obtained by supplying a valid UDP handle. The result is a list containing the source IP address, the source port, the
destination IP address and the destination port.
SEE ALSO scotty(1), Tnm(n), Tcl(n)
AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl>
Tnm udp(n)