Hi,
Quick and to the point:
My question is, does anyone know what protocol starts '\026\003\001'? I'm guessing these are some chars, but I'm not sure what encoding.
Background if you're interested:
I've just setup my freenas for remote ssh access - mainly for sftp.
I'm behind NAT and using port forwarding on 443.
I've done this by moving the HTTPS webGUI from 443 and SSH to it (partly to be off the standard SSH port and partly to get through a work firewall).
Anyway, it's all working, and I was expecting the security logs to show some attempts to gain access, which they did. However I have one repeated log I don't quite understand:
Mar 12 22:59:36 freenas sshd[35978]: Bad protocol version identification '\026\003\001' from 192.168.0.4
I got a series of these at 22:23 and 22:59 last night. What's weird is they're from an internal IP address.
I just connected back in remotely and that IP is down - so could have been my android phone or possibly the laptop (though I'm sure this was off by at least 22:59).
Obviously my first port of call was google and then to search this forum. But there were no helpful results I could see.
Thanks.
Quick and to the point:
My question is, does anyone know what protocol starts '\026\003\001'? I'm guessing these are some chars, but I'm not sure what encoding.
Background if you're interested:
I've just setup my freenas for remote ssh access - mainly for sftp.
I'm behind NAT and using port forwarding on 443.
I've done this by moving the HTTPS webGUI from 443 and SSH to it (partly to be off the standard SSH port and partly to get through a work firewall).
Anyway, it's all working, and I was expecting the security logs to show some attempts to gain access, which they did. However I have one repeated log I don't quite understand:
Mar 12 22:59:36 freenas sshd[35978]: Bad protocol version identification '\026\003\001' from 192.168.0.4
I got a series of these at 22:23 and 22:59 last night. What's weird is they're from an internal IP address.
I just connected back in remotely and that IP is down - so could have been my android phone or possibly the laptop (though I'm sure this was off by at least 22:59).
Obviously my first port of call was google and then to search this forum. But there were no helpful results I could see.
Thanks.