We're still here! We've just sent your keyfile - sorry for the delay in processing.
Pleased try Profile, options, advanced, force size. Unfortunately hosts using Telnet may not negotiate window size. Let us know if this option works. If the host supports ssh then connect using ssh.
Ok. Are you sure that the switch, with the current version of firmware, supports NAWS?
I noticed that on a model HP 2920 switch it was a later update, as follows:
TELNET Negotiate About Window Size (NAWS) Initiation
When a telnet connection is established with a switch, the switch always uses the default values of 80 columns by 24 lines for
the window dimensions. The window can be resized by either dragging the corner of the window, or by executing the terminal
length <x> width <y> CLI command and then configuring the telnet client with those dimensions. The new window dimensions
are lost after that telnet session ends.
When the telnet connection is established with an HP switch, either the switch or the telnet client needs to initiate the inquiry
about the availability of NAWS. If NAWS is available, you can resize the window by dragging the corner of the window to the
desired size. The telnet software uses NAWS to tell the switch what the new window dimensions are. If the switch supports
the requested window dimensions, it uses them for all future interactions. If the switch does not support those window
dimensions, it refuses them and the telnet client requests an alternate set of window dimensions. The negotiation continues
until the telnet client and the switch agree on the window dimensions.
Making Window Size Negotiation Available for a Telnet Session
The switch currently responds to a request from the remote telnet client to negotiate window size. However, some telnet
clients do not request to negotiate window size unless the switch’s telnet server suggests that NAWS is available.
This update allows window size negotiation to occur with telnet clients that support NAWS but do not try to use it unless it
is suggested by the switch’s telnet server. The switch’s telnet server will suggest to the telnet client that NAWS is available.
What happens when you use Penguinet and attempt to login to the server which uses 2FA?
We’ll introduce an option to do this in v2.6
Incidentally, your issue might also be solved by just copying the file "profiles.pnt" from the old machine to the new one.
The user interface is under review for a future version. Please keep all suggestions coming!
Diego, you can already get rid of the status bar if you don't use it. In Profiles/Appearance/Status Bar, remove all the text. If nothing is configured to appear in the status bar, the bar itself won't appear.
We will include this for xterm terminal types in v2.60.
gt-fail, no, we mean selecting "xterm" under "Terminal type" on the "Login" tab in Connection profiles. This restriction is needed because only that terminal type has the features we need in order to tell whether you're in vim (or a similar remote app) or not. When not in an app such as vim, we presume you'd like the scroll wheel to still scroll through your scrollback. When in vim (or similar), we'll translate the scroll wheel movement into cursor up/down, which is what gnome-terminal is doing.
We are thinking about ways to initiate sessions but leave the Connection Profiles window open. This should help with opening many sessions without overdoing the mouse clicks.
Glad to hear you're finding it useful. It's always great to hear from happy users.
If I understand your request correctly, you can already do this. From the profile view, select the 'parent' of the profiles you want to open. Click over to the 'Options' tab, and select 'Connect to all children' under 'On connection'. This will then allow you to double click on the parent profile (Or highlight it and hit connect) and have it open all the child profiles at once.
Let us know if this works for you!
PenguiNet does not currently have the facility to specify a codepage against a profile. Is there anyone out there that would like this?