Converting pseudo-tty to IP Address

How can I easily get the IP Address of a given terminal connected via a
pseudo-tty?

In other words, if I issue the 'tty' command, and receive /dev/pts/1, how
can I convert /dev/pts/1 into normal dotted notation?

I don't want to have to build a hosts file, DNS, etc.

Tim Underwood wrote:

>How can I easily get the IP Address of a given terminal connected via a
>pseudo-tty?
>
>In other words, if I issue the 'tty' command, and receive /dev/pts/1, how
>can I convert /dev/pts/1 into normal dotted notation?
>
>I don't want to have to build a hosts file, DNS, etc.
>
>
>
>
I assume you mean DNS name format, ttys do not normally have IP addresses

tty | awk 'BEGIN{FS="/";}{print $4 "." $3 "." $2 ".";}

or

tty| tr "/" "."| cut -c 2-

if you are happy with 0.pts.dev

--
J. D. Addison
email (E-Mail Removed)

"Tim Underwood" <(E-Mail Removed)> wrote in message
news:vtYib.108471$(E-Mail Removed). net...
> How can I easily get the IP Address of a given terminal connected via a
> pseudo-tty?
>
> In other words, if I issue the 'tty' command, and receive /dev/pts/1, how
> can I convert /dev/pts/1 into normal dotted notation?
>
> I don't want to have to build a hosts file, DNS, etc.


pseudo-tty's are used for all sorts of things, not just network logins.

I think you can trust the output of 'w' , 'who'.

These are created from entries in /etc/wtmp, so you trust this record is
accurate.

but of course you might not want to do that.


You have to realise that your network login has two processes.

one telnetd (or rshd, sshd ) and one shell (bash, sh, ash, zsh ,whateversh )

The psuedotty's are how these two processes communicate - the pseudotty has
to be there because the shell and the rest of the system expects a tty, and
the tty has to control the processes (telnetd and sh ) and so it has to be
implemented in the kernel.

So to find the ip address of a connection, scan /proc/XXXX (XXXX being
positive integers) for the process with the backend pseudo-tty open. thats
the telnetd or equiv. Then read its file list to find the file handle for
the network connection. then you can use other proc tables to map this file
handle to a remote ip address. netstat read this data already? but it doesnt
deal with tty's.