Port forwarding for SSH or remote access?
Hows it going all. Been seeing quite a few people complaining about the switch that happened with port forwarding. I'm attempting to SSH into a raspberry pi from a completely separate network, and every time i port forward the raspi, the port never opens on the router (tested with telnet andhttps://www.yougetsignal.com/tools/open-ports/) I went in (to the app COX support, because you blocked the firmware option that made it simple and easy), and selected the raspi, told it the port i wanted forwarded, and saved it. I can now view it, and look at it, but not use it apparently? Any ideas anyone? I've tried PuTTy and just ssh through cmd/powershell.
SCP/SSH Transfer Speeds Slow
I have tested my Cox residential connection via speed tests and get near the advertised speeds (150MB/s down, 10MB/s up) on the Cox website and via my Ubiquiti router management application. I need to use kerberos enabled scp and ssh to transfer files to a remote server, but the transfer speeds are <500KB/sec in real world tests. Has anyone seen this issue? Is VPN a solution? Thanks B
Secure Shell using PuTTY unstable
When I use PuTTY to log into my home computer (Linux) from a cox.net connection at my mother's house, it disconnects with no warning. I connect to the internet through the built-in WIFI connection of my cable modem. I have found that at the time it disconnects, my PC is also no longer able to ping yahoo.com or google.com. This inability to ping well known URLs indicates that the problem is at the network connection from my mother's house (cox), not the destination address for my ssh connection. Also, when I try to reconnect via ssh it will give a connection error. This error will persist until the ability to successfully ping resumes, which is sometimes immediate, sometimes taking a couple of minutes. I'm using an ARRIS SBG6700-AC cable modem