SqueezePlay OS for Joggler

[Mantaray]

I'm happy with any questions, to try and sort it, so thank you for the reply. But yes, I have selected the wireless tickbox both under the network tab in settings and in setup, entered the name of the network SSID and then selected 'apply changes and reboot.' When I've used WPA I also entered the WPA passphrase.

[JimbobVFR400]

I had a similar problem connecting to Wi-Fi that was resolved by a router reboot. I'd imagine you've tried that already but worth mentioning if not.

[dwl99]

There have also been reports of some Jogglers being quite fussy about what brand of router they connect to - can you borrow another router to try?

[DonnieH]

My joggler wouldn't connect to wireless until one day I opened it to have a look at something else and unplugged and plugged back in the usb receiver and then it started working. Might be something to look at

[Mantaray]

Thanks for the comments. The thing is that it will connect if I'm using the Joggler with Android or Jolicloud, so I'm surmising it's got something to do with how wifi is handled by the SqueezePlay OS network applet? A router reboot didn't help sadly.

[offbeatdave]

There have also been reports of some Jogglers being quite fussy about what brand of router they connect to - can you borrow another router to try?

Interesting. Since changing my router to a Netgear DGN3500, my Openframe2 unit will only connect wirelessly viaWPA-PSK [TKIP] , not via WPA2-PSK [AES] . Via the halfway house of WPA-PSK [TKIP] + WPA2-PSK [AES] it'll see the network but only fleetingly. Via WPA it was rock solid; it is only 4 inches from the router! The many Jogglers around the corners of the house on the other hand all connect without a hitch via WPA2.

The router is in 'up to 300MBps' wireless mode. Haven't bothered to try 'up to 150MBps' or 'g-only' modes.

I've actually got the Openframe2 unit connect with a wire at the moment!

[Mantaray]

Well, I've managed to connect to my Samsung S3 which I've setup as a hotspot, now just got to figure out what's happening with my Netgear Rangemax DG834N that SqueezePlay and my Joggler doesn't like!

[dwl99]

I recently bought one of these for under 20 quid http://www.amazon.co.uk/gp/offer-listin ... dition=new - it's a tiny router/accesspoint/range extender & is absolutely brilliant. It can also be powered by a USB port. You could stick it in as a range extender if you didn't want to change your router.

[roobarb!]

I know this probably won't help much, but I did used to have disconnection issues with one Joggler when I had two base stations in the house. One access point was supposed to cover the ground floor, while the other sat in the middle of the house. I changed over to using a single AirPort Extreme base station when I had BT Infinity installed and although the problems weren't bad before, they've completely vanished now.

Told you it wouldn't help much.

[Fishy]

2) there's a problem with the physical integrity of the connection itself, eg fine when board is cold but then lost when board heats up and expands slightly perhaps? - space was a little tight fitting connector through hole in back of case; or connector could be duff as it came from ebay anyway!
Either way, have now fed Behringer cable in through hole in case and connected it direct to the internal usb - hopefully that will cure it; fingers crossed.

You could try one of the other physical internal USB connections, as I know I've had trouble with them in the past. Memory sticks that would work perfectly in the external socket would fail miserably when installed internally. Not all of those internal connection points are the same. Some are USB2.0 only. Some are USB1.1 and USB2.0.

I use the internal USB socket (normally used for the wireless card) for a memory stick on my kitchen one and it's solid as a rock, so hopefully you'll have more luck with that!

Finally solved this, traced to poor connection from internal usb socket (one the wireless card previously was in) to Behringer sound card.
Tested everything to destruction over the weekend and has been solid as a rock (hate tempting fate by posting this....)

[Mantaray]

Thanks dwl99, I might have to try that. What kind of range does it have?

Roobarb, any ideas why the joggler would be rock solid with the Android and Jolicloud OS's but not connect with Squeezeplay? Is there something different in the way it handles DHCP for example, or does it need to have WPA security for it to work?

[dwl99]

I haven't tested the range but it is wireless N 150mbps and has internal antennae.

[roobarb!]

Roobarb, any ideas why the joggler would be rock solid with the Android and Jolicloud OS's but not connect with Squeezeplay? Is there something different in the way it handles DHCP for example, or does it need to have WPA security for it to work?

It does need WPA / WPA2 to work - WEP isn't supported. Is that what you are using?

[Mantaray]

I live in the middle of the countryside, so I normally just use MAC address filtering. But I thought WPA may be necessary, so I also tried it with both WPA and WPA2 with an eight digit passcode, but it still wouldn't connect. My SSID is simply the the generic 'HOME' so no strange settings there. I have toggled DHCP on and off, and the Android and Jolicloud OS's connect either way. It's just with Squeezeplay (although I seem to recall having a similar problem with XMBC). It's a mystery! Thanks for filling me in on the necessity for WPA though.

[roobarb!]

Thanks for filling me in on the necessity for WPA though.

No problem - it needs WPA/WPA2 security, a DHCP server to give it an address and the SSID shouldn't be hidden. With that little lot it should work fine!

There's no network manager in sqpOS, so the settings are just popped into the wlan0 entry in /etc/network/interfaces. There is a wicd based config applet for it on these forums, though (by Wilberforce) - perhaps you could try that as well?

[offbeatdave]

There have also been reports of some Jogglers being quite fussy about what brand of router they connect to - can you borrow another router to try?

Interesting. Since changing my router to a Netgear DGN3500, my Openframe2 unit will only connect wirelessly viaWPA-PSK [TKIP] , not via WPA2-PSK [AES] . Via the halfway house of WPA-PSK [TKIP] + WPA2-PSK [AES] it'll see the network but only fleetingly. Via WPA it was rock solid; it is only 4 inches from the router! The many Jogglers around the corners of the house on the other hand all connect without a hitch via WPA2.

The router is in 'up to 300MBps' wireless mode. Haven't bothered to try 'up to 150MBps' or 'g-only' modes.

I've actually got the Openframe2 unit connect with a wire at the moment!

At the risk of deviating further off topic, the update to my scenario above is that last night I reflashed the router with a modded firmware (you'd think I'd have had enough of tinkering by now!) and the Openframe 2 unit WILL now connected via WPA2! There appears to be an element of 'fussiness' when it comes to gadgets and wifi connectivity/security.

[gegs]

The router is in 'up to 300MBps' wireless mode. Haven't bothered to try 'up to 150MBps' or 'g-only' modes.

I've gone from the 'up to 300MBps' setting back to 'up to 150MBps'. The higher setting didn't seem very stable and didn't sit well with all my devices; for example, Netflix on my Apple TV used to buffer quite often on the higher setting but is far more reliable on the lower one. I haven't had an "Oh no! Not again!" buffering moment whilst watching a film since I changed. Squeezeplay on the Joggler seems to be better too.

I've read a lot of forum posts (not this one) that recommend the lower setting for stability and it has definitely worked for me.

[Fishy]

Murphy's law for Jogglers - as soon as you think you've nailed it, something else goes wrong.

Came home on Thursday to find kitchen one (PnPIII) wouldn't respond at all after Mrs F had tried to watch something on iPlayer.
Reboot was only option and sickeningly and predictably resulted in dreaded O2 black screen lock up.
Reflashed to original O2-build then upgraded to latest PnPIII.
It was hardwired before (albeit via Powerline adaptors) but now refuses to acquire an IP via network settings.
Have tried everything but the only way to get it going is with the (formerly) internal wireless card which is now sticking out of the usb on the right!
Ironic that I removed the wireless so could have a hidden internal usb connection for the soundcard for purely aesthetic reasons - just like a naughty schoolboy who won't keep his tie straight, these Jogglers don't do good looks or clean lines!!!
Have a 10m cable on order so can temporarily eliminate Powerlines and see if can persuade it to behave itself and use ethernet.

Oh what fun! Really can't remember what I did in the evenings before this Joggler nonsense took over!!

[Fishy]

Update - fault traced to dodgy Powerline adaptor so not the Jogglers fault at all !

[offbeatdave]

Came home on Thursday to find kitchen one (PnPIII) wouldn't respond at all after Mrs F had tried to watch something on iPlayer.
Reboot was only option and sickeningly and predictably resulted in dreaded O2 black screen lock up.

No help now, but if anything locks up and you can still access the Joggler remotely, you can usually just restart tango via the web interface (type the Joggler's IP address into a web browser and select the restart tango option, or telnet into the Joggler and type

Code: Select all

killall tango

which should bring you back to the main screen.

Promise to stop drifting off the SqueezePlay OS topic now!