01-10-2013
It doesn't matter how many open ports you have if your telnet daemon isn't actually using these ports.
Consider that any other daemon on your system could use these ports too. The firewall doesn't decide which program gets an open port. You have to configure the program itself to use other ports.
10 More Discussions You Might Find Interesting
1. Cybersecurity
This may be kind of a stupid question, but here goes:
Say I'm running a FreeBSD webserver (w/apache). I've managed to close ALL open ports (including SSH/telnet and portmapper), excepting '80' that apache is listening on. A netstat -a shows me nothing open.
Discounting DoS/DDoS or holes in... (7 Replies)
Discussion started by: adam_crosby
7 Replies
2. UNIX for Dummies Questions & Answers
Hi all
My freind has Windows 98 and behind a firewall ports used are (LAN)
http:80
ftp :80
Socks :1080
I have telnet server and connected to TCP/IP i.e modem and phone line I want to let my freind Enter my linux box (telnet tunnel) i.e using port 80 and redirect it to telnet port:23... (2 Replies)
Discussion started by: atiato
2 Replies
3. UNIX for Advanced & Expert Users
Hello,
I would like to modify my firewall configuration for being able to handle 2 internet connections in my Red zone.
I would then like to configure some selecting routing rules depending on the internal source.
Actual configuration:
=====================
1 router A (ISP)... (1 Reply)
Discussion started by: el70
1 Replies
4. UNIX for Advanced & Expert Users
Hi,
I am relatively new to UNIX. From the UNIX machine is there anyway of finding out to what and all other machines is the firewall open.
We usually do telnet <machine_name> <port> to fidn out if the firewall is open. Is there anyway i can get an entire list.
Thanks (0 Replies)
Discussion started by: dnatarajan
0 Replies
5. Cybersecurity
Could someone please settle an inter-office argument? Will your network traffic be slower through a firewall on any other port other than port 80. In other words, is port 80 faster than any other port you open on the firewall. I say no. Thanks in advance for the help! (2 Replies)
Discussion started by: cocolsmith
2 Replies
6. Shell Programming and Scripting
Hello All,
Can somebody help me with this script. I have an output file with a list of servers ips and ports. I need to be able to run this script to list all the server ips in the outfile and find out if the port is open or not.
#!/bin/sh
IFS=#;for i in $(cat portTest);
do
# check... (2 Replies)
Discussion started by: liketheshell
2 Replies
7. Shell Programming and Scripting
Dear all
I am writing a shell script to use telnet for the connection test
There are 3 cases to test and detail as:
/* Case 1 - The port can be connected */
# telnet host_a 20101 < /dev/null 2>&1 | grep -q Connected
# echo $? return 0
/* Case 2 - The port cannot be connected */
#... (1 Reply)
Discussion started by: on9west
1 Replies
8. Red Hat
Hi Gurus,
I need to add Multicast Port = xyz
Multicast Address = 123.134.143 ( example) to my firewall rules. Can you please guide me with the lines I need to update my iptables files with. (0 Replies)
Discussion started by: rama krishna
0 Replies
9. AIX
I'm trying to configure a firewall for AIX to accept incoming connections on ports 22 and 443 and deny everything else. All is ok; the server accepts connections only on 22 and 443, but after that I also need to accept all outgoing connections -- ssh and telnet, for example. So I started with
... (0 Replies)
Discussion started by: Michael1457
0 Replies
10. Shell Programming and Scripting
Hi,
I do a telnet to a single server using command :telnet tibserver001 9640
The output i get is :
Trying 10.19....
Connected to tibserver001
However i need to put all the servers in a single file and get the output to see if the server is connected or not.
#! /bin/bash
telnet... (3 Replies)
Discussion started by: samrat dutta
3 Replies
LEARN ABOUT OSF1
port_names
ports(7) Miscellaneous Information Manual ports(7)
NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports
SYNOPSIS
Default Serial Ports:
/dev/tty00
/dev/tty01 (not present on a single-port system)
Parallel Port:
/dev/lp0
DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2
(COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial
printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel
port, for use with a parallel printer.
When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These
devices are located in the /dev directory.
For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a
terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if
one serial port is labeled with an icon for a terminal console) the remaining serial port.
If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also
be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports.
The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral-
lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel
printers, so fewer devices are connected to this port as compared to serial ports.
If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial
devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that
has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and
also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the
device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01).
If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you
use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2
(with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE
Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port
2.
See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the
modem(7) reference page for more information on setting up modems.
SEE ALSO
Commands: lprsetup(8)
Devices: ace(7), modem(7)
System Administration delim off
ports(7)