Fresh Tomato 2018.5, SSH and file sharing not working over 5G Wifi

Discussion in 'Tomato Firmware' started by jerry0000, Mar 10, 2019.

  1. jerry0000

    jerry0000 Connected Client Member

    I am using 2018.5. I cannot SSH into the router via LAN IP if I am on 5G wifi. Works just fine on 2.4G wifi. And it looks like file sharing has the same issue.
    Internet works for both on 5G and 2.4G, and I can ping the router LAN IP using both 5G and 2.4G wifi. Any idea?

    Settings attached.

    Basic->Network: 2.4G and 5G same WPA/AES phrase.
    Intention is to have 2.4G and 5G SSID the same, however I could not do this as I am having the 5G wifi issue mentioned above. So right now, the 5G wifi SSID was appended -5G in the end.

    Advanced->VLan: I did not change anything there. It is default setting.

    Administration->Admin access: Changed default SSH port #, and restricted to key login only.

    Any help is appreciated. For now, I am falling back to use the 2.4G if I need to SSH in router or use file sharing, which is a pain.

    One other issue may or may not related: 5G wifi setting 80 MHz channel width seem to have some issue. Setting 80, and overview shows 40. Setting 40, and overview shows 40 as well. Tried different countries, same results.
     

    Attached Files:

  2. Mr9v9

    Mr9v9 Serious Server Member

    What happens when you try logging in using credentials instead of your preshared key, and set it to default port?
     
  3. jerry0000

    jerry0000 Connected Client Member

    Password login does not work either, wither on default port 22 or not. The SSH session never even prompt me for the credential when connected over 5G wifi. The behavior is the same for password and preshared key. The SSH session just times out.

    BTW, this is a Netgear R7000 runign 2018.5 Fresh Tomato. I think that is on the screenshots, however just want to make it clear.
     
    Last edited: Mar 10, 2019
  4. Mr9v9

    Mr9v9 Serious Server Member

    Confirmed on mine as well (2019.1.015 -beta). As a workaround you can use telnet and that will work for now.
    @kille72 @pedro311 Do you guys know about this behaviour? Has it been reported in the past?
    Anyone on an older build of Shibby or other forks want to test?
     
  5. jerry0000

    jerry0000 Connected Client Member

    Thanks for testing. I have not tried telnet. However, file sharing will NOT work over 5G wifi either. So the telnet workaround is even more limited.

    I initially flashed Shibby 1.32, however the USB indicator lights do not work, so I abandoned and flashed Fresh Tomato 2018.5 without further testing Shibby 1.32. However, I am interested to know if Shibby 1.32 behaves the same or not.
     
  6. Mr9v9

    Mr9v9 Serious Server Member

    My guess is that Dropbear is is not listening on wl1. I created a ticket for you over at the bitbucket page.
     
  7. pedro311

    pedro311 Networkin' Nut Member

    Just checked on my AC3200 with WL1 5G: no problem with SSH, samba, ftp, minidlna:


    Screenshot_20190310-223010.png Screenshot_20190310-223556.png Screenshot_20190310-224050.png
     
    M_ars and kille72 like this.
  8. digixmax

    digixmax LI Guru Member

    FWIW, I am able to SSH to my R7000 home gateway router running 2019.1-beta from my PC behind a RT-AC68P Media Bridge which is connected to the R7000 over 5Ghz WiFi. The R7000 SSH setup is the default.
     
  9. Mr9v9

    Mr9v9 Serious Server Member

    That is interesting, what are you doing that is different from the defaults? Did you modify iptables? Any custom scripts? Does scp work for file transfers as well?
     
  10. digixmax

    digixmax LI Guru Member

    I use the SSH default setup. SSH using PuTTY and SCP using WinSCP both work.
     

    Attached Files:

  11. jerry0000

    jerry0000 Connected Client Member

    Which version of Fresh Tomato you are running?
     
  12. jerry0000

    jerry0000 Connected Client Member

    I am not sure if the media bridge made the difference?
     
  13. pedro311

    pedro311 Networkin' Nut Member

  14. jerry0000

    jerry0000 Connected Client Member

    pharma likes this.
  15. jerry0000

    jerry0000 Connected Client Member

    Can you test if connecting to R7000 on 5G wifi directly?
     
  16. kille72

    kille72 LI Guru Member

    Just checked on my AC56U: no problem with SSH and Samba on 2018.5 and 2019.1 with 5 GHz radio.
     
    M_ars likes this.
  17. Sean B.

    Sean B. Network Guru Member

    Try disabling remote access/remote forwarding

    If that doesn't have any effect, please run this command in a shell on the router or via System Commands in the GUI:

    Code:
    netstat -an
    And post the output. Feel free to redact instances of your WAN IP, but please leave the last octet so all lines can be distinguished.

    What type of client are you using on 5ghz when trying to access via ssh? Windows/Linux computer? Android/Iphone?
     
  18. Sean B.

    Sean B. Network Guru Member

    Dropbear does not bind to the wireless interfaces themselves, it listens on 0.0.0.0:22, which relates to the IP address(es) assigned to the LAN bridge(s).
     
    Last edited: Mar 11, 2019
  19. jerry0000

    jerry0000 Connected Client Member

    Will test disabling remote forward this weekend, as I am traveling and this can only be tested while I am home.

    Can post netstat -an tonight with VPN in.

    Client is putty on my win10 laptop. I do not think it has anything to do with the client, as the same client works fin with 2.4G wifi.
     
  20. jerry0000

    jerry0000 Connected Client Member

    So it might have something to do with the exact version of Netgear R7000 I and Mr9v9 have???
     
  21. Sean B.

    Sean B. Network Guru Member

    @Mr9v9 , do you have remote access and/or remote forwarding enabled for SSH?
     
  22. digixmax

    digixmax LI Guru Member

    I tried SSH from a laptop directly to my R7000 over 5G and it also worked just fine.
     
  23. Mr9v9

    Mr9v9 Serious Server Member

    Yes, testing all local default settings, trying with a Linux terminal.

    [​IMG]


    [​IMG]
    [​IMG]
     
    Last edited: Mar 12, 2019
  24. Mr9v9

    Mr9v9 Serious Server Member

    I found a fix but it makes almost no sense. Changing the wireless settings to A Only and setting the channel manually helps it connect now.

    [​IMG]

    I started the daemon manually and it finally connected. Enabled on startup now works after rebooting and I can connect without any issues.

    Just so we are all on the same page here, I always do an NVRAM Erase and put my settings in manually after upgrades etc. I am not sure why it does not want to work out of the box for me, but maybe this can help @jerry0000 for some functionality in the meantime. Thoughts?
     
    Last edited: Mar 12, 2019
  25. Sean B.

    Sean B. Network Guru Member

    I don't follow. You did have a check in the box for the remote access and/or remote forwarding options under Administration->Admin access and now they are unchecked for testing? Or they were never checked/enabled at all? Because you said yes ( checked/enabled ), but your screen shots show no ( unchecked/disabled ).
     
  26. Mr9v9

    Mr9v9 Serious Server Member

    Sorry I was in a hurry and misread your post let me clarify, I meant to put no and no they were never checked or enabled at all.
     
    Sean B. likes this.
  27. Sean B.

    Sean B. Network Guru Member

    Are you able to reproduce the issue at all now? Or is it just working every reboot/time you try to connect?
     
  28. Mr9v9

    Mr9v9 Serious Server Member

    While leaving the ssh daemon settings above alone, If I change my 5 Ghz settings back to default it stops connecting, 2.4 Ghz is not affected, and neither is LAN. I then change it back to those strange 5 Ghz A Only settings posted above, it starts working again.

    I will test tomorrow with other settings because I don't have too many 'a' devices aside from my Laptop.
     
    Last edited: Mar 12, 2019
  29. jerry0000

    jerry0000 Connected Client Member

    Thanks for all the details/info. I cannot test until this weekend, as I am out of town, and this has to be tested at home. I will test and report back.

    However, even if I reproduce Mr9v9's results, this is not much of an workaround, as just like him, I do not have too many A devices.

    Additionally, does the change also fix the file sharing issue?

    Any way, I will test and report back this weekend.
     
  30. Mr9v9

    Mr9v9 Serious Server Member

    Setting the band to 'N Only' breaks it for me. Setting the channel to any value, or channel width does nothing on my Linux laptop.

    Setting 5 Ghz to the 'defaults' now if I test using Win10 on another laptop, using puTTY I can connect just fine.
    ssh can't work because of a specific wireless card now? I guess that makes sense, but at the same time it does not:

    Linux Laptop= Intel Wireless AC 7265

    Win10 Laptop= Intel Wireless AC 7260

    Aside from weight, there is nothing different about these cards, they both operate the same, and they don't even have MU-MIMO. So my guess now is it comes down to the client kernel/driver level? If @jerry0000 is running Windows and it still does not work then I am going to be very confused.
     
  31. Sean B.

    Sean B. Network Guru Member

    It may be a failure on the GUI back end to implement the settings correctly, rather than the settings themselves causing an issue. Cutting the middle man out of the equation and configuring, or at least verifying, the settings directly with the driver via CLI would seem a worthwhile check.
     
  32. jerry0000

    jerry0000 Connected Client Member

    I am on Win 10, HP Spectre, Intel Wireless AC 7265
     
  33. jerry0000

    jerry0000 Connected Client Member

    I setup my new ASUS RT-AC3200, and SSH and file sharing works over 5G. So it might be something with the Netgear R7000?
     
  34. jerry0000

    jerry0000 Connected Client Member

    I got an ASUS RT-AC3200, and SSH and file sharing works over 5G wifi. So it looks like there is something funky with the Netgear R7000?

    I have another question. What is the difference between the two 5G wifi? My laptop and Galaxy S7 only sees the 5G-1. Cannot see 5G-2.
     
  35. Sean B.

    Sean B. Network Guru Member

    "Tri-Band" is mostly marketing. All it is is 2 5ghz radios, #1 is using the lower channels 36-48 and #2 is using the upper channels 149-161 and 165. Combined with some driver coding voodoo that "steers" clients to one 5ghz radio or the other depending on the clients speed capability. It's basically trying to separate not-so-fast 5ghz clients onto one radio that's using the lower channels, and fast 5ghz clients onto another radio that's using the upper channels. They feel making a "3rd band" in that fashion is enough justification to tac on another 1300Mbps to their "throughput" rating to make it 600 + 1300 + 1300. Yeah, gotta love the bs.
     
  36. jerry0000

    jerry0000 Connected Client Member

    Got it. Totally agree that is marketing BS.

    Back to the SSh issue over 5G - so it looks like there is something funky with the Netgear R7000. As it worked over the ASUS 5G wifi.
     
  37. pedro311

    pedro311 Networkin' Nut Member

    I just received a response from the user of this router, and he has no problems with ssh connection over 5GHz WL.
     
    kille72 likes this.
  38. jerry0000

    jerry0000 Connected Client Member

    This is really getting weird now. I have this issue, and Mr9v9 has it as well.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice