I just had cause to use this and came up with a few hurdles I had to
workaround - posting in case this helps anyone.

So, the reason I needed to use it was because I wanted to set up
"bridging" on my Receiver.  The Receiver is on the WiFi but I have an
Ethernet-only device (Raspberry Pi) I wanted to hang off it.  This can
be done but only if you can switch on the bridging.

My first attempt was to use the compiled program found at
http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe.   However, this
doesn't work - it gives lots of errors when run.  I managed to track
down what I think is the problem: it uses ipconfig on Windows to find
the local IP Address.  However, the program assumes it is called "IP
Address" whereas for some time now (since Vista I think!) it is actually
now called "IPv4 Address" so that doesn't work.

So I think you have to use the source Perl version.  I got that down but
I had a lot of trouble installing the correct Perl pre-requisites on my
Windows machine.  I could get ActiveState Perl but getting the
additional modules didn't seem to work for me.  I think this is because
the cpan command assumes you have gmake and gcc installed and maybe
other things too.   There might be a way to get that all to work but I
gave up.

Instead I ran it on a Linux box and that was much easier.  Essentially
all I had to was this:


Code:
--------------------
    sudo apt install build-essential
  sudo cpan install Log::StdLog Term::Shell Class::Accessor 
IO::Interface::Simple
  git clone https://github.com/robinbowes/net-udap.git
  cd net-udap
  ./scripts/udap_shell.pl
--------------------


There was still some further confusion, however.  I have an SB3, the
SBR, and also a Radio.  All three seem to behave differently and the
Radio in particular seems to cause errors.  The SBR seems to be only
contactable when it is in init mode (red flashing slowly) and in that
mode it seems like it is no longer on the house wifi so it's no longer
accessible.  I think in that mode you need to use the Ethernet (or it's
own special direct wifi).  The SB3 by contrast is easy to discover and
access - but that's also not needed since it is configurable via the
remote.

The answer for me, anyway, was to connect the SBR directly to the PC via
Ethernet and then I could get the config working and with no chance of
confusion with the other Squeezies on the network.

Hope this is helpful to someone.

Ben


------------------------------------------------------------------------
bstrulo's Profile: http://forums.slimdevices.com/member.php?userid=15997
View this thread: http://forums.slimdevices.com/showthread.php?t=57861

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss

Reply via email to