03-20-2002
What do you mean by "telnet access to port 80"? Incoming? Or outgoing? As far as I am aware, there is no reliable means of knowing which application is producing an incoming request, nor is there any reliable way of blocking outgoing requests based on the application. One of the reasons is that there is no set source port - it just picks one above 1024 that isn't in use, and makes the connection.
Someone let me know if I'm wrong...
10 More Discussions You Might Find Interesting
1. Solaris
we disabled telnet on solaris 9 via previous a thread. We use CMS (call management system) supervisor which used port 23 (telnet). We cannot use telnet via local directive and it was shut down as stated when we shut down telnet in the inetd file. I cannot now log into the CMS box since port 23 is... (3 Replies)
Discussion started by: panzerkw
3 Replies
2. UNIX for Advanced & Expert Users
Hi all,
I have a problem. I have machine names and their IP addresses in /etc/hosts file. My application does telnet on that machine host name. The application does not uses IP address for tenet. It will fetch the host name from /etc/hosts file.
Now the telnet server runs on customized port.... (6 Replies)
Discussion started by: zing_foru
6 Replies
3. Shell Programming and Scripting
Hi,
I would like to create a simple script that will telnet a number of IP and Ports one after the other to confirm connectivity to those addresses.
I don't need to log on, just output to a file what the response is, i.e Escape Character, connectivity refused etc.
Complete newbie to... (6 Replies)
Discussion started by: asou
6 Replies
4. AIX
can some one help me ?
what happens when we telnet to a port ?
example
telnet 192.168.0.xx 1234
where 1234 is a port number
Thank you (5 Replies)
Discussion started by: anwesh
5 Replies
5. Windows & DOS: Issues & Discussions
Hello all.
I have an old computer with M$-DOS 7. I want to use it like a dumb terminal, with telnet. I need to connect it to my desktop These are my questions:
How can i configure the serial port on dos?
How can i telnet form dos to the serial port?
How can i set up a telnet server on the... (12 Replies)
Discussion started by: mghis
12 Replies
6. Cybersecurity
Hi, we have recently setup a new UNIX server with solaris 10 and I am having issue with with SMTP/sendmail.
telnet localhost 25 --- works
telnet hostname.domain.com 25 -- does not work.
# telnet hostname.domain.com 25
Trying 10.122.1.111...
telnet: Unable to connect to remote host:... (1 Reply)
Discussion started by: esmgr
1 Replies
7. Red Hat
My linux version is 2.6.18-194.e14 (Oracle enterprise linux).
Could you please tell me how to enable telnet on the server.
When I try to connect the server through another pc using telnet it is throwing error.
Connecting To <ip address>...Could not open connection to the host, on port 23.... (3 Replies)
Discussion started by: oradba_arun
3 Replies
8. IP Networking
Hi,
I am trying to set up a dev environment and I have Ubuntu server (10.16.1.92) and a CentOS VM (10.16.3.235) on this. On the CentOS I have a program running on port 5433. Now my problem is that I am unable to telnet this port from another Windows server whereas I can telnet port 22 from... (5 Replies)
Discussion started by: rishav
5 Replies
9. UNIX for Dummies Questions & Answers
Hi,
Well this is probably a silly one that I should know...but I don't !
I'm telnetting to various ports from a shell script and the telnet is echoing back that it's 'trying xxx.xx.xx.xx...' but not the port number it's trying!
Any help much appreciated
Thanks (1 Reply)
Discussion started by: Grueben
1 Replies
10. Solaris
Hi,
I need to block ssh port 22 from all the servers except one server ip.
Until solaris11.3 and below, I used to do like below(under /etc/ipf/ipf.conf),and it's working fine
pass in quick from $server_ip to any port=22
block in quick from any to any port=22
But I tried almost same in... (1 Reply)
Discussion started by: Sumanthsv
1 Replies
LEARN ABOUT DEBIAN
net::sip::leg
Net::SIP::Leg(3pm) User Contributed Perl Documentation Net::SIP::Leg(3pm)
NAME
Net::SIP::Leg - Wrapper around Socket for sending and receiving SIP packets
SYNOPSIS
my $leg = Net::SIP::Leg->new( addr => '192.168.0.2' );
$leg->deliver( $packet, '192.168.0.5:5060' );
DESCRIPTION
A Leg wraps the socket which is used to send and receive packets. It provides ways to strip Via header from incoming packets, to add Via
header to outgoing packets and to add Record-Route header while forwarding.
It's usually not used directly, but from Net::SIP::Dispatcher.
CONSTRUCTOR
new ( %ARGS )
The constructor creates a new object based on the hash %ARGS. The following keys are used from %ARGS:
sock The socket as IO::Socket::INET object. "addr", "port" and "proto" will be determined from this object and not from %ARGS.
addr The local address of the socket. If this is given but no port it will extract port from addr, if it's in the format
"host:port".
port The port of the socket. Defaults to 5060.
proto The connection protocol, e.g. 'tcp' or 'udp'. Defaults to 'udp'.
contact Optional contact information which will be added as Record-route header to outgoing requests and used within Contact header for
200 Responses to INVITE. If not given it will be created based on "addr", "port" and "proto".
If no socket is given with "sock" it will be created based on "addr", "port" and "proto". If this fails the constructur will "die()".
The constructor will creeate a uniq branch tag for this leg.
METHODS
forward_incoming ( PACKET )
Modifies the Net::SIP::Packet PACKET in-place for forwarding, e.g strips top Via header in responses, adds received parameter to top
Via header in requests, handles the difference between forwarding of requests to strict or loose routes and inserts Record-Route header
in requests.
forward_outgoing ( PACKET, LEG_IN )
Similar to forward_incoming, but will be called on the outgoing leg. LEG_IN is the Net::SIP::Leg, where the packet came in (and where
forward_incoming was called). Will add Record-Route header and remove itself from Route.
deliver ( PACKET, ADDR, [ CALLBACK ] )
Delivers Net::SIP::Packet PACKET through the leg $self to ADDR, which is "ip:port". Usually this method will be call from within
Net::SIP::Dispatcher.
If the packet was received by the other end (which is only possible to say if a reliable protocol, e.g. 'tcp' was used) it will call
CALLBACK if provided. See invoke_callback in Net::SIP::Util for the format of callbacks. If the packet could not be delivered CALLBACK
will be invoked with the appropriate errno ($!).
While delivering requests it adds a Via header.
receive
Reads a packet from the socket and returns the Net::SIP::Packet PACKET and the senders ADDR as "ip:port". If reading failed will return
"()".
check_via ( PACKET )
Returns TRUE if the top Via header in the Net::SIP::Packet PACKET contains the branch-tag from $self, otherwise FALSE. Used to check if
the response came in through the same leg the response was send.
add_via ( PACKET )
Adds itself to PACKET as Via header.
can_deliver_to ( ADDR|%SPEC )
Returns TRUE if the leg can deliver address specified by ADDR or %SPEC. ADDR is a hostname which can be prefixed by the protocol (
e.g. "udp:host" ) and postfixed by the port ( "host:port", "tcp:host:port",... ).
If the caller has 'proto','addr' and 'port' already as separate items it can call the method with %SPEC instead.
Right now it has now way to check if the leg can deliver to a specific host because it has no access to the routing information of the
underlying OS, so that only proto will be checked.
fd Returns socket of leg. In some special environments (like tests) there might be legs, which don't have a socket associated. In this
case you need to call receive from Net::SIP::Dispatcher yourself, because it cannot be called automatically once it receives data on
the socket.
dump
Returns string containing information about the leg. Used for debugging.
perl v5.14.2 2012-06-26 Net::SIP::Leg(3pm)