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
ieee1284_open
IEEE1284_OPEN(3) Functions IEEE1284_OPEN(3)NAME
ieee1284_open - open a port
SYNOPSIS
#include <ieee1284.h>
int ieee1284_open(struct parport *port, int flags, int *capabilities);
DESCRIPTION
In order to begin using a port it must be opened. Any initial set-up of the port is done at this stage. When an open port is no longer
needed it should be closed with ieee1284_close(3).
The possible flags are:
F1284_EXCL
This device cannot share the port with any other device. If this is the case it must be declared at this stage, so that other drivers
trying to access the port know not to bother; otherwise they will wait until this driver releases the port, i.e. never.
The iopl/dev-port access methods don't support this yet, but the ppdev ones do.
If capabilities is not NULL it must point to storage for an int, which will be treated as a set of flags, one per bit, which the library
sets or clears as appropriate. If a capability is present it will be used when asked for. They are:
CAP1284_RAW
Pin-level access is available. If this capability is present then the following functions are effective: ieee1284_write_data,
ieee1284_read_status, ieee1284_wait_status, ieee1284_write_control, ieee1284_read_control, ieee1284_frob_control.
CAP1284_NIBBLE
There is an implementation of nibble mode for this port.
CAP1284_BYTE
There is an implementation of byte mode for this port.
CAP1284_COMPAT
There is an implementation of compatibility mode for this port.
CAP1284_ECP
There is a hardware implementation of ECP mode for this port.
CAP1284_ECPRLE
There is an RLE-aware implementation of ECP mode for this port (the F1284_RLE flag is recognised by the ECP transfer functions).
CAP1284_ECPSWE
There is a software implementation of ECP mode for this port.
CAP1284_BECP
There is an implementation of bounded ECP mode for this port.
CAP1284_EPP
There is a hardware implementation of EPP mode for this port.
CAP1284_EPPSWE
There is a software implementation of EPP mode for this port.
CAP1284_IRQ
An interrupt line is configured for this port and interrupt notifications can be received using ieee1284_get_irq_fd(3).
CAP1284_DMA
A DMA channel is configured for this port.
RETURN VALUE
E1284_OK
The port is now opened.
E1284_INIT
There was a problem during port initialization. This could be because another driver has opened the port exclusively, or some other
reason.
E1284_NOMEM
There is not enough memory.
E1284_NOTAVAIL
One or more of the supplied flags is not supported by this type of port.
E1284_INVALIDPORT
The port parameter is invalid (for instance, the port may already be open).
E1284_SYS
There was a problem at the operating system level. The global variable errno has been set appropriately.
SEE ALSO ieee1284_close(3)AUTHOR
Tim Waugh <twaugh@redhat.com>
Author.
COPYRIGHT
Copyright (C) 2001-2003 Tim Waugh
09/18/2007 IEEE1284_OPEN(3)