I did it (we were nearly right).

Code:

ssh -L 5900:<LMCEserver>:5900 <user>@<othermachine>

Still not quite sure I have understood what I have done... could somebody please educate me? Why is 5900 in there twice? How does this relate to my firewall rule?

Cheers,
Matt.

OK, the ssh -L thing did work, but it only logs into the LMCE server - I am looking for a way to remotely ssh directly into another machine on my network.

I also tried ssh -p5900 <LMCEserver> again, but to no avail - connection refused. Admin firewall setting is...

tcp   ipv4   5900 to 5900   22   192.168.80.XXX   port_forward

@Sigg3.net - thanks for the suggestion, but an X forward won't cut it unfortunately. I didn't explain myself very well. I want to be able to share a desktop with somebody remotely (hence I'm now frigging with port 5900, as I intend to use VNC).

Any other suggestions?

Cheers,
Matt.

Thanks for sticking with me!

With everything set up, before running squeezeslave, "squeezeslave -L" is as follows...

Code:

dcerouter_1023729:~# squeezeslave -L
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, &lowLatency )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 415
Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, &lowLatency )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 415
Output devices:
  0: (ALSA) HDA ATI SB: ALC889 Analog (hw:0,0) (11/46)
  1: (ALSA) HDA ATI SB: ALC889 Digital (hw:0,1) (11/46)
  3: (ALSA) C-Media USB Audio Device   : USB Audio (hw:1,0) (11/46)
  4: (ALSA) front (11/46)
  5: (ALSA) surround40 (11/46)
  6: (ALSA) surround41 (11/46)
  7: (ALSA) surround50 (11/46)
  8: (ALSA) surround51 (11/46)
  9: (ALSA) surround71 (11/46)
 10: (ALSA) iec958 (11/46)
 11: (ALSA) spdif (11/46)
 13: (ALSA) asym_analog (42/46)
 14: (ALSA) dmix (42/42)
*15: (ALSA) default (42/46)
 16: (OSS) /dev/dsp (11/46)
 17: (OSS) /dev/dsp1 (11/46)

Then I run "/usr/bin/squeezeslave -o3 -m00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log" which gives...

Code:

dcerouter_1023729:~# /usr/bin/squeezeslave -o3 -m00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, &lowLatency )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 415
Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, &lowLatency )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 415

And then if I do "squeezeslave -L" again I get...

Code:

bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, &lowLatency )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 415
Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, &lowLatency )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 415
Output devices:
  0: (ALSA) HDA ATI SB: ALC889 Analog (hw:0,0) (11/46)
  1: (ALSA) HDA ATI SB: ALC889 Digital (hw:0,1) (11/46)
  4: (ALSA) front (11/46)
  5: (ALSA) surround40 (11/46)
  6: (ALSA) surround41 (11/46)
  7: (ALSA) surround50 (11/46)
  8: (ALSA) surround51 (11/46)
  9: (ALSA) surround71 (11/46)
 10: (ALSA) iec958 (11/46)
 11: (ALSA) spdif (11/46)
 13: (ALSA) asym_analog (42/46)
 14: (ALSA) dmix (42/42)
*15: (ALSA) default (42/46)
 16: (OSS) /dev/dsp (11/46)

...note the lack of C-Media USB audio device. Is that normal behaviour?

Cheers,
Matt.

Haha tranquilo.

Well that is exactly how I had it set up in the first place. I created a new room called "Guitar Amp", and assigned the squeezeslave to that. So back to my very first post :-)

Cheers,
Matt.

Carlos,

But the room "Guitar Amp" does not have an MD!

I thought your first post says to not put it in a room without an MD?

The USB sound card is physically installed on the core/hybrid in "Cupboard".

Cheers,
Matt.

Hmmm I don't see what I am doing wrong.

I created a new room called "Guitar Amp". My USB sound card is physically on the core, and the core is in the room "Cupboard". There is no MD in "Guitar Amp".

In web admin, under A/V devices, on the Squeezeslave, I have chosen "Cupboard" for the room, and then in advanced selected "Guitar Amp" under Entertain Areas. The setting does not seem to stick. The Entertain Areas just goes back to the default of "Cupboard" being ticked.

Is this what I am supposed to be doing? Under the Rooms settings, I see there is an option to tick "manually configure EA", but when I tick it, nothing happens! And if I refresh, the tick dissapears.

Cheers,
Matt.

Thank you, most kind.

