Shell server adjustments

[scott]

Has something changed in the shell server ssh config that would invalidate some ssh clients? I can't consistently connect via ssh to sh.sonic,.net anymore. It works from some clients and not others. The only common denominator I've found is that the clients that do not work are using ssh version "OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5" and the clients that work are using other versions of ssh, such as for example "OpenSSH_8.5p1, OpenSSL 1.1.1k 25 Mar 2021" and "OpenSSH_7.9p1, OpenSSL 1.1.1i-freebsd 8 Dec 2020". Here is a verbose output from a connection attempt that fails:

I was unable to log in as well But then I went to members.sonic.net and saw that my credit card had expired and now overdue bill. I updated cc info, paid and was able to ssh and content to mail.sonic.net via browser. Now that I can log in, I find that my shell setting has been lost and chsh says permission denied.

Hi,

What shell would you prefer?

-Scott

[jwermont]

Hi, over the past several days, my connection to the shell has been very unstable. It disconnects me every few minutes, and sometimes I can't get back on right away. As far as I can tell, there's nothing wrong with my internet connection - I can connect to sites via my browser with no problem, and I don't get disconnected.

I don't think it has to do with which shell I'm running. When I can stay logged in for a sufficient length of time, everything works as normal.

I use my shell account a lot, so this is putting a dent in my regular activities. Does anyone know what's going on? Thanks!

[scott]

Hi, over the past several days, my connection to the shell has been very unstable. It disconnects me every few minutes, and sometimes I can't get back on right away. As far as I can tell, there's nothing wrong with my internet connection - I can connect to sites via my browser with no problem, and I don't get disconnected.

I don't think it has to do with which shell I'm running. When I can stay logged in for a sufficient length of time, everything works as normal.

I use my shell account a lot, so this is putting a dent in my regular activities. Does anyone know what's going on? Thanks!

Are you leaving it at a shell prompt? You might want to put "unset TMOUT" in your profile or bashrc.

Or if there's enough clamor, I can turn off the setting of TMOUT, but I think it's not a bad idea to have some kind of TMOUT set. (What's a good value? 3 hours? 12 hours? Or...?)

-Scott

[scott]

Hi, over the past several days, my connection to the shell has been very unstable. It disconnects me every few minutes, and sometimes I can't get back on right away. As far as I can tell, there's nothing wrong with my internet connection - I can connect to sites via my browser with no problem, and I don't get disconnected.

I don't think it has to do with which shell I'm running. When I can stay logged in for a sufficient length of time, everything works as normal.

I use my shell account a lot, so this is putting a dent in my regular activities. Does anyone know what's going on? Thanks!

Are you leaving it at a shell prompt? You might want to put "unset TMOUT" in your profile or bashrc.

Or if there's enough clamor, I can turn off the setting of TMOUT, but I think it's not a bad idea to have some kind of TMOUT set. (What's a good value? 3 hours? 12 hours? Or...?)

-Scott

NM, I'm dumb. I turned off TMOUT completely until we are sure about the network the shell server is sitting on. That had to wait until next week, I'm trying to get myself decompressed a bit, I'd rather not crack under techno-stress.

-Scott

[scott]

Folks should be able to log in now. Can you?

Thanks for any reports you can provide.

-Scott

[scott]

Folks should be able to log in now. Can you?

Thanks for any reports you can provide.

-Scott

A yes or no from anybody would be nice. Though it is still early in the morning, I'm only seeing logins from certain networks, no ipbb/lightspeed yet.

[scott]

Folks should be able to log in now. Can you?

Thanks for any reports you can provide.

-Scott

A yes or no from anybody would be nice. Though it is still early in the morning, I'm only seeing logins from certain networks, no ipbb/lightspeed yet.

Okay, if anybody can't get in, don't forget to email shellmaster@sonic.net to open a ticket.

As an interim (or perhaps, permanent) measure to try to see more people logging in, I moved the shell server over to the new network address. I can (CAN) log in from the east coast, so trying to confirm we don't have some internal network issue going on, or if it's just Saturday morning.

-Scott

[ds_sonic_asif]

ssh works fine this morning for me over a Sonic Fusion Fiber connection in Berkeley.

[swerthei]

I am able to log on today, from some clients. But from certain clients I am still getting the same error I posted about earlier:

C:\Users\swerthei>ssh swerthei@sh.sonic.net
Corrupted MAC on input.
ssh_dispatch_run_fatal: Connection to 208.201.242.22 port 22: message authentication code incorrect

This happens on two different Windows computers.

[jwermont]

Hi Scott,

I just logged into the shell, it seems fine so far. Thanks for looking into it!

Joyce