NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
gsm7224 : at the end of my rope configuring ssh
I apologize for not selecting the correct "location" -- it won't let me select anything close to my model. Perhaps a moderator can put this post in the correct place. I am working with a gsm7442L...
Hi,
Sorry about this. I meant to write back in.
I have concluded that there are two possible problems here:
- Although the switch is supposed to support SSH 2, I suspect either that:
- It does not really support it
- It requires that, even if you have elected not use SSH 1, the presence of an SSH 1 key is required
- Alternatively, the nvram may be corrupted, and unfortunately there is no copy operation by which I could get back the key I downloaded and compare it with the one I have locally.
I looked into testing SSH 1 keys, but modern openssh just does not support it. I was unable to install an older version that would create SSH 1 keys.
I reached the point where the amount of time it was taking me to get this one to work exceeded its cost (it was pretty cheap on ebay -- I should have known there would be a catch), so I am returning it.
I ordered an M4100 to replace it. That one appears to date to circa 2015, so I hope that it will be relatively easier to get it working.
But this is all sketchy stuff and definitely not for the faint of heart. I have a cisco sg250-08 that I bought just a few years ago so it's pretty new. I had all manner of trouble getting ssh to work on it. The difference is that the ssh daemon starting was not dependent on the format of any keys (that is just a very poor design choice).. There were meaningful error messages. And the switch is new enough that I was able to find the solution using my google fu.
Thanks all for your replies. I do consider this a "solution": just don't given in to the sunken cost fallacy 🙂
- Although the switch is supposed to support SSH 2, I suspect either that:
TheTaoOfPhil wrote:
I apologize for not selecting the correct "location" -- it won't let me select anything close to my model. Perhaps a moderator can put this post in the correct place.
No surprise given that this place is a rat's nest.
You might get more help, and find earlier questions and answers specific to your device, in the appropriate section for your hardware. That's probably here:
Discuss Ethernet Switches Plus and Pro Managed
You might like to search there for messages related to your problem.
I will ask the Netgear moderator to move your message.
In the meantime you could visit the support pages:
Support | NETGEAR
Feed in your model number and check the documentation for your hardware. Look at the label on the device for the model number.
Check for various troubleshooting tips.
You may have done this already. I can't tell from your message.
I mention it because Netgear stopped supplying printed manuals and CD versions some years ago and people sometimes miss the downloads.
Thanks for those suggestions and for looking into further resources. I do have the documentation. And I will check the other forums.
I also did find a few additional and random bits of information on the web about how to create the keys. Those did not work either. I was also able to find the firmware and updated it to 6.2.0.14. It seems that this is the latest version.
The problem with the switch recognizing the format of the keys seems to have been solved by the setting the clock on the switch to the correct time zone. Once I got that squared away, sshd still doesn't start, but for a different reason -- it does not complain about the ssh keys being bad.
Now the UI is telling me that ssh is not enabled. But when I enable ssh I am getting these messages:
6> JUN 26 07:33:54 192.168.8.3-1 UNKN[39649952]: sshd_control.c(385) 63 %% SSHD: sshdEventAdminModeSet failed, event=0
<6> JUN 26 07:33:54 192.168.8.3-1 UNKN[39649952]: sshd_control.c(444) 62 %% SSHD: sshdListenTask failed to Startup
<6> JUN 26 07:33:54 192.168.8.3-1 UNKN[39649952]: sshd_control.c(209) 61 %% SSHD: sshdListenTask already runningIt looks as if there might be a process lock file of some kind that's hanging around and needs to be deleted.
The switch also seems to be struggling with dhcp refresh:
<6> JUN 26 07:13:38 169.254.100.100-1 UNKN[54549764]: dhcp_support.c(226) 60 %% dhcp_bind(): networkPort dhcpstate failed
<6> JUN 26 05:13:25 169.254.100.100-1 UNKN[54549764]: dhcp_support.c(226) 59 %% dhcp_bind(): networkPort dhcpstate failed
<6> JUN 26 03:13:12 169.254.100.100-1 UNKN[54549764]: dhcp_support.c(226) 58 %% dhcp_bind(): networkPort dhcpstate failed
<6> JUN 26 01:12:59 169.254.100.100-1 UNKN[54549764]: dhcp_support.c(226) 57 %% dhcp_bind(): networkPort dhcpstate failedAfter I copied in the new firmware and rebooted, it took a long time for dhcp to refresh and for my router's dns to register the ip; (which it had known previous). This must be why.
I am beginning to wonder if this switch has a hardware problem.
Thanks for your help!
--Phil
michaelkenward wrote:No surprise given that this place is a rat's nest.
Indeed 8-)
According the product documentation and downloads page https://www.netgear.com/support/product/gsm7224v1 Netgear does talk of the GSM7224v, a ProSAFE 24 Port Gigabit Managed Switch (dated from 2007).
This Managed Switches community section talking of Managed Switches Series including: M4100, M4200, M4250, M4300, M4500, M5300, M6100, M7100 was opened long before the area was generated.
Let's hope there is some related know-how and experience was left back here.
Hi,
Sorry about this. I meant to write back in.
I have concluded that there are two possible problems here:
- Although the switch is supposed to support SSH 2, I suspect either that:
- It does not really support it
- It requires that, even if you have elected not use SSH 1, the presence of an SSH 1 key is required
- Alternatively, the nvram may be corrupted, and unfortunately there is no copy operation by which I could get back the key I downloaded and compare it with the one I have locally.
I looked into testing SSH 1 keys, but modern openssh just does not support it. I was unable to install an older version that would create SSH 1 keys.
I reached the point where the amount of time it was taking me to get this one to work exceeded its cost (it was pretty cheap on ebay -- I should have known there would be a catch), so I am returning it.
I ordered an M4100 to replace it. That one appears to date to circa 2015, so I hope that it will be relatively easier to get it working.
But this is all sketchy stuff and definitely not for the faint of heart. I have a cisco sg250-08 that I bought just a few years ago so it's pretty new. I had all manner of trouble getting ssh to work on it. The difference is that the ssh daemon starting was not dependent on the format of any keys (that is just a very poor design choice).. There were meaningful error messages. And the switch is new enough that I was able to find the solution using my google fu.
Thanks all for your replies. I do consider this a "solution": just don't given in to the sunken cost fallacy 🙂
- Although the switch is supposed to support SSH 2, I suspect either that:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
