Has anyone encountered the following behavior?
When ports are configured as autoconnect to telnet into a unix host, running the ‘who’ command displays either of the following 3 results under the ‘Connected to’ column:
- the correct destination IP address
- nothing at all
- garbage characters
The first case occurs the least. Also the number under the sessions column is sometimes unrealisticly high (ie: 1134617) although not always the same number.
As well, if I run the kill command ‘ie kill tty=4’ while a port is listed by ‘who’ causes the TS4 to reboot.
firmware: 82000716_J
ports setup as follows:
set port ra=1-4 dport=23 dest= auto=on
set flow ra=1-4 altpin=on
set port ra=1 termtype=~001
set port ra=2 termtype=~002
set port ra=3 termtype=~003
set port ra=4 termtype=~004
I’ve been using this setup for a couple of years now on both the TS4 and TS16.
The reason for the wierd termtype is that I’m using the passed termtype that sets $TERM to uniquely identify the source TS port. I then detect the actual terminal type later. This behavior exists regardless of whether I have the termtype set or left at default.
BTW, before anyone suggests that I use Realport, I gave it up a couple of years ago because the dgrp module needed unloading whenever a single port got bunged up and restarting realport to the portserver wouldn’t clear up the problem. Before I could unload the dgrp module I had to kick users off of other TS that were having no problems. They weren’t happy.