Newbie Alert!
I'm having problems connecting to my Joggler (SqueezeplayOS2) via Putty and need some help. It's probably something stupid that I'm doing or have overlooked ...
Story so far:
I installed SQPOS2 via flash drive, enabled LMS. Had a little play, streamed some radio. I was able to connect via Putty without issue (didn't do anything, just as a test).
I then started from scratch with a usb harddrive (intention being to run LMS from this joggler, with music files stored locally). Again I successfully installed SQPOS2, enabled LMS and pointed it at my music directory on the harddrive.
It's running really well, and I'm very happy with the user experience so far (SQPOS2 seems really polished).
BUT, I've now hit a problem trying to connect via Putty or WinSCP. Using Putty, all I get is a blank window, with a green cursor, but I cannot type anything. I think a connection has been established, as no error message is received (if I deliberately specify the wrong port, I get a connection refused message and the Putty window displays 'Inactive').
SSH is installed and started automatically by SQPOS2, and I have double-checked this via the menu structure.
Anybody got any ideas what am I doing wrong?
Help needed - SSH access - SQPOS2
Re: Help needed - SSH access - SQPOS2
Have you changed the network settings in SQPOS2 to connect to your wifi/ethernet? Does the Joggler show up in your router's DHCP list? Have you checked the IP address you are SSHing into in case your router has randomly changed it?
Re: Help needed - SSH access - SQPOS2
Thanks for the reply. The joggler is successfully connected via wifi, and I have assigned it a static IP via my router. I have triple checked that I'm using the correct IP address (192.168.0.10). I am able to ping the IP from my windows laptop, and can also access LMS via my browser (192.168.0.10:9000).
Any other ideas? There are no stupid questions (I'm a complete newbie to the Joggler, but vaguely computer literate), and can provide any further info as required. Thanks,
Any other ideas? There are no stupid questions (I'm a complete newbie to the Joggler, but vaguely computer literate), and can provide any further info as required. Thanks,
Re: Help needed - SSH access - SQPOS2
Yup; just connect your Joggler for a time to the network via a cable. Test out your SSH access there first. If it doesn't work then make necessary adjustments. Once stable then use your wireless connection.
Here my wireless network is separated by a firewall to the internet and the rest of teh network; such that I had to modify some stuff on the firewall to allow wireless access from the wired network to the wireless.
Here my wireless network is separated by a firewall to the internet and the rest of teh network; such that I had to modify some stuff on the firewall to allow wireless access from the wired network to the wireless.
- Pete
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens
Auto mater
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens
Auto mater
Re: Help needed - SSH access - SQPOS2
I've encountered a similar problem with sqpOS 2.
Installed earlier this week on usb - accessing via PuTTy is hit'n'miss .... more often than not, it fails with a timeout error. Moreover, when I scan the network with Netscan, again the Joggler shows randomly on the list of devices. Even though it's not listed my Touch can still access the server (???).
I suspect something changed in the wifi driver between vers 1.09 and 2.06 ... I think this is mentioned in the changelog.
Installed earlier this week on usb - accessing via PuTTy is hit'n'miss .... more often than not, it fails with a timeout error. Moreover, when I scan the network with Netscan, again the Joggler shows randomly on the list of devices. Even though it's not listed my Touch can still access the server (???).
I suspect something changed in the wifi driver between vers 1.09 and 2.06 ... I think this is mentioned in the changelog.
Re: Help needed - SSH access - SQPOS2
If you're using the default wireless card in the Joggler then the drivers are the same. It takes a few moments to generate the keys on first boot, but I'm assuming you've been trying to connect for longer than that would take!castalla wrote:I suspect something changed in the wifi driver between vers 1.09 and 2.06 ... I think this is mentioned in the changelog.
Can you ping the Joggler reliably?
BirdsLikeWires - Get fresh builds of Debian Bullseye, Bookworm, and Trixie for OpenFrame with the latest 5.10, 6.1, and 6.12 kernels! 
Re: Help needed - SSH access - SQPOS2
It's very strange. Installed 2.06 on usb - wifi access is very unreliable ssh terminal often fails with timeout. Very low transmission rates - incessant buffering on Shairplay, for example.
Switched back to 1.09 - no access problems, no buffering on Shairplay. I replicated this several times - with same effects.
Switched back to 1.09 - no access problems, no buffering on Shairplay. I replicated this several times - with same effects.
Re: Help needed - SSH access - SQPOS2
Mmm, that's a problem... I wonder what's changed there, then? The kernel is new, but the driver is just the same (it's not the kernel drive that we're using in either version). I didn't experience the problems mentioned here, but then my test router and test Joggler are in the same room, so maybe I've not been seeing it.
I'll have a play for the next release, maybe I can come up with something.
I'll have a play for the next release, maybe I can come up with something.
BirdsLikeWires - Get fresh builds of Debian Bullseye, Bookworm, and Trixie for OpenFrame with the latest 5.10, 6.1, and 6.12 kernels!
Re: Help needed - SSH access - SQPOS2
Thanks. I should mention that the Joggler is really on the outer reaches of my wifi range! It's as if 2.06 has less wifi reach than 1.06 ....