I should mention that I was trying to do this from the point of view of sharing a specific window with a friend, who is in a remote location. But I have no confidence that this is even possible (was hoping to do something clever with an X forward). So remote VNC it is.

One tutorial I've looked at mentions running "ssh -L 5900:localhost:5900 <hostname>" on the remote machine before running the VNC viewer - is that command necessary in addition to what we are trying to do, to create a tunnel? I think that port relates to VNC. Or does it relate to tightVNC specifically? Again, I dunno. I will try it out with this port though when I get home.

Cheers,
Matt.

Nope, it's connected directly to the Internet.

But I can ssh into the core, and then ssh into the desktop, so surely the problem isn't there in any event?

Is there perhaps some sort of special ssh permissions on the desktop I need to set, for when it is being ssh-ed into directly?

No idea.

Cheers,
Matt.

In Theory this should work, but havent tested it yet..

ssh your no-ip on port 10015  then the core will forward port 10015 to port 22 on your desktops IP. In the example the Desktop Ip would be 10.0.0.15.

Webadmin -- Advanced -- Network -- Firewall Rules.

Thanks for this.

Unfortunately my remote machine says "Connection refused". I have ssh-ed into the core, and then ssh-ed into the desktop in question without any problems. Firewall is set up with a port forward as per your example. Have also tried a few different ports.

Any clues?

Cheers,
Matt.

I should have said, the command I thought most likely to be appropriate was...

Code:

ssh -p1234 <MyExternalIP>

...but I wasn't sure where/what port 1234 was, or the correct way to set this/a port up in web admin. This port must relate to my desktop right?

Cheers,
Matt.

Have spent a lot of time researching this, and am struggling to sort fact from fiction, so thought I would ask my friends at LMCE.

I can ssh into my core using my no-ip IP address no problem, and I can ssh into my desktop from there (which sits on the internal LMCE network).

What I would like to do is remotely ssh into the desktop directly. I undertand this involves me forwarding ports on the router, but I am struggling to put the theory into context.

Could anybody tell me what I have to do to set this up in web admin, and the ssh command I would have to issue? I think I just need a real example to get my head round this.

Cheers,
Matt.

Thanks for the replies chaps.

That is exactly what I did - added the squeezeslave to a room with no MD. I have clearly misunderstood how this works. I created a new room specifically for the squeezeslave, in fact.

Am I supposed to create an MD first? If so, how do I do that without MD hardware?

Or am I supposed to be adding it to an existing MD i.e. the core MD in this case? If so, how do I tell LMCE to play audio to the squeezeslave, and not the MD (using the orbiter)?

Cheers,
Matt.

Andrew,

Thanks for the reply, very useful, as always.

I apprecate these multi-channels are a robust way of getting the desired result, but I really wanted to avoid shelling out for one of those (and having to deal with setting it up etc).

I believe I am right in saying that a Squeezebox has a built in speaker? And it cannot drive an amp? Although I guess if it has headphones output or similar, that can be used.

That Keene in-wall amp looks fantastic. At first I thought that £100 is a bit steep, but when you think that my solution requires a mobo (~£50), an amplifier (~£30) and PSU (~£20), and won't be as energy efficient, it makes an awful lot of sense. Thanks!

Just need somebody to sort this out for me now http://forum.linuxmce.org/index.php/topic,12605.0.html

davegravy,

I don't need the audio zones to sync. I have read a few threads about this, appears to be a common problem. Does the audio sync properly between MDs out of interest?

Cheers,
Matt.

I have two approaches in my head, and I don't know which one would be best.

I want some speakers in the garden and in the bathroom, which will require an amp of course. The amps I am looking at are just a cheapo low-power 2 channel things - I am not interested in rinsing hundreds of pounds on uber Denon rs232 controlled amps. So which is best...

1. Squeezeslave USB sound cards on the core, with the amps ALWAYS on waiting to be used. How much energy does an amp use when it is on, but nothing is playing? Is it recommended/safe?

2. Cheapo Atom boards for each zone, with the amp being powered off the PSU, meaning it will switch on and off when the mobo is switched on and off. Overkill? Or brilliant? Less energy usage, if a little bit more expensive?

I am leaning towards 2, it will work out cheaper than a squeezebox (or there won't be a lot in it at least). Or is there another approach that I may have missed?

Cheers,
Matt.

Brilliant idea, Langston. And a very good incentive. I look forward to judging everybody's hard work.

Cheers,
Matt.