NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
wolfsden3
Nov 04, 2016Aspirant
ReadyNAS 102 - No alternative port on host field WTF Netgear Derps?
WTF netgear dev derps? I can't put an alternative port in the host field for my ssh host target. For example, if I go to backup > add backup > host: I put in: derps.netgearderps.net:10003 ...it has t...
StephenB
Nov 14, 2016Guru - Experienced User
wolfsden3 wrote:
That link was stupid because Brian the moderator pretty much says post another request or call supposed complain.
It's not stupid. Netgear development looks the ideas in idea exchange, and they do implement them. Getting more votes for a posted idea is (IMO) more effective than creating a lot of duplicates in the exchange. You can of course call and complain too.
FWIW, I have mod privileges here also - my rank doesn't say that, simply because it caused some folks to assume I work for Netgear (which I don't). In any event BrianL was talking to someone else (several months ago), and the post he was talking about was already moved off the thread.
mdgm-ntgr
Nov 14, 2016NETGEAR Employee Retired
We value each and every suggestion, but we do need to prioritise where we allocate our resources.
The numbers of votes for different features in the Idea Exchange helps to give us an indication as to how popular a suggestion is.
I can understand that you're frustrated with a lack of progress on this request but please note this is a public community. It's possible that children may read what's on this site, so please tone down the language.
Actually it's product management that ultimately decides what gets implemented. The dev team can and do make their recommendations.
- hausNov 17, 2016Aspirant
OP, the solution for the time being is to leave sshd listening on 22, but block the port in your firewall. Then open up that port to traffic from your ReadyNAS' public-facing IP address only, so it can connect to your sshd daemon. The port will appear closed to everyone else.
Quick edit: sshd can listen on multiple ports, this is how I do it, so your regular ssh sessions can still happen over your alternate port.
- wolfsden3Nov 17, 2016AspirantOK, so this is the EXACT mother f'ing problem. This guy says to keep it "listening" on port 22. Derp...can't you read my original post? It's not a LISTENING issue it's a destination problem. Stupid programmers seriously. In the filed you have a host (an IP or a hostname blahblahblah.com) then a port field...that's where it's going to. SSH by default as you clearly know listens on port 22 BUT you can change that and I do to fend off the hacker losers. Now...if you read my post you'd know that the problem with derpy Netgear programmers is they GIVE YOU THE OPTION TO TYPE INTO THE PORT FIELD BUT ONLY LET YOU USE PORT 22. That makes NO SENSE! Why can I overwrite the default value IF THEY DON'T LET YOU! Scenario: netgear crap box that's almost useless now >>>>> backup via ssh & rsync >>>>>> ALTERNATE PORT for SSH on the DESTINATION SIDE say 50000 (goes to the sshd on the destination server) >>>>>> done. So for every other customer I have I can use that alternate port 50000 except the one with the crap netgear box that although they let you overwrite the port field, they won't accept anything but 22 in the field. So mother f ing stupid. Allocating resources has nothing to do with it. It's clearly a VALID destination and host and all netgear needs to do is take out the piece of code that does the host name checking and blocks you from using port 22. How hard is that? It should have NEVER been put in! Who's the dev ops manager that thought that was a good idea? They should be strung up. To set the record straight I don't expect anything to come out of my comments other than making a point as to how stupid netgear is, these forums and how utterly pointless it is to make requests since they never get listened to. Sure, I can go in my destination firewall, allow port 22 from only the client site and port redirect it to port 50000 but WHY should I do that when the stupid STANDARD is allowing ANY port as the destination not just 22 and netgear dev had to go and F up a default that didn't need to be restricted. Can anyone see my point? Seriously! Yea...that other post was "moved" off the thread...again, proves my point. It's pointless to post crap like this. It just helps me to vent. MERICA! :P F U Netgear!
- hausNov 17, 2016Aspirant
Deleted because through your ranting I can't even figure out what you're asking anymore. I tried to help.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!