PDA

View Full Version : Net::UDAP - SqueezeBox Receiver configuration tool



Pages : [1] 2

Robin Bowes
2009-01-08, 04:46
Hi all,

Net::UDAP is a Perl module to configure the SqueezeBox Receiver (SBR)
from a PC, i.e. without requiring a SqueezeBox Controller (SBC).

The project homepage is here:

http://projects.robinbowes.com/Net-UDAP

Net::UDAP was originally released in June 2008 and there have been no
significant changes since then. However, I've recently updated the
documentation so thought I'd post this announcement in case anyone tried
it previously but got stuck for whatever reason.

I've also fixed the registration system on the website so it is now
possible to register, login, and create support tickets. You could even
go completely crazy and add/improve the doucmenation by editing the wiki!

Net::UDAP is free software, but allow me to draw your attention to my
Paypal donnation link:

http://projects.robinbowes.com/Net-UDAP/trac/wiki/WikiStart#Donations

;)

Enjoy!

R.

peter
2009-01-08, 05:50
Excellent work, Robin!
I'll check it out.

IMHO LogiTech should make a handsome donation for your good work (and
work they should've been doing themselves).
How about 5 free Duets for each of your kids? ;)

Regards,
Peter

Robin Bowes
2009-01-08, 05:58
Peter wrote:
> Excellent work, Robin!
> I'll check it out.
>
> IMHO LogiTech should make a handsome donation for your good work (and
> work they should've been doing themselves).
> How about 5 free Duets for each of your kids? ;)

Oh, I get my rewards, direct and indirect.

For example, I start a new perl coding job on Monday 12th essentially on
the back of my Net::UDAP code.

So, I'm fairly happy.

That's not to say that I wouldn't welcome more recompense, financial or
otherwise ;)

R.

peter
2009-01-09, 11:32
Robin Bowes wrote:
> Hi all,
>
> Net::UDAP is a Perl module to configure the SqueezeBox Receiver (SBR)
> from a PC, i.e. without requiring a SqueezeBox Controller (SBC).
>
> The project homepage is here:
>
> http://projects.robinbowes.com/Net-UDAP
>
> Net::UDAP was originally released in June 2008 and there have been no
> significant changes since then. However, I've recently updated the
> documentation so thought I'd post this announcement in case anyone tried
> it previously but got stuck for whatever reason.
>

I've 'compiled' this version with perlapp from the Activestate Perl PDK.
The resulting executable is a probably bit easier to user for the average
SB user. You can put it up on the Net-UDAP page if you want.

http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe

Regards,
Peter

Robin Bowes
2009-01-09, 13:55
Peter wrote:

> I've 'compiled' this version with perlapp from the Activestate Perl PDK.
> The resulting executable is a probably bit easier to user for the average
> SB user. You can put it up on the Net-UDAP page if you want.
>
> http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe

Thanks for this.

Any idea about the licensing implications? i.e. is it freely distributable?

R.

Robin Bowes
2009-01-09, 14:02
Robin Bowes wrote:
> Peter wrote:
>
>> I've 'compiled' this version with perlapp from the Activestate Perl PDK.
>> The resulting executable is a probably bit easier to user for the average
>> SB user. You can put it up on the Net-UDAP page if you want.
>>
>> http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe
>
> Thanks for this.
>
> Any idea about the licensing implications? i.e. is it freely distributable?

Hmmm, I get the variable "not initialised" msgs when I ran this the
first time, but it was OK with code direct from the RELEASE_1.0.0 tag
and also the second time I ran this executable. I wonder what causes that?

R.

Howard Passman
2009-01-09, 17:29
Robin Bowes wrote:
> Hi all,
>
> Net::UDAP is a Perl module to configure the SqueezeBox Receiver (SBR)
> from a PC, i.e. without requiring a SqueezeBox Controller (SBC).
>
> The project homepage is here:
>
> http://projects.robinbowes.com/Net-UDAP
>
> Net::UDAP was originally released in June 2008 and there have been no
> significant changes since then. However, I've recently updated the
> documentation so thought I'd post this announcement in case anyone tried
> it previously but got stuck for whatever reason.
>

I've 'compiled' this version with perlapp from the Activestate Perl PDK.
The resulting executable is a probably bit easier to user for the average
SB user. You can put it up on the Net-UDAP page if you want.

http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe

Regards,
Peter

Hi Peter,

I got your UI to work, but am not sure how to change parameters. I assumed "set" then the parameter name and then the value, but that wasn't it. Could you give us less technical folks a hint about how to change or set parameters.

Also, it appears you have to reset the device to default in order to get in to it. If someone wanted to change one parameter is it possible for you to make is so we could "discover" a specific MAC address or ip?

Thanks to you and Robin for all the work. My only comment is the folks that really need this (first time users of the SBR) probably won't be able to use the tool unless you come up with a much easier UI.

Thanks,

Howard

peter
2009-01-10, 00:15
Robin Bowes wrote:
> Peter wrote:
>
>
>> I've 'compiled' this version with perlapp from the Activestate Perl PDK.
>> The resulting executable is a probably bit easier to user for the average
>> SB user. You can put it up on the Net-UDAP page if you want.
>>
>> http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe
>>
>
> Thanks for this.
>
> Any idea about the licensing implications? i.e. is it freely distributable?
>

I have a license for the compiler, so I can distribute the executable.
That means I can share it with anyone I want. That's fairly standard for
compilers. Perlapp isn't really a compiler though. It bundles the Perl
compiler and the libraries used inside the exe-package and unpacks it
all before running. That's why you'll notice that the start up time is
slower because of the unpacking.

I know the Logitech guys use perlapp for packaging SqueezeCenter, so
they could have packed it for you too. Even better, they could also make
an OS-X executable.

Regards,
Peter

peter
2009-01-10, 00:27
Howard Passman wrote:
> Hi Peter,
>
> I got your UI to work, but am not sure how to change parameters. I
> assumed "set" then the parameter name and then the value, but that
> wasn't it. Could you give us less technical folks a hint about how to
> change or set parameters.
>
> Also, it appears you have to reset the device to default in order to
> get in to it. If someone wanted to change one parameter is it possible
> for you to make is so we could "discover" a specific MAC address or ip?
>
> Thanks to you and Robin for all the work. My only comment is the folks
> that really need this (first time users of the SBR) probably won't be
> able to use the tool unless you come up with a much easier UI.
>

Howard,

I didn't create the UI, Robin deserves all credit for that. I just
compiled the program in an easily distributable Windows exe format. I
agree that the UI should (and could) be much easier. I could create a
Windows wizard myzelf (with the wxPerl library) but I really don't have
the time to spare. I also figure that this is really a task for the
Logitech guys. I don't understand how they get away with selling the SBR
as a separate product without providing a simple setup tool with it.
Open Source does not mean you let your users do all the work.

I can design one, though.
- Start the wizard
- A list of detected SBRs is displayed, select one
- Q: Ethernet or Wireless

Wireless:
WEP or WPA?
- Enter WEP/WPA key
- Enter SSID

Wireless/Ethernet:
DHCP or manual?
- Enter IP
- Enter netmask
- Enter gateway
- Enter squeezecenter server

- Save settings

That wasn't so hard ;)
A few days work added to the stuff Robin already did.

Regards,
Peter

Robin Bowes
2009-01-10, 04:04
Howard Passman wrote:
> peter;381812 Wrote:
>> Robin Bowes wrote:
>>> Hi all,
>>>
>>> Net::UDAP is a Perl module to configure the SqueezeBox Receiver (SBR)
>>> from a PC, i.e. without requiring a SqueezeBox Controller (SBC).
>>>
>>> The project homepage is here:
>>>
>>> http://projects.robinbowes.com/Net-UDAP
>>>
>>> Net::UDAP was originally released in June 2008 and there have been no
>>> significant changes since then. However, I've recently updated the
>>> documentation so thought I'd post this announcement in case anyone
>> tried
>>> it previously but got stuck for whatever reason.
>>>
>> I've 'compiled' this version with perlapp from the Activestate Perl
>> PDK.
>> The resulting executable is a probably bit easier to user for the
>> average
>> SB user. You can put it up on the Net-UDAP page if you want.
>>
>> http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe
>>
>> Regards,
>> Peter
>
> Hi Peter,
>
> I got your UI to work, but am not sure how to change parameters. I
> assumed "set" then the parameter name and then the value, but that
> wasn't it. Could you give us less technical folks a hint about how to
> change or set parameters.

Howard,

There's a guide here:

http://projects.robinbowes.com/Net-UDAP/trac/wiki/GettingStarted

In a nutshell, you're right; setting/changing parameters is done, e.g.,
like this:

UDAP> discover
UDAP> list
# MAC Address Type Status
== ================= ========== ===============
1 00:04:20:16:05:8f squeezebox init
UDAP> configure 1
UDAP [1] (squeezebox 16058f)> set server_address=192.168.1.50
UDAP [1] (squeezebox 16058f)> save_data

> Also, it appears you have to reset the device to default in order to
> get in to it. If someone wanted to change one parameter is it possible
> for you to make is so we could "discover" a specific MAC address or ip?

You don't have to reset the device - just put it in init mode, i.e.
slow-blinking red LED.

> Thanks to you and Robin for all the work. My only comment is the folks
> that really need this (first time users of the SBR) probably won't be
> able to use the tool unless you come up with a much easier UI.

I initially started work on a SC plugin that does this - I ought to
re-visit it and get it finished. Spare time is the issue...

R.

Robin Bowes
2009-01-10, 04:07
Peter wrote:
> I don't understand how they get away with selling the SBR
> as a separate product without providing a simple setup tool with it.
> Open Source does not mean you let your users do all the work.

The SBR is sold separately for users who require > 1 receiver with just
one controller, i.e. buy a duet + a separate SBR or two.

R.

mherger
2009-01-10, 04:28
> I know the Logitech guys use perlapp for packaging SqueezeCenter, so
> they could have packed it for you too. Even better, they could also make
> an OS-X executable.

We only use PerlApp on Windows (so far). Shouldn't the script run on OSX'
perl installation?

Michael

Howard Passman
2009-01-10, 05:31
Howard Passman wrote:
> peter;381812 Wrote:
>> Robin Bowes wrote:
>>> Hi all,
>>>
>>> Net::UDAP is a Perl module to configure the SqueezeBox Receiver (SBR)
>>> from a PC, i.e. without requiring a SqueezeBox Controller (SBC).
>>>
>>> The project homepage is here:
>>>
>>> http://projects.robinbowes.com/Net-UDAP
>>>
>>> Net::UDAP was originally released in June 2008 and there have been no
>>> significant changes since then. However, I've recently updated the
>>> documentation so thought I'd post this announcement in case anyone
>> tried
>>> it previously but got stuck for whatever reason.
>>>
>> I've 'compiled' this version with perlapp from the Activestate Perl
>> PDK.
>> The resulting executable is a probably bit easier to user for the
>> average
>> SB user. You can put it up on the Net-UDAP page if you want.
>>
>> http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe
>>
>> Regards,
>> Peter
>
> Hi Peter,
>
> I got your UI to work, but am not sure how to change parameters. I
> assumed "set" then the parameter name and then the value, but that
> wasn't it. Could you give us less technical folks a hint about how to
> change or set parameters.

Howard,

There's a guide here:

http://projects.robinbowes.com/Net-UDAP/trac/wiki/GettingStarted

In a nutshell, you're right; setting/changing parameters is done, e.g.,
like this:

UDAP> discover
UDAP> list
# MAC Address Type Status
== ================= ========== ===============
1 00:04:20:16:05:8f squeezebox init
UDAP> configure 1
UDAP [1] (squeezebox 16058f)> set server_address=192.168.1.50
UDAP [1] (squeezebox 16058f)> save_data

> Also, it appears you have to reset the device to default in order to
> get in to it. If someone wanted to change one parameter is it possible
> for you to make is so we could "discover" a specific MAC address or ip?

You don't have to reset the device - just put it in init mode, i.e.
slow-blinking red LED.

> Thanks to you and Robin for all the work. My only comment is the folks
> that really need this (first time users of the SBR) probably won't be
> able to use the tool unless you come up with a much easier UI.

I initially started work on a SC plugin that does this - I ought to
re-visit it and get it finished. Spare time is the issue...

R.


Thanks Robin. The only comand line stuff I'm used to is Windows or CISCO so I used a space between the command and the parameter. I see I needed to use a =.

Thanks very much

Howard Passman
2009-01-10, 05:42
Peter wrote:
> I don't understand how they get away with selling the SBR
> as a separate product without providing a simple setup tool with it.
> Open Source does not mean you let your users do all the work.

The SBR is sold separately for users who require > 1 receiver with just
one controller, i.e. buy a duet + a separate SBR or two.

R.

When you read these forums the beginners who buy the DUET seem to have the biggest issue with getting the SBR set up. Logitech could eliminate a huge amount of bad feelings towards their SBR by creating a UI to set the network paramters. It's the only device out there that I know of that you need to set up this way. Even CISCO routers you can use command line, which I found easier than using the SBC. As a matter of fact I still do. Although I no longer have a problem setting up a SBR with the SBC, it still takes longer than an alternative way would. This is self evident by the fact I and others are messing with Robin's tool (stop the snickers) rather than using the provided routine. There is always an active thread calling for this exact item.

The SB line is fun, affordable and works pretty well, but all a competitor would need to do is make a few things easier and make parts and accessories avaliable and I think you'd see a drop in sales for Logitech. They (the manufacturer) seem to be pretty stubborn for someone dealing with the general public on an entertainment product. Just my take.

Howard

Mnyb
2009-01-10, 07:32
I agree NET-UDAP is nedeed for the setup even if you have an SBC.

It is completely logical to have two independent setup procedures one for SBC and one for SBR as they are two separate machines. To make one depend on the other is a bizzare choice ?

The benchmarks is actually the SB2,3 classic so "they " know how to do it ;-)

a couple of clicks with the ir remote and you can change for example the dns settings.

But if I read my flood of bugmail corectly there is promising work going on.
to their credit they are doing something and actually listened to the users.

peter
2009-01-10, 08:22
Michael Herger wrote:
>> I know the Logitech guys use perlapp for packaging SqueezeCenter, so
>> they could have packed it for you too. Even better, they could also make
>> an OS-X executable.
>>
>
> We only use PerlApp on Windows (so far). Shouldn't the script run on OSX'
> perl installation?
>

Windows, Linux, OSX. All of them, I guess.

But Windows & OSX should cover most customers and Linux boxes usually
have Perl installed already.

Regards,
Peter

peter
2009-01-10, 08:26
Mnyb wrote:
> The benchmarks is actually the SB2,3 classic so "they " know how to do
> it ;-)
>

They don't have a computer based setup either.
They have their own UI.
Not great, but workable.

> But if I read my flood of bugmail corectly there is promising work
> going on.
> to their credit they are doing something and actually listened to the
> users.
>

There's this standard easy setup stuff for Wifi they're trying to
implement, I guess.
But a generic (SB/SBR/Transporter) windows/osx based GUI setup program
would be probably be a better choice.

Regards,
Peter

Mnyb
2009-01-11, 04:12
Mnyb wrote:
> The benchmarks is actually the SB2,3 classic so "they " know how to do
> it ;-)
>

They don't have a computer based setup either.
They have their own UI.
Not great, but workable.

> But if I read my flood of bugmail corectly there is promising work
> going on.
> to their credit they are doing something and actually listened to the
> users.
>

There's this standard easy setup stuff for Wifi they're trying to
implement, I guess.
But a generic (SB/SBR/Transporter) windows/osx based GUI setup program
would be probably be a better choice.

Regards,
Peter

Yes i mentioned the SB3 as this actually works and is simple to use.
That was what i meant with "they know how to do it"

a GUI setup pgm of some sort would be exellent, and to be able to alter one setting without going trough the whole settings procedure is a given.
This also works with the old product.

TKSQB
2009-02-14, 11:09
Peter wrote:
> Excellent work, Robin!
> I'll check it out.
>
> IMHO LogiTech should make a handsome donation for your good work (and
> work they should've been doing themselves).
> How about 5 free Duets for each of your kids? ;)

Oh, I get my rewards, direct and indirect.

For example, I start a new perl coding job on Monday 12th essentially on
the back of my Net::UDAP code.

So, I'm fairly happy.

That's not to say that I wouldn't welcome more recompense, financial or
otherwise ;)

R.

Hello!
Thanks for the tool.- But I have problem with running it. The comes different error-messages, for example "error lin Line 27", and after copying file to my path "error in lin31".
I habe OS "Win Vista" and Perl 5.8.8. What must I do that "udap_shell.pl" works well, so that I can configure my squeezebox without controller?
Regards
Bernd

TKSQB
2009-02-14, 11:55
Thanks Robin. The only comand line stuff I'm used to is Windows or CISCO so I used a space between the command and the parameter. I see I needed to use a =.

Thanks very much

Hello!
Great,- I can start the exe, but how must I setup the commands? I must do configuration for the squeezebox, but trying " wireless_wpa_cipher: 1 - TKIP, 2 - AES, 3 - TKIP & AES
wireless_wpa_mode: 1 - WPA, 2 - WPA2
wireless_wpa_on: 0 - WPA Off, 1 - WPA On
wireless_wpa_psk: WPA Public Shared Key
UDAP> set lan-network-address=192.168.0.19
set command not valid here
UDAP> set lan-network-address:192.168.0.19
set command not valid here
UDAP> set server_address=192.168.0.19
set command not valid here
UDAP> configure logitech+squeezebox+000420173046
UDAP> server_address=192.168.0.19
Unknown command 'server_address=192.168.0.19'; type 'help' for
s.
UDAP> list
# MAC Address Type Status
== ================= ========== ===============
1 00:04:20:17:30:46 squeezebox init
UDAP> server_address=192.168.0.19
Unknown command 'server_address=192.168.0.19'; type 'help' for
s.
UDAP> configure logitech+squeezebox+000420173046
UDAP> set server_address=192.168.0.19
set command not valid here
UDAP>
"

donīt work.
What do I wrong???

Regards

TKSQB
2009-02-18, 13:20
Robin Bowes wrote:
> Peter wrote:
>
>
>> I've 'compiled' this version with perlapp from the Activestate Perl PDK.
>> The resulting executable is a probably bit easier to user for the average
>> SB user. You can put it up on the Net-UDAP page if you want.
>>
>> http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe
>>
>
> Thanks for this.
>
> Any idea about the licensing implications? i.e. is it freely distributable?
>

I have a license for the compiler, so I can distribute the executable.
That means I can share it with anyone I want. That's fairly standard for
compilers. Perlapp isn't really a compiler though. It bundles the Perl
compiler and the libraries used inside the exe-package and unpacks it
all before running. That's why you'll notice that the start up time is
slower because of the unpacking.

I know the Logitech guys use perlapp for packaging SqueezeCenter, so
they could have packed it for you too. Even better, they could also make
an OS-X executable.

Regards,
Peter
hello! I used the udap_sshell.exe-tool but my SQB wonßt work.- No ethernet direct an no wlan.
My conf. looks so:

UDAP [1] (squeezebox 173046)> list
bridging: 0
hostname:
interface: 0
lan_gateway: 192.168.0.1
lan_ip_mode: 0
lan_network_address: 192.168.0.19
lan_subnet_mask: 255.255.255.0
primary_dns: 192.168.0.1
secondary_dns: 0.0.0.0
server_address: 0.0.0.0
squeezecenter_address: 192.168.0.8
squeezecenter_name:
wireless_SSID: TIT4N
wireless_channel: 3
wireless_keylen: 1
wireless_mode: 0
wireless_region_id: 14
wireless_wep_key_0:
wireless_wep_key_1: examplekey1111111
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 0
wireless_wpa_cipher: 3
wireless_wpa_mode: 0
wireless_wpa_on: 1
wireless_wpa_psk:

Iīm nerved, because i DOMīT NO WHERE is the problem. logitech wil not help, becaquse the tool is not supported.- they will sell their controller.
regards aīnd thanks

cdmackay
2009-02-20, 19:00
wireless_SSID: TIT4N
wireless_channel: 3
wireless_keylen: 1
wireless_mode: 0
wireless_region_id: 14
wireless_wep_key_0:
wireless_wep_key_1: examplekey1111111
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 0
wireless_wpa_cipher: 3
wireless_wpa_mode: 0
wireless_wpa_on: 1
wireless_wpa_psk:


Looks like you have turned on WPA (wireless_wpa_on: 1), but not set a WPA key (PSK), and set a WEP key, but not turned on WEP (wireless_wep_on: 0). Was that intentional?

cdmackay
2009-02-20, 19:02
I noticed an oddity: I have multiple network interfaces; I note that the shell only sends the UDP broadcast out over the first interface.

If the SBR happens to be on another interface, the SBR never sees the broadcast.

I had to bring down my other interfaces, leaving only the SBR network up, in order for it to work.

TKSQB
2009-02-21, 11:50
Hello!
Thanks to All. Now Iīve found out the errors and it works fine without controller.
Regards

mirhon
2009-03-11, 07:29
@Peter

I'm not sure how to add WEP key using your udap_shell_1_0_0.exe.
On Net-UDAP site:
http://projects.robinbowes.com/Net-UDAP/trac#January212009
I can read:
"I just committed a change that switches to hex entry for WEP keys. This simply means that instead of entering a hex key like this: abcd, you should now enter it like this: 61626364."

How to add WEP key using this exe (hex or plain text)?

mirhon
2009-03-13, 11:06
I've done it. It works fine :-)
I configured my receiver to use DHCP (via WiFi) but now (from some reasons) I have to change its settings.
Can I change this to static IP doing it the same way as at the beginning?
Do I have to reset my squeezebox to original state before I start?

loafsta
2009-04-18, 12:43
I'm definitely a novice and apologize in advance if I'm asking this question in the wrong place or if it has been covered elsewhere - I've certainly looked for an answer, but haven't found one that seemed on point. I'm considering getting an SBR (w/out SBC), using NAS running SC on an onboard Ubuntu system and controlled w/ ipeng on ipod touch to feed music stored on the NAS to my stereo without having my computer on. Wondering if anyone has experience/pointers before I make the plunge. Should I expect any issues setting up SBR on my laptop with Net::UDAP, identifying the SBR through SC running on my NAS (connected to SBR by ethernet through router) and using ipeng as controller using the router's wifi (rather than P2P with the SBR) even when my laptop is off? I assume once my SBR is set up, any devices running SC (such as my NAS) will be able to find it, but not sure.

Any thoughts would be appreciated.

cdmackay
2009-04-19, 09:43
mirhon wrote:
> I've done it. It works fine :-)
> I configured my receiver to use DHCP (via WiFi) but now (from some
> reasons) I have to change its settings.
> Can I change this to static IP doing it the same way as at the
> beginning?
> Do I have to reset my squeezebox to original state before I start?

I think you do.

In my experience, the SB will only respond to the UDAP discovery if the
SB is in its config state, i.e. slow flashing red LED.

cheers,
calum.

cdmackay
2009-04-19, 09:51
loafsta wrote:
> I'm definitely a novice and apologize in advance if I'm asking this
> question in the wrong place or if it has been covered elsewhere - I've
> certainly looked for an answer, but haven't found one that seemed on
> point. I'm considering getting an SBR (w/out SBC), using NAS running
> SC

that's a NAS appliance?

> on an onboard Ubuntu system

how does this relate to the NAS? Or is the NAS box itself running Ubuntu?

> and controlled w/ ipeng on ipod touch to
> feed music stored on the NAS to my stereo without having my computer on.

that should be fine.

> Should I expect any issues setting up SBR on my laptop with Net::UDAP,

That should be fine. You need to connect the SBR via wired ethernet
initially, however, in order to configure it via Net::UDAP. Once
configured, it can be wired or wifi, of course.

> identifying the SBR through SC running on my NAS (connected to SBR by
> ethernet through router) and using ipeng as controller using the
> router's wifi (rather than P2P with the SBR) even when my laptop is
> off?

That should be fine. Note that iPeng connects to SC itself, never to the
SBR, so as long as iPeng can connect to SC on the NAS, via wifi, and SC
can also connect to the SBR - via either wired or wifi - then you should
be fine.

> I assume once my SBR is set up, any devices running SC (such as
> my NAS) will be able to find it, but not sure.

do you really intend to have multiple devices running SC? Normally,
you'd have one, and control it from other PCs, iPeng, SBC, etc.

Having multiple SC instances, even sharing a data backend, just means
extra sets of settings to administer.

cheers,
calum.

loafsta
2009-04-19, 10:59
loafsta wrote:
> I'm definitely a novice and apologize in advance if I'm asking this
> question in the wrong place or if it has been covered elsewhere - I've
> certainly looked for an answer, but haven't found one that seemed on
> point. I'm considering getting an SBR (w/out SBC), using NAS running
> SC

that's a NAS appliance?

> on an onboard Ubuntu system

how does this relate to the NAS? Or is the NAS box itself running Ubuntu?

> and controlled w/ ipeng on ipod touch to
> feed music stored on the NAS to my stereo without having my computer on.

that should be fine.

> Should I expect any issues setting up SBR on my laptop with Net::UDAP,

That should be fine. You need to connect the SBR via wired ethernet
initially, however, in order to configure it via Net::UDAP. Once
configured, it can be wired or wifi, of course.

> identifying the SBR through SC running on my NAS (connected to SBR by
> ethernet through router) and using ipeng as controller using the
> router's wifi (rather than P2P with the SBR) even when my laptop is
> off?

That should be fine. Note that iPeng connects to SC itself, never to the
SBR, so as long as iPeng can connect to SC on the NAS, via wifi, and SC
can also connect to the SBR - via either wired or wifi - then you should
be fine.

> I assume once my SBR is set up, any devices running SC (such as
> my NAS) will be able to find it, but not sure.

do you really intend to have multiple devices running SC? Normally,
you'd have one, and control it from other PCs, iPeng, SBC, etc.

Having multiple SC instances, even sharing a data backend, just means
extra sets of settings to administer.

cheers,
calum.

Thanks for the input, Calum. The NAS does run SC using an onboard Ubuntu system. Sounds like I should be able to make this work if I can just work my way through Net::UDAP - which may be no small feat for me. You are correct that I'm not going to use multiple devices running SC - I was just making the distinction between setting up the SBR through my laptop, then finding the SBR with another networked device (the NAS). No doubt I'll be back here bugging you for pointers when this all goes awry!

cdmackay
2009-04-19, 13:53
loafsta wrote:
> Thanks for the input, Calum. The NAS does run SC using an onboard
> Ubuntu system.

ok, I see.

> Sounds like I should be able to make this work if I can
> just work my way through Net::UDAP - which may be no small feat for me.

It's not too hard, and we can help if you can't get it to work. I've
configured *all* my SBs, including Booms, using Net::UDAP, partly
because it's easier than entering things via the remote, even when that
is possible.

> You are correct that I'm not going to use multiple devices running SC -
> I was just making the distinction between setting up the SBR through my
> laptop, then finding the SBR with another networked device (the NAS).

Ah, ok; there's no connection between the two, so that doesn't matter.
During the configuration, you're just entering some data into the SBR's
non-volatile memory, including pointing it at your SC server (the NAS).

What system you use to initially configure the SBR is irrelevant.

> No doubt I'll be back here bugging you for pointers when this all goes
> awry!

ok :)

cheers,
calum.

jmendez
2009-04-29, 01:20
Hi,
I'm trying to use an SBR w/o the remote. I've discovered SqueeMote and iPeng for the iPhone! I've had success with discovering my SBR using Peter's compiled udap shell and have followed Robin's instructions best I can but the SBR's button remains yellow. Can anyone take a look at my config below and see if I've got it all correct for my application?

bridging: 0 <leave as 0?>
hostname: <"Hostname" from my SqueezeCenter Status page>
interface: 0 <since I'm trying to connect to wireless network>
lan_gateway: <"ADSL Port Gateway IP Address" - Netgear Status>
lan_ip_mode: 1 <for DHCP>
lan_network_address: <"LAN Port IP Address" - Netgear Router Status page>
lan_subnet_mask: <"LAN Port IP Subnet Mask" - Netgear Router Status>
primary_dns: <"Domain Name Server" - Netgear Router Status page>
secondary_dns: <"Domain Name Server" - Netgear Router Status page>
server_address: <"Server IP Address" from SqueezeCenter Status page>
squeezecenter_address: <"Server IP Address" from SqueezeCenter Status page>
squeezecenter_name: <leave blank?>
wireless_SSID: <my SSID has two words but SBR won't allow spaces!!>
wireless_channel: <"Channel" from my Netgear Router Status page>
wireless_keylen: 0 <I'm using WPA-PSK so leave as-is?>
wireless_mode: 0 <not sure what this means>
wireless_region_id: 0 <4 for US right?)
wireless_wep_key_0: <I'm using WPA-PSK so leave this blank, correct?>
wireless_wep_key_1: <I'm using WPA-PSK so leave this blank, correct?>
wireless_wep_key_2: <I'm using WPA-PSK so leave this blank, correct?>
wireless_wep_key_3: <I'm using WPA-PSK so leave this blank, correct?>
wireless_wep_on: 0 <I'm using WPA-PSK so 0, correct?>
wireless_wpa_cipher: 1 <not sure what this means>
wireless_wpa_on: 1 <I'm using WPA-PSK so 1, correct?>
wireless_wpa_mode: 1 <I'm using WPA-PSK so 1, correct?>
wireless_wpa_psk: <just my wpa password right?>

I'm amazing I got as far as talking to the SBR and feel like I'm really close. Any help would be great!
Jason

dsdreamer
2009-04-29, 13:51
bridging: 0
hostname: <you are not forced to set this>
interface: 0
lan_gateway: <don't set if you're using DHCP>
lan_ip_mode: 1 <for DHCP>
lan_network_address: <don't set if you're using DHCP>
lan_subnet_mask: <don't set if you're using DHCP>
primary_dns: <don't set if you're using DHCP>
secondary_dns: <don't set if you're using DHCP>
server_address: <don't set it>
squeezecenter_address: <"Server IP Address" from SqueezeCenter Status page>
squeezecenter_name: <leave blank>
wireless_SSID: <Change your SSID to a single word, just to be safe>
wireless_channel: <Doesn't matter in Infrastructure mode>
wireless_keylen: 0 <Zero is fine>
wireless_mode: 0 <must be zero for Infrastructure mode. i.e., when using an Aceess Point>
wireless_region_id: 4 <for US>
wireless_wep_key_0: <using WPA-PSK so leave this blank, or set to zero>
wireless_wep_key_1: <using WPA-PSK so leave this blank, or set to zero>
wireless_wep_key_2: <using WPA-PSK so leave this blank, or set to zero>
wireless_wep_key_3: <using WPA-PSK so leave this blank, or set to zero>
wireless_wep_on: 0 <using WPA-PSK so 0>
wireless_wpa_cipher: ? <1 is for TKIP, 2 is for AES, 3 is for TKIP + AES>
wireless_wpa_on: 1 <using WPA so 1 is correct>
wireless_wpa_mode: ? <You had 1 here. You could try 2 instead>
wireless_wpa_psk: <just your wpa password, but quotation marks may be needed if multiple words used>


I'm suspecting one problem is getting the SSID to be recognized, since it is two words. Either use quotation marks around the SSID in Net-UDAP (not sure that this works) or change your SSID to a single word, which seems a safer bet.

The fact that you're using a Pre-shared key (PSK) doesn't determine the encryption method (wireless_wpa_cipher) or the flavor of WPA being used (wireless_wpa_mode). You will need to figure this out from your access point or router configuration screens.

You will need to know which cypher is in use (check your access point), and set wireless_wpa_cipher to 1, 2 or 3 accordingly. Generally speaking, TKIP is associated with WPA1, and anything using AES or AES + TKIP is associated with WPA2 and thus you will need to set wireless_wpa_mode to 1 or 2 for WPA1 or WPA2 respectively. (WPA1 is generally known as WPA, since it was once the first and only WPA method.)

Hellsblade
2009-04-30, 13:40
Hi,

I just upgraded the firmware in my squeezebox duet to version 7.3 r5497, but now the Squeezebox duet doesn't seem to recognize my Wireless network.

I've tried resetting the controller and the receiver but I get no further then "try other network".
I have several devices working ok in this Wireless network (notebooks and PDÁ) , but the squeezebox is the only one not working.

When I connect the receiver to the wired network I can get it to work with the NET::udap perl program, but when the interface is set to wireless and I set the parameters necessary parameters (SSID and wpa2 etc) it doesn't work.

Is there any option to overcome this? Or is my remote bricked :-(.

Regards,

Henk Wieland
Amsterdam
The Netherlands

tcutting
2009-04-30, 14:01
Refer to this thread:
http://forums.slimdevices.com/showthread.php?t=62844

It seems they found a problem with this version of the controller firmware.

/quote
There seems to be an unresolved issue with this release. Please revert
back to the previous firmware by unpowering your Controller, then pressing
& holding Vol+ while powering it up again.
/quote

Hellsblade
2009-04-30, 23:59
Hi Thank for pointing this out.
Now i only have to find the SD card restore procedure and a URL to download an older firmware. This really sucks. This is not beta firmware but alpha.
By the way i think the NET::UDAP should be integrated in the Squeezecentre settings webinterface. Great program/script.

Rgrds,
Hellsblade

MikeDC
2009-05-06, 17:05
I ran the udap tool (compiled version). All seemed to go well, but when I typed reset, there was no message returned and the SBR continued to blink as if in init mode. Then the SBR light went off completely (although the unit was still powered).

I've discovered that went the server (a VortexBox in this case) is off, the SBR will show a blue light. But once the server is booted and SqueezeCenter loads, the SBR's light goes completely black again.

dsdreamer
2009-05-06, 17:32
I ran the udap tool (compiled version). All seemed to go well, but when I typed reset, there was no message returned and the SBR continued to blink as if in init mode. Then the SBR light went off completely (although the unit was still powered).

I've discovered that went the server (a VortexBox in this case) is off, the SBR will show a blue light. But once the server is booted and SqueezeCenter loads, the SBR's light goes completely black again.

If when the server comes up, the SBR light goes off, this indicates that the power state of the SBR is "off" which I think should be called "standby." You should be able to find it in the SqueezeCenter web interface and toggle the power mode.

MikeDC
2009-05-07, 11:10
Can someone provide a sample of their UDAP config for an SBR that is in Bridge mode, wired, static IP?

I had this working before I used the UDAP tool to set a static IP, and now I can get Bridged mode to work again.

Thanks for any assistance you can provide.

margolbe
2009-05-07, 17:03
Hi,

I am thinking about buying just the receiver and want to use Net:UDAP to configure.

I am unclear about the following:

# The computer running Net::UDAP and your SBR must be connected to the same wired network, and must be on the same subnet.

I'm not sure I understand. I plan on using this wirelessly. But, in order to configure I must first hook up the receiver to the ethernet connection on my router? Once its configured, I then move my receiver back to my audio system? Is this correct?

# This network must be connected to the first network interface on the computer, in order for SBR discovery to work. If your SBR is on a network interface other than the first you must either move it, or configure down any preceding network interfaces, until it is so assigned. Otherwise the discover command will not find your SBR [this is tracked in Ticket #6; now fixed in the trunk].

How do you identify the first network?

Thanks,

Bruce

dsdreamer
2009-05-07, 17:28
Hi,

# The computer running Net::UDAP and your SBR must be connected to the same wired network, and must be on the same subnet.

I'm not sure I understand. I plan on using this wirelessly. But, in order to configure I must first hook up the receiver to the ethernet connection on my router? Once its configured, I then move my receiver back to my audio system? Is this correct?


Correct in every particular. It is really hard for the wireless connection to be used since the connection needs to be configured (especially as regards encryption) before the SBR can be reached wirelessly. This is classic bootstrap problem.



How do you identify the first network?

The only safe way is to have only one network connection active. Linux users may be able to get a clue from the network device names, like eth0, eth1 etc. I would take the safe approach, i.e., make sure to have only one network adapter enabled and have that connected to your wired router port. In Windows, you could use the device manager to disable the other adapters for the duration of the configuration. If you have both wired and wireless adapters, disable the wireless one and you should be good to go.

cdmackay
2009-05-15, 18:04
margolbe wrote:
> # This network must be connected to the first network interface on the
> computer, in order for SBR discovery to work. If your SBR is on a
> network interface other than the first you must either move it, or
> configure down any preceding network interfaces, until it is so
> assigned. Otherwise the discover command will not find your SBR [this is
> tracked in Ticket #6; now fixed in the trunk].
>
> How do you identify the first network?

apologies; that was my comment you're quoting above. As noted, on UNIX
systems the interfaces are presented in an ordered way, so it's easy to
see which is the first.

But the fix is to download and try the trunk version, which checks all
interfaces; thanks to Robin for fixing this, the instant I reported it :)

cheers,
c.

sderuiter
2009-05-20, 13:43
@Peter

I'm not sure how to add WEP key using your udap_shell_1_0_0.exe.
On Net-UDAP site:
http://projects.robinbowes.com/Net-UDAP/trac#January212009
I can read:
"I just committed a change that switches to hex entry for WEP keys. This simply means that instead of entering a hex key like this: abcd, you should now enter it like this: 61626364."

How to add WEP key using this exe (hex or plain text)?

Hi, I have the same issue. My WEP key is in HEX, which leads to a yellow button. The SBR does work over wired, it has the latest firmware downloaded.

But how should I convert my 10digit HEX key to ASCII?

I haven't found a reference that translates above "abcd" into "61626364", maybe this is just an example.

Any help appreciated. I'm so close...

Siduhe
2009-05-20, 14:06
But how should I convert my 10digit HEX key to ASCII?


http://www.dolcevie.com/js/converter.html

sderuiter
2009-05-20, 14:11
http://www.dolcevie.com/js/converter.html

Thanks, but if I type in my HEX key, I get:

!q?p~

as output. Surely that isn't right?

Siduhe
2009-05-20, 14:14
Try this one - will work both ways...

http://centricle.com/tools/ascii-hex/

sderuiter
2009-05-20, 14:18
Try this one - will work both ways...

http://centricle.com/tools/ascii-hex/

Color me stupid, but it doesn't work.

It does't matter if I put colons (:) in between.

Any hints?

I've also tried to convert my key using http://www.ascii.cl/conversion.htm, but that led to nowhere.

THank you

Siduhe
2009-05-20, 14:35
PM me your hex key.

sderuiter
2009-05-20, 14:47
PM me your hex key.

Done. Thanks for your help.

Robin Bowes
2009-05-20, 16:55
sderuiter wrote:
> mirhon;405516 Wrote:
>> @Peter
>>
>> I'm not sure how to add WEP key using your udap_shell_1_0_0.exe.
>> On Net-UDAP site:
>> http://projects.robinbowes.com/Net-UDAP/trac#January212009
>> I can read:
>> "I just committed a change that switches to hex entry for WEP keys.
>> This simply means that instead of entering a hex key like this: abcd,
>> you should now enter it like this: 61626364."
>>
>> How to add WEP key using this exe (hex or plain text)?
>
> Hi, I have the same issue. My WEP key is in HEX, which leads to a
> yellow button. The SBR does work over wired, it has the latest firmware
> downloaded.
>
> But how should I convert my 10digit HEX key to ASCII?
>
> I haven't found a reference that translates above "abcd" into
> "61626364", maybe this is just an example.

As Siduhe has pointed out, there are several on-line tools that can
convert from ascii to hex and vice versa.

What you need to do is:

1. Take your hex key, e.g. '61626364' and convert it to ascii. This will
result in something like 'abcd'
2. Use the resulting ascii string to set the WEP key

You will run into problems if you have used hex results in non-printable
ascii characters. You could get round that by choosing a nice ascii
password, converting to hex, storing the WEP key in your WAP, then using
the original ascii to set the WEP key on your SBR.

Of course, the best way to fix this would be to upgrade to the latest
version of Net-UDAP which accepts WEP key entry in hex.

R.

sderuiter
2009-05-20, 23:33
sderuiter wrote:[color=blue]

Of course, the best way to fix this would be to upgrade to the latest
version of Net-UDAP which accepts WEP key entry in hex.

R.

Hi Robin,

That's what I tried at first. I downloaded and unzipped the files on my ReadyNAS NV, however, I was unable to run the program at all (perl 5.8.8 is installed). I'm no expert in perl or Unix permissions to get a program to run, but I suspect it's something trivial.

I've copied all files to a subdir under /usr/bin.
When I run the command from your wiki, the following output greets me:


Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0# scripts/udap_shell.pl
-bash: scripts/udap_shell.pl: Permission denied
Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0#


If I cd to the scripts directory, I get:


Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0/scripts# udap_shell.pl
-bash: udap_shell.pl: command not found
Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0/scripts#


Edit:

Silly me. Running "perl udap_shell.pl" runs the udap shell! Hooray, I'm in!
However, still the button stays at yellow.
I've entered my HEX key as 10 digits, without the (:). Is that how it's supposed to be done?



Your help is appreciated.

Robin Bowes
2009-05-22, 12:03
sderuiter wrote:
> I've copied all files to a subdir under /usr/bin.
> When I run the command from your wiki, the following output greets me:

Which wiki page are you following?

>
> Code:
> --------------------
>
> Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0# scripts/udap_shell.pl
> -bash: scripts/udap_shell.pl: Permission denied
> Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0#
>
> --------------------

That's because the script hasn't got the executable bit set.

Either use:

Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0# perl scripts/udap_shell.pl

or:

Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0# chmod +x scripts/udap_shell.pl
Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0# scripts/udap_shell.pl

>
>
> If I cd to the scripts directory, I get:
>
> Code:
> --------------------
>
> Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0/scripts# udap_shell.pl
> -bash: udap_shell.pl: command not found
> Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0/scripts#
>
> --------------------

That's because on unix/linux, unlike DOS/Windows, the current directory
is not in the command path.

To run a command in the current directory, use:

Nemo:/usr/bin/ndap/tags/RELEASE_1.0.0/scripts# ./udap_shell.pl

>
> I seem to be unable to run any perl script.

Nope, you are obviously just new to linux/unix. There's a bit of a
learning curve!

R.

cira
2009-06-06, 10:53
I bought a classic which i assumed (based on what I read) would be expandable via receivers.

I now am in the situation where I have a working classic and a receiver that I can do nothing with.

I'm attempting to use the UDAP tool as well as the .exe Peter compiled, but I'm stuck at one point

"•Type set server_address=192.168.1.50 squeezecenter_address=192.168.1.50 wireless_SSID=3Com wireless_wep_key_0=abcde wireless_wep_on=1
◦(substitute the correct wireless values for your network, and the correct IP address of your Squeezecenter) "

I have no need to go wireless since I have ethernet in my room. How do i tell it to look for the wired connection? Beyond that how do you find the IP of your squeeze center?

thanks for any help!

cira
2009-06-06, 11:43
in other words, i feel like ihave no idea what i'm doing, haha

robinbowes
2009-06-06, 12:18
Cira,

I suggest you look at the Sample Usage page:

https://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage

To find the adddress of your squeezecenter:

goto the web interface
Click "settings" (bottom right)
Click the "Information" tab
Server IP Address is the third line down.

If you have DHCP on your wired network, something like this should work:

discover
conf 1
set interface=1 lan_ip_mode=1 squeezecenter_address=a.b.c.d
save_data
reset

where a.b.c.d is the Server IP Address you looked up earlier.

R.

jackamo
2009-06-16, 07:56
Hi!

I'm absolute beginner in all this stuff together with very poor english.

So my Q are:
1. what should I do if my wireless network is without WEP and WPA - MAC adress filtering only?
2. where I can find wireless_region_id=? I'm from Europe and having D-Link DI-524 wifi router.

Robin Bowes
2009-06-16, 08:32
jackamo wrote:
> Hi!
>
> I'm absolute beginner in all this stuff together with very poor
> english.
>
> So my Q are:
> 1. what should I do if my wireless network is without WEP and WPA - MAC
> adress filtering only?

Don't enable WEP or WPA:

set wireless_wep_on=0 wireless_wpa_on=0

> 2. where I can find wireless_region_id=? I'm from Europe and having
> D-Link DI-524 wifi router.


The regions are:

wireless_region_id: 4 - US, 6 - CA, 7 - AU, 13 - FR, 14 - EU, 16 - JP,
21 - TW, 23 - CH

You can find all this information by running the udap_shell.pl script
and typing "fields".

R.

jackamo
2009-06-17, 00:21
OK! Thank you!

What are functions I miss if I choose only Receiver without Controller? Is there smth I can do with Controller and can't in SqueezeCenter?

Robin Bowes
2009-06-17, 00:45
jackamo wrote:
> OK! Thank you!
>
> What are functions I miss if I choose only Receiver without Controller?
> Is there smth I can do with Controller and can't in SqueezeCenter?

I don't believe the SBR can do more without the SBC, but I suggest you
post that as another question in a separate thread - you'll likely get a
more considered response.

R.

cira
2009-06-21, 10:59
Cira,

I suggest you look at the Sample Usage page:

https://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage

To find the adddress of your squeezecenter:

goto the web interface
Click "settings" (bottom right)
Click the "Information" tab
Server IP Address is the third line down.

If you have DHCP on your wired network, something like this should work:

discover
conf 1
set interface=1 lan_ip_mode=1 squeezecenter_address=a.b.c.d
save_data
reset

where a.b.c.d is the Server IP Address you looked up earlier.

R.


THANKYOU! Thankyou for your help, thankyou for creating the workaround... thanks!

hase
2009-07-07, 10:45
hi there,

i got a SBR today, and tried setting it up with the net::udap tool, unfortunately i was not very successful :(. the perl script seems to be running ok, but the 'discover' command does not find the SBR. i'm using

- ubuntu 9.04
- netgear wgr614v2 router with only 2 devices connected (pc and the SBR)
- the SBR is blinking red (slow)
- there are no blocked ports/services in the router
- the SBR does not show up under the 'attached devices' section of the router

does anyone have an idea why it's not working? i'm absolutely out of ideas.

thanks!
robert

Robin Bowes
2009-07-07, 11:31
hase wrote:
> hi there,
>
> i got a SBR today, and tried setting it up with the net::udap tool,
> unfortunately i was not very successful :(. the perl script seems to be
> running ok, but the 'discover' command does not find the SBR. i'm using
>
> - ubuntu 9.04
> - netgear wgr614v2 router with only 2 devices connected (pc and the
> SBR)
> - the SBR is blinking red (slow)
> - there are no blocked ports/services in the router
> - the SBR does not show up under the 'attached devices' section of the
> router
>
> does anyone have an idea why it's not working? i'm absolutely out of
> ideas.

Can you please take this to the Net::UDAP list:

http://lists.projects.robinbowes.com/mailman/listinfo/net-udap

Thanks,

R.

daviseh
2009-08-03, 21:18
I am having a problem figuring this out. I have a wired setup with the following specs

IP Address = 192.168.0.105
Gateway = 192.168.0.1
Squeezecenter address=192.168.105

So I reset the SBR and entered the following:

discover
conf 1
set interface=0 lan_ip_mode=0 lan_gateway=192.168.0.1 lan_network_address=?????? lan_subnet_mask=255.255.255.0 primary_dns=192.168.0.1 squeezecenter_address=192.168.0.105
save_data
reset

I assumed that the lan_network_address became the static IP. Is this correct? If not, how do you assign a static IP address?

Thanks for the help.

Robin Bowes
2009-08-04, 02:49
On 04/08/09 05:18, daviseh wrote:
> I am having a problem figuring this out. I have a wired setup with the
> following specs
>
> IP Address = 192.168.0.105
> Gateway = 192.168.0.1
> Squeezecenter address=192.168.105
>
> So I reset the SBR and entered the following:
>
> discover
> conf 1
> set interface=0 lan_ip_mode=0 lan_gateway=192.168.0.1
> lan_network_address=?????? lan_subnet_mask=255.255.255.0
> primary_dns=192.168.0.1 squeezecenter_address=192.168.0.105
> save_data
> reset
>
> I assumed that the lan_network_address became the static IP. Is this
> correct? If not, how do you assign a static IP address?

According to the docs, interface=0 means wireless; try interface=1

R.

daviseh
2009-08-04, 12:34
On 04/08/09 05:18, daviseh wrote:
> I am having a problem figuring this out. I have a wired setup with the
> following specs
>
> IP Address = 192.168.0.105
> Gateway = 192.168.0.1
> Squeezecenter address=192.168.105
>
> So I reset the SBR and entered the following:
>
> discover
> conf 1
> set interface=0 lan_ip_mode=0 lan_gateway=192.168.0.1
> lan_network_address=?????? lan_subnet_mask=255.255.255.0
> primary_dns=192.168.0.1 squeezecenter_address=192.168.0.105
> save_data
> reset
>
> I assumed that the lan_network_address became the static IP. Is this
> correct? If not, how do you assign a static IP address?

According to the docs, interface=0 means wireless; try interface=1

R.

Thanks Robin. I changed interface from 0 to 1 and I was able to use iPeng to connect to Squeezenetwork.

When I log into squeezenetwork the player is there. However, squeezecenter does not find the player and I can not connect to squeezecneter from iPeng. So I guess I still have some settings wrong.

Any ideas?

Ed

Robin Bowes
2009-08-06, 03:11
On 04/08/09 20:34, daviseh wrote:
>
> Thanks Robin. I changed interface from 0 to 1 and I was able to use
> iPeng to connect to Squeezenetwork.
>
> When I log into squeezenetwork the player is there. However,
> squeezecenter does not find the player and I can not connect to
> squeezecneter from iPeng. So I guess I still have some settings wrong.

This is the example I give on the wiki [1] for a wired, static connection:

discover
conf 1
set interface=1 lan_ip_mode=0 lan_gateway=192.168.3.1
lan_network_address=192.168.3.10 lan_subnet_mask=255.255.255.0
primary_dns=192.168.3.1 squeezecenter_address=192.168.1.150
save_data
reset

If this doesn't work [2], then you have some other network issue -
firewall on the squeezecenter server, perhaps?

R.

[1] https://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage

[2] change the IP values to match your own network

daviseh
2009-08-07, 06:25
On 04/08/09 20:34, daviseh wrote:
>
> Thanks Robin. I changed interface from 0 to 1 and I was able to use
> iPeng to connect to Squeezenetwork.
>
> When I log into squeezenetwork the player is there. However,
> squeezecenter does not find the player and I can not connect to
> squeezecneter from iPeng. So I guess I still have some settings wrong.

This is the example I give on the wiki [1] for a wired, static connection:

discover
conf 1
set interface=1 lan_ip_mode=0 lan_gateway=192.168.3.1
lan_network_address=192.168.3.10 lan_subnet_mask=255.255.255.0
primary_dns=192.168.3.1 squeezecenter_address=192.168.1.150
save_data
reset

If this doesn't work [2], then you have some other network issue -
firewall on the squeezecenter server, perhaps?

R.

[1] https://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage

[2] change the IP values to match your own network

THanks Robin - One last question. I am not sure about the lan_network_address. If the address of the NIC card in my desktop is 192.168.0.100 per ipconfig and squeezecenter settings gives me that address as the server where do you find the lan_network_address. I assumed that was the static address I am assigning to the SBR.

I turned off the firewall but I keep losing the SBR. Squeezecenter finds it but ipeng and squeemote do not. Also, I can't switch to squeezenetwork and get a pin. I have gone from DHCP to static and back numerous times but can't seem to get it right.

I have read and re-read these threads but am clueless!

Steven_Foers
2009-08-14, 13:36
Hi

I'm trying to get my intel iMac running 10.5.7 to 'see' my squeezebox duet.

I've connected both Mac and SB to my BT router via cable.

I've run the udap_shell.pl (had to chmod it to 777 first) in Terminal but 'discover' gets no response at all.

I've used the windows compiled version in XP (under Parallels) and get:

info: ***Broadcasting adv_discovery message to MAC address 00:00:00:00:00:00 on 255.255.255.255

When I try 'list' I get the headings but no results.

I've ensured the mac and windows firewalls are off (router firewall is on).

the SB is sitting here slowly flashing red.

I can see a wireless network called logitech+squeezebox+0004201744D4

If anyone can offer a suggestion as to what I need to do (simple terms please, I'm on my limits with this - I'm not a Terminal user) I would really appreciate it ( please:) )

Thanks

Steven

Robin Bowes
2009-08-15, 03:53
On 07/08/09 14:25, daviseh wrote:

> THanks Robin - One last question. I am not sure about the
> lan_network_address. If the address of the NIC card in my desktop is
> 192.168.0.100 per ipconfig and squeezecenter settings gives me that
> address as the server where do you find the lan_network_address. I
> assumed that was the static address I am assigning to the SBR.

It is - you choose the address. If your desktop has address
192.168.0.100, then try using 192.168.0.101.

> I turned off the firewall but I keep losing the SBR. Squeezecenter
> finds it but ipeng and squeemote do not. Also, I can't switch to
> squeezenetwork and get a pin. I have gone from DHCP to static and back
> numerous times but can't seem to get it right.

If you've getting a connection to the server, then you've set up the SBR
OK. I'm not sure why you're having problems with the other things.

R.

karibe
2009-08-17, 02:37
I'm trying to configure by SBR by NET::UDAP script but without luck

The most strange thing is that when I'm typing discover, I'm getting:



UDAP> discover
info: <<< Broadcasting adv_discovery message to MAC address 00:00:00:00:00:00 on 255.255.255.255
info: >>> adv_discovery response received from 88:04:88:04:88:04
info: <<< Broadcasting get_ip message to MAC address 88:04:88:04:88:04 on 255.255.255.255
info: >>> get_ip response received from 88:04:88:04:88:04
info: <<< Broadcasting get_data message to MAC address 88:04:88:04:88:04 on 255.255.255.255
info: >>> get_data response received from 88:04:88:04:88:04
UDAP> list
# MAC Address Type Status
== ================= ========== ===============
1 88:04:88:04:88:04 squeezebox wait_slimserver



as You see MAC address is completely different than on the bottom of unit 00:04:20...

when I type configure 1 list



UDAP> configure 1
UDAP [1] (squeezebox 048804)> list
bridging: 0
hostname: ����������������
interface: 0
lan_gateway: 205.0.205.0
lan_ip_mode: 0
lan_network_address: 141.0.141.0
lan_subnet_mask: 205.0.205.0
primary_dns: 205.0.205.0
secondary_dns: 141.0.141.0
server_address: 205.0.205.0
squeezecenter_address: 205.0.205.0
squeezecenter_name: ����������������
wireless_SSID: ����������������
wireless_channel: 0
wireless_keylen: 0
wireless_mode: 141
wireless_region_id: 0
wireless_wep_key_0: 00cd00cd00cd00cd00cd00cd00
wireless_wep_key_1: 8d008d008d008d008d008d008d
wireless_wep_key_2: 00cd00cd00cd00cd00cd00cd00
wireless_wep_key_3: cd00cd00cd00cd00cd00cd00cd
wireless_wep_on: 0
wireless_wpa_cipher: 205
wireless_wpa_mode: 0
wireless_wpa_on: 205
wireless_wpa_psk: �������������������������������



this options are completely insane and after reset

Is my unit broken ?

robinbowes
2009-08-17, 03:01
karibe,

It certainly shouldn't be returning a different MAC addresses every time.

Did you try a factory reset?

http://wiki.slimdevices.com/index.php/Hardware_Reset_commands#Squeezebox_Receiver

R.

karibe
2009-08-17, 04:20
karibe,

It certainly shouldn't be returning a different MAC addresses every time.

Did you try a factory reset?

http://wiki.slimdevices.com/index.php/Hardware_Reset_commands#Squeezebox_Receiver

R.

Yes many times, and LED blinking fast so reset was successful
And after that same situation, some strange MAC I try it at home and in work and effect is same

rwwebb
2009-08-17, 04:24
Hello,

I am trying to set up the Squeezebox Receiver without the need for a controller and having a nightmare. To do this I have done the following;
1. Wire connected my SBR to my Belkin Wireless Router which also is connected to my desktop
2. Turned off the McAfee firewall protection. This is the only way that I can use netUDAP. When the firewall is on, it cannot do the discovery step.
3. Squeezecenter is running on my desktop (192.168.2.2) and iPeng is accessing this server with no problems.
4. When I perform the discovery command using netUDAP, the SBR is found and I configure is as follows;

UDAP [1] (squeezebox 174401)> list
bridging: 0
hostname:
interface: 0
lan_gateway: 192.168.2.1
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0
server_address: 192.168.2.2
squeezecenter_address: 192.168.2.2
squeezecenter_name:
wireless_SSID: 48aGeldeston
wireless_channel: 11
wireless_keylen: 0
wireless_mode: 0
wireless_region_id: 14
wireless_wep_key_0:
wireless_wep_key_1:
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 0
wireless_wpa_cipher: 1
wireless_wpa_mode: 2
wireless_wpa_on: 1
wireless_wpa_psk: <My Password>

UDAP [1] (squeezebox 174401)>

5. When I use the save_data and reset commands, everything looks fine but the light on the SBR is yellow.
6. I then unplug the SBR from the router, expecting it to be picked up by the wireless network but nothing happens.
7. I have also opened ports 17784 and 9000 to allow the UDP access to work.

Any help with this would be much appreciated.

Rich

karibe
2009-08-17, 04:33
karibe,

It certainly shouldn't be returning a different MAC addresses every time.

Did you try a factory reset?

http://wiki.slimdevices.com/index.php/Hardware_Reset_commands#Squeezebox_Receiver

R.
Yes I did many times

karibe
2009-08-17, 04:35
karibe,

It certainly shouldn't be returning a different MAC addresses every time.

Did you try a factory reset?

http://wiki.slimdevices.com/index.php/Hardware_Reset_commands#Squeezebox_Receiver

R.

Yes i did, many times

karibe
2009-08-17, 04:36
Yes I did many times...

robinbowes
2009-08-17, 04:38
Rich,

"Yellow" means your SBR is not connecting to your wireless network correctly.

Try connecting wired, to make sure everything else is setup OK:

discover
conf 1
set interface=1 lan_ip_mode=1 squeezecenter_address=192.168.2.2
save_data
reset

If that works, you need to review your wireless settings and make sure they're correct.

You might find the examples [1] useful. In particular, the WPA2 with TKIP+AES one [2].

R.

[1] https://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage
[2] https://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage#WirelessWPA2TKIPAESDHCP

robinbowes
2009-08-17, 05:32
Yes I did many times...

In that case, it may be that your SBR is faulty.

You might like to try calling Logitech support, although you may find that they only offer offical support if you have the Controller as well.

R.

rwwebb
2009-08-17, 05:37
Robin,

I made the changes to wired as follows;

set interface=1 lan_ip_mode=1 squeezecenter_address=192.168.2.2

and it worked. The light goes green and then a light violet? I was able to see the device from SqueezeCenter until I inadvertantly removed it using iPeng.

Having had that success, I tried the following;

set
interface=0
wireless_mode=0
wireless_region_id=14
wireless_SSID=48aGeldeston
wireless_wpa_on=1
wireless_wpa_mode=2
wireless_wpa_cipher=3
wireless_wpa_psk="myPassword"
lan_ip_mode=1
squeezecenter_address=192.168.2.2

and it didn't work. With regards my network, I am running a Belkin Wireless G Plus router, using WPA2 and TKIP as the encryption.

As an aside, for your utility to work, do I need to reset the device everytime? So far, it has been the only way I can find it.

I also need to shut down my firewall when I do the setup, even though I have opened the necessary ports. Is this common?

I really appreciate the input.

Rich

robinbowes
2009-08-17, 06:12
Robin,

I made the changes to wired as follows;

set interface=1 lan_ip_mode=1 squeezecenter_address=192.168.2.2

and it worked. The light goes green and then a light violet? I was able to see the device from SqueezeCenter until I inadvertantly removed it using iPeng.

Having had that success, I tried the following;

set
interface=0
wireless_mode=0
wireless_region_id=14
wireless_SSID=48aGeldeston
wireless_wpa_on=1
wireless_wpa_mode=2
wireless_wpa_cipher=3
wireless_wpa_psk="myPassword"
lan_ip_mode=1
squeezecenter_address=192.168.2.2

and it didn't work. With regards my network, I am running a Belkin Wireless G Plus router, using WPA2 and TKIP as the encryption.


Rich,

I'm using pretty much the same config on my network:

bridging: 0
hostname: Squeezebox
interface: 0
lan_gateway: 192.168.2.1
lan_ip_mode: 1
lan_network_address: 192.168.2.138
lan_subnet_mask: 255.255.255.0
primary_dns: 192.168.2.1
secondary_dns: 0.0.0.0
server_address: 0.0.0.0
squeezecenter_address: 192.168.1.150
squeezecenter_name: ��
wireless_SSID: wrt54gl01
wireless_channel: 6
wireless_keylen: 1
wireless_mode: 0
wireless_region_id: 14
wireless_wep_key_0: 00000000000000000000000000
wireless_wep_key_1: 00000000000000000000000000
wireless_wep_key_2: 00000000000000000000000000
wireless_wep_key_3: 00000000000000000000000000
wireless_wep_on: 0
wireless_wpa_cipher: 3
wireless_wpa_mode: 2
wireless_wpa_on: 1
wireless_wpa_psk: sekrit

The only difference is that I use TKIP+AES.

I switched my WAP to use TKIP and re-configured a SBR with wireless_wpa_cipher=1 and it connected fine.

So, I'm not sure what's happening in your case. Are you sure the key is correct?


As an aside, for your utility to work, do I need to reset the device everytime? So far, it has been the only way I can find it.


No, if you press the button until the light flashes red then release you should be able to discover the device and see the current configuration.


I also need to shut down my firewall when I do the setup, even though I have opened the necessary ports. Is this common?

You can't have the necessary hole in the firewall. Net-UDAP requirements are:

* port 17784 (UDP) open
* UDP broadcast traffic permitted


I really appreciate the input.

Rich


You're rich, eh?

https://projects.robinbowes.com/Net-UDAP/trac#Donations

Oh, how I laugh at my terrible puns!

R.

rwwebb
2009-08-17, 08:41
Sorted with the following configuration;

UDAP [1] (squeezebox 174401)> list
bridging: 0
hostname: LivingRoomSB
interface: 0
lan_gateway: 0.0.0.0
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0
server_address: 192.168.2.2
squeezecenter_address: 192.168.2.2
squeezecenter_name:
wireless_SSID: 48aGeldeston
wireless_channel: 11
wireless_keylen: 0
wireless_mode: 0
wireless_region_id: 14
wireless_wep_key_0:
wireless_wep_key_1:
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 0
wireless_wpa_cipher: 3
wireless_wpa_mode: 1
wireless_wpa_on: 1
wireless_wpa_psk: <My Password>

I removed the default gateway setting and set the wireless_wpa_mode to 1 even though the router explicitly states that it is WPA2.

Thanks for all your help. It is a great utility that you have set up. From reading the posts, it is a surprise that Logitech do not provide this themselves.

MillmoorRon
2009-08-17, 10:32
Is this just for the initial setup so that you can set network stuff, then Squeezecenter is used normally for other options?

karibe
2009-08-18, 00:14
In that case, it may be that your SBR is faulty.

You might like to try calling Logitech support, although you may find that they only offer offical support if you have the Controller as well.

R.

I'm afraid I have to care myself.
Two last ideas:
1.I'll try to configure it by simple ethernet switch ( not by linksys wrt54G v.6 router with ddwrt software as previously )
2. Maybe direct connection through CAT5 crossed cable will be solution

ggoodwin
2009-08-18, 07:25
I've been stuggling with getting a new SBR working using the UDAP exe all day.

Tried wired and wireless
Light turns blue
SBR has an IP from DHCP (seen in SBR config and DHCP server)
SBR does not respond to ping though
also tried static ip and dhcp reservation with same results

Eventually I saw rwwebb's post and tried pasting his wireless config with just my personalisations and bingo it connects to the wireless network and sc! exactly what I wanted.

The only thing I can see being different from what I had been doing is forcibly /applying all the commands/options even when they are already set/default to the correct setting.

thoughts?

GarryG
a happy man with SB3 (LOUNGE), BOOM (KITCHEN) and SBR (GARDEN)

Robin Bowes
2009-08-19, 01:35
On 17/08/09 18:32, MillmoorRon wrote:
>
> Is this just for the initial setup so that you can set network stuff,
> then Squeezecenter is used normally for other options?

That's correct.

R.

Robin Bowes
2009-08-19, 01:40
On 18/08/09 08:14, karibe wrote:
>
> robinbowes;449118 Wrote:
>> In that case, it may be that your SBR is faulty.
>>
>> You might like to try calling Logitech support, although you may find
>> that they only offer offical support if you have the Controller as
>> well.
>>
>> R.
>
> I'm afraid I have to care myself.
> Two last ideas:
> 1.I'll try to configure it by simple ethernet switch ( not by linksys
> wrt54G v.6 router with ddwrt software as previously )
> 2. Maybe direct connection through CAT5 crossed cable will be solution

Karibe,

If you have both the computer running Net-UDAP and the SBR plugged into
the normal switch ports of the WRT54G then it should be fine. I use a
similar router (actually, a WRT54GS and a WRT54GL) with dd-wrt.

It certainly sounds like your unit is faulty.

R.

Robin Bowes
2009-08-19, 01:45
On 18/08/09 15:25, ggoodwin wrote:
>
> I've been stuggling with getting a new SBR working using the UDAP exe
> all day.
>
> Tried wired and wireless
> Light turns blue
> SBR has an IP from DHCP (seen in SBR config and DHCP server)
> SBR does not respond to ping though
> also tried static ip and dhcp reservation with same results
>
> Eventually I saw rwwebb's post and tried pasting his wireless config
> with just my personalisations and bingo it connects to the wireless
> network and sc! exactly what I wanted.
>
> The only thing I can see being different from what I had been doing is
> forcibly /applying all the commands/options even when they are already
> set/default to the correct setting.
>
> thoughts?

What "set" command were you using originally?

And what was the one that worked?

R.

karibe
2009-08-19, 01:46
On 18/08/09 08:14, karibe wrote:[color=blue]
Karibe,

If you have both the computer running Net-UDAP and the SBR plugged into
the normal switch ports of the WRT54G then it should be fine. I use a
similar router (actually, a WRT54GS and a WRT54GL) with dd-wrt.

It certainly sounds like your unit is faulty.

R.

I've just call logitech support and even reset procedure is strange in my case. When I press button for 6s it blinking fast in red then slowly in red and next I have purple for a second then randomly yellow or green or blue then again red and so on...
It must be broken :(

grego.speiser
2009-08-24, 12:58
I have a squeezebox classic whose display stopped working last week. It played music fine.

I called tech support, they had me do a factory reset (holding down '+' on remote) which did not fix anything. Unfortunately, the unit is no longer connected to my server. I've tried connecting it blind--following steps from other posts and looking at the display from by boom--but I can't get it reconnected.

Would Robin's app be useful here?

Greg

Robin Bowes
2009-08-24, 14:43
On 24/08/09 20:58, grego.speiser wrote:
>
> I have a squeezebox classic whose display stopped working last week. It
> played music fine.
>
> I called tech support, they had me do a factory reset (holding down '+'
> on remote) which did not fix anything. Unfortunately, the unit is no
> longer connected to my server. I've tried connecting it
> blind--following steps from other posts and looking at the display from
> by boom--but I can't get it reconnected.
>
> Would Robin's app be useful here?

Yes, it may be.

If you do a factory reset again, then try a discovery using Net-UDAP, it
should find your classic. You should then be able to configure it, and
have it working again.

Good luck!

R.

strocky
2009-08-31, 11:47
Many thanks to Robin & Peter

Currently the proud owner of a Duet installed & configured via my PC and now Squeezecentre controlled via a Nokia 770 Internet tablet (and a SB Boom)

Although the install instructions look daunting, with a bit of patience, you can easily set up the Duet Receiver without the need for a Ģ130 controller

1) Forget downloading PERL & the script - Use peter's link -:

http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe

2) Read the pre-requisites

http://projects.robinbowes.com/Net-UDAP/trac/wiki/GettingStarted

3) Run the program d/l in Step 1

4) Type "list" (in command box)

5) Type "configure 1"

6) Type "list"

7) Type the command to configure the duet to suit your router setup

example "set interface=0 wireless_mode=0 wireless_region_id=14 wireless_SSID=MySSID wireless_wep_on=1 wireless_keylen=0 wireless_wep_key_0=1a2b3c4d5e lan_ip_mode=1 squeezecenter_address=192.168.1.150"

Interface=0 is Wireless, 1 = Wired
Wireless Region=14 (Europe) (USA=1)
SSID= The name of your wireless network
Wireless Wep on = 1 (means your using a password on your wireless network)
Wireless_wep_key = You wireless network password in ASCII (Letters)
set interface=0 wireless_mode=0 wireless_region_id=14 wireless_SSID=MySSID wireless_wep_on=1 wireless_keylen=0 wireless_wep_key_0=1a2b3c4d5e lan_ip_mode=1 squeezecenter_address=192.168.1.150 or whatever IP address you want for the squeezecentre to display on your PC/Iphone/PDA

Couple of notes -:

If you wireless password is displayed as hex, use this link to convert
http://www.dolcevie.com/js/converter.html

If your using WPA-PSK(TKIP) security use WPA 1 example

eg "set wireless_SSID=MySSID wireless_mode=0 wireless_region_id=14 wireless_wpa_on=1 wireless_wpa_mode=1 wireless_wpa_psk="Top Secret!"

Make sure your using the same DHCP range i.e. 192.168.0.??? or 192.168.1.???



More examples here -:

https://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage

TKSQB
2009-09-07, 02:31
hello, I bourght a 2nd squeezebox receiver. The firts is configured with udap_shell and I use my HP PDA. Everything works well. Now I tried to configure the 2nd one. The night was short but it donīt works the receiver goes to blue but donīt find the server. The greatest problem for me i to edit the configuration again and again via udap_shell. Is it possible to configure with a configuration-file witch I can modify and save to load it new? If yes, where must I save the file, which extension must the file have and can I use a simple Editor? I use udap_shel for windows.
regards and thanks for help

Robin Bowes
2009-09-07, 02:41
On 07/09/09 10:31, TKSQB wrote:
>
> hello, I bourght a 2nd squeezebox receiver. The firts is configured with
> udap_shell and I use my HP PDA. Everything works well. Now I tried to
> configure the 2nd one. The night was short but it donīt works the
> receiver goes to blue but donīt find the server.

http://wiki.slimdevices.com/index.php/SBRFrontButtonAndLED

"BLUE": Waiting to connect to SqueezeCenter or SqueezeNetwork

That suggest you have not specified the server address correctly, or the
server is firewalled.

> The greatest problem
> for me i to edit the configuration again and again via udap_shell. Is it
> possible to configure with a configuration-file witch I can modify and
> save to load it new? If yes, where must I save the file, which extension
> must the file have and can I use a simple Editor? I use udap_shel for
> windows.
> regards and thanks for help

No, you can't do that.

However, two things that might help.

1. Press and hold the button until the light flashes red slowly, and
release it before it begins flashing red quickly. This puts the SBR in
config mode and enables Net-UDAP to discover it and retrieve the current
settings.

2. udap_shell should have a command history - press cursor up to scroll
back through previous commands. Perhaps this doesn't work on Windows?

R.

TKSQB
2009-09-07, 03:42
thanks for Your answer. (sorry for my bad english, but it seems that there are more user on the english-side!?)
Itīs to get silly, my box hangs the most time after config with status yellow, so that have to do the whole same procedure.
My conf on the router for Wlan=
SSID=TiT4
WPA+WPA2 (fritz7110)= 11111111111111111111111111111111111

Squeeze-box:
briding:0
interface=0
lan_gateway:192.168.0.1 (itīs my router)
lan_ip_mode=0
lan_network_address:192.168.0.8
lan_subnet_mask:255.255.55.0
server_address:192.168.0.4 (itīs my flac-file-server)
wireless_SSID:TiT4
wireless_channel:3 (itīs my conf. wlan-channel on router)
wireless_region_id:14 (german)
wireless_wpa_cipher:3
wireless_wpa_on:1
wireless_wpa_psk:111111111111111111111111111111111 11

regards

htrd
2009-09-07, 14:00
the receiver goes to blue but donīt find the server.

I had a similar problem, described in the thread at http://forums.slimdevices.com/showthread.php?t=66823.

In my case it made a difference if I set a value for lan_network_address, even though I was (successfully!) using dhcp and that value should have been ignored!

Its not very scientific, but maybe try setting dummy values for any of the settings which still contain the factory default value.

karibe
2009-09-20, 23:23
Hello
After successfully setup and first run SBR + SC duet I have usability problem.
I'm only using the same computer where is SC installed or external laptop as controller of SBR. The main problem is that after turning off SC serwer & controller for night I can't return back connection between SC and SBR when server is turned on again. I have to power off SBR ( by taking out AC plug ) and connect it again. Is it possible to set up SBR to auto reconnect after SC is showing up?

Mnyb
2009-09-21, 02:05
Hello
After successfully setup and first run SBR + SC duet I have usability problem.
I'm only using the same computer where is SC installed or external laptop as controller of SBR. The main problem is that after turning off SC serwer & controller for night I can't return back connection between SC and SBR when server is turned on again. I have to power off SBR ( by taking out AC plug ) and connect it again. Is it possible to set up SBR to auto reconnect after SC is showing up?

This is how it should work by default ? it does for me .
I have both server and squeezeboxes set to static-IP's , but afiak it *should* work on dhcp networks to.
Maybe it's enough to have static-IP for the server.

karibe
2009-09-21, 02:12
This is how it should work by default ? it does for me .
I have both server and squeezeboxes set to static-IP's , but afiak it *should* work on dhcp networks to.
Maybe it's enough to have static-IP for the server.

Are you saying that this is working for You? When You power on server SBR connecting again?
I have dhcp but SC and SBR always gets same ip's 192.168.1.20 for SBR and 192.168.1.18 for SC. Mayby I should fill up "server_address: IP address of currently active server (either Squeezenetwork or local server"?

ph0n33z
2009-09-21, 09:41
Alright,

I can play music over the SB through SC when I set squeezecenter_address to my pc's IP. All of that works fine.

However, the led never changes from blue even after configuration. Squeezenetwork does not see the player as being online, even when I can play music to it. I am trying to use iPeng directly with the SB through squeezenetwork, but since it doesn't see a player I can't do it.

Is there something else I have to do to configure the SB to speak with Squeezenetwork? Is there a squeezenetwork ip that I can use instead of my local SC?

gabe01
2009-09-22, 18:58
Okay, so I posted on another discussion group that my SC/SBRs had somehow pooped out. Everything worked perfectly for months and one day I could no longer find the SBRs in my SC. I didn't get anywhere with the suggestions I got and I'm assuming Logitech's support won't be helpful since I ditched the SBRC for an iPod Touch w/ iPeng long ago.

Anyway, I'm pretty un-versed in the language you guys are speaking, but I can follow simple instructions really well :)

I was reading through the instructions in Strocky's post from 8/31 and got through the email with only a few hiccups.

I first did a total uninstall of SC and hard reset of the SBR. It was blinking red slowly. Currently, I have a laptop running Vista with a hardwire connection to my NetGear router. I have disabled by wireless adapter for the time being, as was suggested earlier in this thread.

Here is my current set up:
UDAP [1] <squeezebox 16bd83>> list
bridging: 0
hostname: (name listed under SC Information > Hostname)
interface: 0
lan_gateway: 0.0.0.0
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0
server_address: 0.0.0.0
squeezecenter_address: 192.168.1.3 (i got this from SC Information tab > Server IP address)
squeezecenter_name:
wireless_SSID: (network name)
wireless_channel: 6
wireless_keylen: 0
wireless_mode: 0
wireless_region_id: 1
wireless_wep_key_0: (network password)
wireless_wep_key_1:
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 1
wireless_wpa_cipher: 3
wireless_wpa_mode: 1
wireless_wpa_on: 0
wireless_wpa_psk:

I do have WEP 64 bit and verified that the password is correct.

Now the light on the SBR is solid yellow. I understand this means that it's having a problem connecting to the network.

I found post #77 in this thread that addresses the yellow light and says to try the wired connection and lists the commands to do that (interface=1 lanipmode=1, savedata) and I still have a yellow light.

Any thoughts what on what to do next?

Thanks a ton - sorry for the long post!

Hokie02
2009-10-07, 17:25
So I set up my SBR a few months ago with a SBC and everything worked fine since then using iPeng. Recently I noticed the light on my SBR is stuck on blue and I can't get it to go to white.

I reset the SBR and ran UDAP wired to my computer and I am able to get it to turn white and work then (still don't think iPeng worked). I cannot however get it to turn white on wireless. I've tried everything and no matter what I put it turns blue. Here is my latest attempt, please let me know what could be wrong?

UDAP [1] (squeezebox 16af35)> list
bridging: 0
hostname: Squeezebox
interface: 0
lan_gateway: 0.0.0.0
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0
server_address: 192.168.1.4
squeezecenter_address: 192.168.1.4
squeezecenter_name:
wireless_SSID: VTHokies
wireless_channel: 11
wireless_keylen: 1
wireless_mode: 0
wireless_region_id: 4
wireless_wep_key_0: 1F90336FF1
wireless_wep_key_1:
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 1
wireless_wpa_cipher: 3
wireless_wpa_mode: 1
wireless_wpa_on: 0
wireless_wpa_psk:

I've also tried it with lan_gateway: 192.168.1.1, primary_dns:192.168.1.1, and lan_network_address: 192.168.1.4 and nothing. Any advice??

Hokie02
2009-10-07, 19:15
Just to follow up on my previous post. When I get the connection working through a wired connection (finally get a white light) both ipeng and squeezecenter can send music to my receiver. One strange thing is that if I choose an online music station or Pandora it shows that it's playing in squeezecenter or on ipeng but no sound comes out?

I still can't get the wireless to work. Looks like I have to shell out $200 to buy a stupid controller!!

radish
2009-10-07, 20:31
So I set up my SBR a few months ago with a SBC and everything worked fine since then using iPeng. Recently I noticed the light on my SBR is stuck on blue and I can't get it to go to white.

I reset the SBR and ran UDAP wired to my computer and I am able to get it to turn white and work then (still don't think iPeng worked). I cannot however get it to turn white on wireless. I've tried everything and no matter what I put it turns blue. Here is my latest attempt, please let me know what could be wrong?

UDAP [1] (squeezebox 16af35)> list
bridging: 0
hostname: Squeezebox
interface: 0
lan_gateway: 0.0.0.0
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0
server_address: 192.168.1.4
squeezecenter_address: 192.168.1.4
squeezecenter_name:
wireless_SSID: VTHokies
wireless_channel: 11
wireless_keylen: 1
wireless_mode: 0
wireless_region_id: 4
wireless_wep_key_0: 1F90336FF1
wireless_wep_key_1:
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 1
wireless_wpa_cipher: 3
wireless_wpa_mode: 1
wireless_wpa_on: 0
wireless_wpa_psk:

I've also tried it with lan_gateway: 192.168.1.1, primary_dns:192.168.1.1, and lan_network_address: 192.168.1.4 and nothing. Any advice??

The network settings don't look right. If it's not showing an IP that suggests DHCP is failing. Try setting lan_ip_mode=0 (static IP) and then set gateway/dns etc as appropriate. One thing I noticed is that you set lan_network_address to 192.168.1.4, but that's what you also have squeezecenter_address set to - that can't be right!

Hokie02
2009-10-08, 05:41
The network settings don't look right. If it's not showing an IP that suggests DHCP is failing. Try setting lan_ip_mode=0 (static IP) and then set gateway/dns etc as appropriate. One thing I noticed is that you set lan_network_address to 192.168.1.4, but that's what you also have squeezecenter_address set to - that can't be right!

What do you mean that if it's not showing an IP that suggest DHCP is failing? If what isn't showing an address? I set lan_network_address=0.0.0.0 and then after I reset it I'm still stuck on blue and when I plug it back in to do another conf 1 and list it's then set to some other address like 169.254.80.xxx. You have to have it plugged in wired when setting up the wireless correct? It's like it's automatically assigning a lan_network_address but I don't know if it does it wirelessly because the only way to check it is to plug it in?

For my settings I was just trying to copy what others were saying was working and then using my own values. I'm pretty sure I have DHCP (how do you know?) so that's why I didn't set gateway or dns. If I do set those, they should both be the same at 192.168.1.1 correct? (that's what ipconfig says for default gateway, IP4 says 192.168.1.4). So if I set lan_ip_mode to 0 then I use those values and if I don't then those values can be empty correct?

You also said I lan_network_address to the same as squeezecenter_address at 192.168.1.4 but I set lan_network_address to 0.0.0.0? Did you mean I set server address the same as squeezecenter_address? I thought that's how you were supposed to do it? What should I be setting squeezecenter address to? If I look at the squeezecenter control panel it says the server is running and the server address is 192.168.1.4 and that mysqueezebox.com server address is 66.150.114.115. Am I supposed to be using that 2nd IP address for anything?

I really appreciate your help and would really like to get this working!!

Hokie02
2009-10-08, 05:50
Forgot to ask, do I have to do a hard reset (hold down button till fast red flash) every time I retry a new set of settings or go from wired to wireless? If I try going from my wireless settings that aren't working back to wired it doesn't seem to work unless I hard reset it first.

Also, can you think of any reason why none of the internet radio will play? I can select and and it shows playing in both Squeezebox Server web interface and on the iPeng but no sound comes out? This is for wired.

radish
2009-10-08, 06:02
What do you mean that if it's not showing an IP that suggest DHCP is failing? If what isn't showing an address?

lan_network_address. If you're using DHCP it should be set automatically to something like 192.168.1.x. If you're not you have to set it manually, but it has to be unique - you can't set it to an address already used by the server.



I set lan_network_address=0.0.0.0 and then after I reset it I'm still stuck on blue and when I plug it back in to do another conf 1 and list it's then set to some other address like 169.254.80.xxx.

That's an autoconf IP, it means that you have it set to use DHCP (which is fine) but the DHCP is failing. That usually means it's not connecting to the network properly (WEP key error I would guess). The fact that it works wired would back that up.



I'm pretty sure I have DHCP (how do you know?)

ipconfig /all would say "DHCP enabled: yes" on Windows.



If I do set those, they should both be the same at 192.168.1.1 correct? (that's what ipconfig says for default gateway, IP4 says 192.168.1.4).

Then that sounds right.



So if I set lan_ip_mode to 0 then I use those values and if I don't then those values can be empty correct?

Yes but you can't copy the IP, it has to be unique (but of the form 192.186.1.x). If you're using DHCP on the network but you want to set one manually it has to be outside the DHCP range to avoid collisions. To keep it simple, use static everywhere or DHCP everywhere.



You also said I lan_network_address to the same as squeezecenter_address at 192.168.1.4 but I set lan_network_address to 0.0.0.0?

I was just reading what you said in the last line of your post.



What should I be setting squeezecenter address to?

The server's IP.



Am I supposed to be using that 2nd IP address for anything?

No


Recommendation - disable WEP (it doesn't do any good anyway) and try the setup without any network security. That will prove the basics are working, then enable WPA and use that. I've often seen issues with WEP key errors where the device think's it's connected but it isn't (which would explain the blue light).

Hokie02
2009-10-08, 06:15
lan_network_address. If you're using DHCP it should be set automatically to something like 192.168.1.x. If you're not you have to set it manually, but it has to be unique - you can't set it to an address already used by the server.


That's an autoconf IP, it means that you have it set to use DHCP (which is fine) but the DHCP is failing. That usually means it's not connecting to the network properly (WEP key error I would guess). The fact that it works wired would back that up.


ipconfig /all would say "DHCP enabled: yes" on Windows.


Then that sounds right.


Yes but you can't copy the IP, it has to be unique (but of the form 192.186.1.x). If you're using DHCP on the network but you want to set one manually it has to be outside the DHCP range to avoid collisions. To keep it simple, use static everywhere or DHCP everywhere.


I was just reading what you said in the last line of your post.


The server's IP.


No


Recommendation - disable WEP (it doesn't do any good anyway) and try the setup without any network security. That will prove the basics are working, then enable WPA and use that. I've often seen issues with WEP key errors where the device think's it's connected but it isn't (which would explain the blue light).

Thank you so much for the detailed response, I just wish I understood it all! I do have DHCP enabled (checked in ipconfig) so I'd like to stick with DHCP for everything. I can try disabling WEP but I want to make sure I understand everything else first. For lan_network_address I can use 0.0.0.0 and it should assign it automatically since I have DHCP. I also want to stay with lan_mode of 1 (DHCP) and not set anything for lan_gateway and primary_dns since those are static only settings, correct? Server address and squeezecenter address should still both be the same and should be 192.168.1.4 I believe.

If this is the case I have everything already set up correctly, I just need to just try disabling WEP. Let me give that a go and see what happens. Do I need to reset the SBR completely before switching over to wireless or can I just start changing the settings from the wired setting and just making sure I'm on interface=0?

Hokie02
2009-10-08, 06:29
radish, THANK YOU THANK YOU THANK YOU!!!! I finally got it working after 5 hours of messing around thanks to your help! I turned off the WEP and didn't even set a server_address (realized it after i input it) and now it works wirelessly, including the internet radio/pandora stuff which wasn't working before. Is there a reason I didn't need to set server_address? These were my working settings:

bridging: 0
hostname:
interface: 0
lan_gateway: 0.0.0.0
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0
server_address: 0.0.0.0
queezecenter_address: 192.168.1.4
squeezecenter_name:
wireless_SSID: VTHokies
wireless_channel: 11
wireless_keylen: 1
wireless_mode: 0
wireless_region_id: 4
wireless_wep_key_0: 1F90336FF1
wireless_wep_key_1:
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 0
wireless_wpa_cipher: 3
wireless_wpa_mode: 1

Now my question is, how do I get WEP working? I'd really like to use it as I have like 50 neighbors who will mooch off my connection. What could I be doing wrong with the WEP? I entered it exactly how it is on my computer?

Hokie02
2009-10-08, 06:52
Nevermind, took your advice and got it working just fine with WPA! Now no more stupid wep keys!! Thank you so much again, you're a life saver! (or at least a $200 saver for a controller) :)

Hokie02
2009-10-08, 11:18
Ok, I still have one problem. When I get it set up the light turns white and I can control everything wirelessly from my computer and from the iPeng but if I turn off my computer and the light goes blue (expected) it doesn't turn back to white when I turn the computer back on like it's supposed to. I need to either unplug it and plug it back in or reprogram it using UDAP. What could cause this?

htrd
2009-10-08, 12:45
the light goes blue

Check out this post:

http://lists.projects.robinbowes.com/Net-UDAP/mailman/net-udap/2009-September/000122.html

Hokie02
2009-10-08, 12:55
Check out this post:

http://lists.projects.robinbowes.com/Net-UDAP/mailman/net-udap/2009-September/000122.html

What is this link in response to? With the help of radish I was able to get everything set up so I can now connect but I still have to unplug/replug the SBR every time I restart my computer.

strocky
2009-10-13, 04:10
radish, THANK YOU THANK YOU THANK YOU!!!! I finally got it working after 5 hours of messing around thanks to your help! I turned off the WEP and didn't even set a server_address (realized it after i input it) and now it works wirelessly, including the internet radio/pandora stuff which wasn't working before. Is there a reason I didn't need to set server_address? These were my working settings:

bridging: 0
hostname:
interface: 0
lan_gateway: 0.0.0.0
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0
server_address: 0.0.0.0
queezecenter_address: 192.168.1.4
squeezecenter_name:
wireless_SSID: VTHokies
wireless_channel: 11
wireless_keylen: 1
wireless_mode: 0
wireless_region_id: 4
wireless_wep_key_0: 1F90336FF1
wireless_wep_key_1:
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 0
wireless_wpa_cipher: 3
wireless_wpa_mode: 1

Now my question is, how do I get WEP working? I'd really like to use it as I have like 50 neighbors who will mooch off my connection. What could I be doing wrong with the WEP? I entered it exactly how it is on my computer?


I'd edit out your Wireless Wep Key (or your neighbours could access your Network)

lowfi
2009-10-20, 13:26
The software didnt work for me in windows 7 (precompiled exe) and osx 10.6.1. I ended up using ubuntu8.04 to do the setup of a receiver. Now it works flawlessly.

Anybody else experienced this problem?

How btw can i update the firmware of a receiver right now? I imagine you normally do this with the SBC?

Mnyb
2009-10-20, 18:40
The software didnt work for me in windows 7 (precompiled exe) and osx 10.6.1. I ended up using ubuntu8.04 to do the setup of a receiver. Now it works flawlessly.

Anybody else experienced this problem?

How btw can i update the firmware of a receiver right now? I imagine you normally do this with the SBC?

The reciever auto updates fw , it's tied to the version of squeezeboxserver you are running, fyi reciever fw is not changed as often as controller.

lbryanray
2009-10-22, 12:20
I've been running my duet receiver from my laptop without a controller (many, many thanks to Robin). I'm doing this with squeezebox server (the old squeezecenter).
I'd like to be able to listen to Pandora, and if I understand correctly, I need to do that through the web - mysqueezebox.com or what we used to call squeezenetwork. But although I'm logged in with the same information at squeezebox server and mysqueezebox, Myqueezebox.com does not recognize my player. It says "Oops! You don't appear to have any players registered to this account."
Is there a way to use the UDAP config tool to get control via the web? Is there a way to switch back and forth (from control by squeezebox server to control from mysqueezebox without a controller?

Thanks,
Bryan

toby10
2009-10-23, 04:53
You can play Pandora (and any other supported Music Services) from your local SBS server. Can you currently play any Internet Radio to your player from SBS?

Make sure you have your MySB login info entered onto your SBS > Settings > MySqueezeBox. This will "register" your player onto MySB.

If you do want to get your player connected directly to MySB you can simply use the SBS server to send the player to MySB and/or grab the player back from MySB. SBS > Extras > Music Source

But as you are limited to laptop control (Receiver with no Controller) you may as well just use SBS for all player purposes including Internet Radio and Music Services.

lbryanray
2009-10-23, 06:57
Thanks Toby. I must be missing something here. I can play internet radio, but I don't see how I can connect to Pandora from SBS. (I do have a Pandora account and have it as an App in MySB.) Where in the list of sources should Pandora show up in SBS?
I do also have my MySB login entered in the SBS as you indicated.
Bryan

toby10
2009-10-23, 07:36
Thanks Toby. I must be missing something here. I can play internet radio, but I don't see how I can connect to Pandora from SBS. (I do have a Pandora account and have it as an App in MySB.) Where in the list of sources should Pandora show up in SBS?
I do also have my MySB login entered in the SBS as you indicated.
Bryan

Should be listed in My Apps on SBS7.4, or in Music Services on SC7.4 (not sure which you are running).

lbryanray
2009-10-23, 11:21
Should be listed in My Apps on SBS7.4, or in Music Services on SC7.4 (not sure which you are running).

I'm running squeezebox server Version: 7.4.1 - r28947 .
I dont see any reference to Apps in the squeezebox server. I get choices of My Music, Internet Radio, Favorites, and Extras. but none of these contains Apps.
I can only see Apps at mysqueezebox.com. Pandora is there, but as mentioned above, I can't play it because mysqueezebox.com doesn't recognize my player.

toby10
2009-10-23, 11:56
What computer and OS are you running SBS on?
In Extras try clicking on "connect to MySB". This should log your player onto MySB.

lbryanray
2009-10-23, 13:45
What computer and OS are you running SBS on?
In Extras try clicking on "connect to MySB". This should log your player onto MySB.

I'm using an IBM ThinkPad running Windows XP Pro. From what you are saying, it sounds like I'm not seeing everything in SBS that I should. There is no "connect to MySB" option under Extras, just Alarm Clock, Music Source, Info Browser, Podcasts.

Someone in another thread
http://forums.slimdevices.com/showthread.php?p=475278#poststop
had a sort of similar problem that was resolved as an issue with the database for MySB at Logitech. Wonder if something odd has happened there for me as well.

lbryanray
2009-10-24, 08:50
What computer and OS are you running SBS on?
In Extras try clicking on "connect to MySB". This should log your player onto MySB.

I'm running squeezebox server Version: 7.4.1 - r28947 .
I dont see any reference to Apps in the squeezebox server. I get choices of My Music, Internet Radio, Favorites, and Extras. but none of these contains Apps.
I can only see Apps at mysqueezebox.com. Pandora is there, but as mentioned above, I can't play it because mysqueezebox.com doesn't recognize my player.

toby10
2009-10-24, 09:32
.....
In Extras try clicking on "connect to MySB". This should log your player onto MySB.

And trying Extras?

lbryanray
2009-10-24, 13:03
And trying Extras?

There is no "connect to MySB" under Extras. The only listings there are Alarm Clock, Music Source, Info Browser, and Podcasts.
It seems like I'm not connecting properly to MySB although I'm logged in the same there and on the server.
Someone in another thread had a problem like mine -
http://forums.slimdevices.com/showthread.php?t=70067
that was some mixup at the Logitech database side. I wonder if that's my issue as well.

lbryanray
2009-10-24, 13:57
And trying Extras?
connect to MySB does not exist under extras

Aesculus
2009-10-28, 15:29
connect to MySB does not exist under extras

Extras=>Music Source

lbryanray
2009-10-28, 18:21
Extras=>Music Source

I'm still looking, but there's no "connect to MySB" under Music Source. I see my squeezebox server hostname there and my desktop computer's music library, but that's it.
thanks

Aesculus
2009-10-29, 18:07
I'm still looking, but there's no "connect to MySB" under Music Source. I see my squeezebox server hostname there and my desktop computer's music library, but that's it.
thanks

There should be an entry for mysqueezebox.com.

Did you fill out the email and pw under Server Settings = > mysqueezebox.com?

lbryanray
2009-10-29, 19:19
There should be an entry for mysqueezebox.com.

Did you fill out the email and pw under Server Settings = > mysqueezebox.com?

Yes, I did fill out the Server Settings. i'm not sure what you mean by the email.
Oddly enough, if I open the control panel from the icon in the windows taskbar, there is a 'diagnostics' tab, which shows the IP address of the mysqueezebox.com and 'OK' for the 'ping' and 'port' status. But somehow I'm just not connected.

toby10
2009-10-30, 03:58
MySB registration requires a validation from the email you provided to MySB.

enroberts
2009-11-04, 13:32
Hello, I too am having the same issues the above poster has been having in regards to getting the SBR to connect to pandora/slacker/sirius radio. I did activate the account using the link provided in the email, but still get the OOPS! message on MSB.com that was discussed earlier here. without getting the reciever to register with mySB.com, pandora, slacker, or any other apps "installed" via mySB.com will no appear in the server software, nor will the user be able to even connect the rcvr to mySB.com. This is only true for new users, not users who were able to register their accounts when squeezenetwork.com was still available. Ultimatly, Logitech needs to create a button on the squeezebox server software control panel that says "connect SBR to MySB.com" The only current way to do it is using a Duet remote, and even then, you must decide whether you want to listen to your PC music or connect to MySB.com and listen to Pandora, slacker, or other "Apps" you might have installed. Logitech messed up on this one! I have well over 100 customers right now with squeezeboxe rcvrs in their houses and would continue to sell hundreds more, but without this problem being solved, I CANT! Any one have some ideas? Thanks much! -Neal

JasonAG
2009-11-10, 11:53
Forgive the newbie question, but I too want to configure a SqueezeBox Receiver without a controller. Has anyone had success using Net::UDAP on Windows XP through a Virtual Machine? I have Windows XP on my MacBook Pro, but it's running in VMWare Fusion 3. Will Net::UDAP discover the Receiver through VMWare's NAT?

Thanks!

Blisteringblue
2009-11-27, 08:37
Thanks for this thread everyone. I just configured my receiver on vista (wired & dhcp) in about 5 mins !! I just did not need the controller, however nice it looks !!

lbryanray
2009-11-27, 20:51
Any one have some ideas? Thanks much! -Neal[/QUOTE]

I was able to get properly connected without the controller by interacting with Logitech support. They apparently fixed the database entries on their end and now all is working fine for me.

gabe01
2009-11-30, 14:29
Hello - I have posted in the past with a problem that my SBR light went blue and I couldn't get everything configured correctly with UDAP. In the end, I bought a remote controller, ran the configuration, and then returned it =P...well, now it's happened again! I have 2 SBRs running with iPeng. One SBR light went blue (last time both went blue) and is no longer listed as an "available player". The other SBR is working normally. I imagine that I just need to copy whatever configuration settings are in my working one, to my non-working one, and that I can use UDAP to check this out. However, before I do this, I wanted to see if running the script would cause a "reset" or something that would cause both SBRs to lose all of their configurations? Or, if I can run the script, take a look at one list of settings, and re-type those for the other SBR? Anyone know? I really don't want to get in the habit of having to buy/return those controllers!

Robin Bowes
2009-11-30, 15:35
On 30/11/09 21:29, gabe01 wrote:
>
> Hello - I have posted in the past with a problem that my SBR light went
> blue and I couldn't get everything configured correctly with UDAP. In
> the end, I bought a remote controller, ran the configuration, and then
> returned it =P...well, now it's happened again! I have 2 SBRs running
> with iPeng. One SBR light went blue (last time both went blue) and is no
> longer listed as an "available player". The other SBR is working
> normally. I imagine that I just need to copy whatever configuration
> settings are in my working one, to my non-working one, and that I can
> use UDAP to check this out. However, before I do this, I wanted to see
> if running the script would cause a "reset" or something that would
> cause both SBRs to lose all of their configurations? Or, if I can run
> the script, take a look at one list of settings, and re-type those for
> the other SBR? Anyone know? I really don't want to get in the habit of
> having to buy/return those controllers!


If you press and hold the button until it starts flashing, then release,
you should be able to discover with Net-UDAP. Don't press and hold too
long or you'll do a factory reset which would lose your settings.

R.

gabe01
2009-12-01, 10:36
On 30/11/09 21:29, gabe01 wrote:[color=blue]
>
If you press and hold the button until it starts flashing, then release,
you should be able to discover with Net-UDAP. Don't press and hold too
long or you'll do a factory reset which would lose your settings.

R.

Thanks for the response! I assume that you are saying I should do this to the SBR that is currently working normally? The non-working one should get a factory reset since it is not working at all. Then I would discover the working one, note those settings, and discover the non-working one and enter the configuration?

local.bin
2009-12-11, 16:43
Is there a slight possibility that Net-UDAP works with a Squeezebox Radio :-/?

Tiring entering my WPA2 code each time I have problems!

Thanks in advance

Cheers

pippin
2009-12-11, 16:44
Is there a slight possibility that Net-UDAP works with a Squeezebox Radio :-/?

Tiring entering my WPA2 code each time I have problems!

Thanks in advance

Cheers

The Radio doesn't speak UDAP.

local.bin
2009-12-13, 06:44
Ok thanks for the reply :)

ericj
2009-12-13, 10:21
I have upgraded to Mac OS 10.6 and tried NET UDAP. Both the SVN and the zip file load fine, but the discover command returns instantaneously. I also tried the broacast_test.pl (working blindly here) which told me that IO/Interface/SIMPLE.pm cannot be located.

Any clues on what is up? Is @INC, which point to a Perl Library correct?

Thanks in advance.
Eric

strocky
2010-01-01, 18:48
Right just bolloxed my connection to the duet, when I installed IPENG to my IPOD Touch

Went to set-up UDAP again, but when I use the "discover" command, I get the following error -:

UDAP> discover
info: *** Broadcasting adv_discovery message to MAC address 00:00:00:00:00:00 on
255.255.255.255
Use of uninitialized value in length at /PerlApp/Net/UDAP/Util.pm line 57, <FIN>
line 2.
Use of uninitialized value in length at /PerlApp/Net/UDAP/Util.pm line 67, <FIN>
line 2.
Supplied string has length0(expected length: 6) at /PerlApp/Net/UDAP.pm line 296

Use of uninitialized value in concatenation (.) or string at /PerlApp/Net/UDAP.p
m line 297, <FIN> line 2.
info: adv_discovery response received from
Use of uninitialized value in length at /PerlApp/Net/UDAP/Util.pm line 57, <FIN>
line 2.
Use of uninitialized value in length at /PerlApp/Net/UDAP/Util.pm line 67, <FIN>
line 2.
Supplied string has length0(expected length: 6) at /PerlApp/Net/UDAP.pm line 358

mac not found in msg at /PerlApp/Net/UDAP/Shell.pm line 156
UDAP>


Only difference between the last install & this one is the O/S on my PC (Vista x64 to Windows 7 x64)

Any pointers?

ericj
2010-01-07, 05:38
I pulled from backup my last known good Net::Udap, and see the same problem with it not really doing discover, and with the error mentioned above.
Anyone verify that it is a Snow Leopard problem?
Thanks.

drbob49
2010-01-07, 05:45
I'm unable to 'discover' using Net::UDAP from my macbook using Snow Leopard. Have to use VMware installed XP and it all works fine.

Bob

robinbowes
2010-01-07, 05:59
Guys (& Gals),

Most of the discovery issues in Net::UDAP are because I did a dirty hack to work out the machines local IP addresses (I parse the output of ifconfig or ipconfig on Windows). This is fragile and fails on OSX and any non-English locale.

There is a module that can be used to list local IP addresses - I use it in the current trunk version - but is not pure perl, ie. it requires binary compilation and I am trying to keep Net::UDAP pure perl so it's easy to install (extract the tarball/zip and run).

Anyway...

I've added a new option in the 1.0.x branch to allow the local address to be specified. Get it here:

https://projects.robinbowes.com/Net-UDAP/trac/browser/branches/1.0.x

(download the zip file from the link at the bottom of the page)

Use it as follows:

scripts/udap_shell.pl --local-address a.b.c.d

where:
a.b.c.d is the IP address of the local machine

Please let me know how this works for you, preferably with a post to my mailing list:

http://lists.projects.robinbowes.com/mailman/listinfo/net-udap

Cheers,

R.

ericj
2010-01-07, 10:32
That works. Thanks. I was getting a bit tired, carry my remote back to the office whenever the receiver would forget the server's ip.
Eric

bebop
2010-01-08, 13:03
Made it possible for me to set a static IP on my Duet Player.
A word of caution though ! do not set the SBC Controller to static ip before you have made the initial setup of the SBC Player, otherwise it will not find it.

moozoo
2010-01-09, 08:28
Hey everyone,

I want to congratulate you guys on the FANTASTIC work you have done! VERY much appreciated! The world need more like you!

I am running into some issues though: the unit works fantastically in wired mode. I cannot get it to funtion in wireless though. My router (Linksys WRT120) is set to WEP 128bit encryption. Everytime it tries to connect wirelessly, I get a yellow light. I had assigned the mac address of the SB receiver to the router (I am wondering if the mac address changes if it goes from wired to wireless) and put that reserved ip address into the lan_network_address field. The other thing I find bizarre is that while I did change the wep_keylen to 1 (for 128 bit), everytime the SB receiver resets and I check its config, I notice that it chops out about half of the wireless_wep_key_0 field (leading me to believe that it is somehow still stuck on 64 bit). Is anyone else having this issue? Should I go to WPA?

Any help is much appreciated! Thanks again!!!

garym
2010-01-09, 08:37
have you tried with WEP 64 or better yet, WPA

do a search of this forum on keyword "WEP" and you'll see lots of posts on issues related to WEP

jkeny
2010-01-16, 16:08
Noob here :)
I have struggled with this for a couple of hours now but can't get it to work. Can I connect my SBR directly to my laptop without any wireless network involvement? My laptop is on WiFi but the modem/router is not convenient to my HiFi.

I tried RobinBowes standard net tool & local address variant but I can't get SBR discovered. I've tried standard ethernet & crossed ethernet cable between laptop & SBR.

Any help appreciated.

ronin
2010-01-17, 18:38
ok, so i got everything set up nicely using the config below.
however, when i try to switch sources within iPeng the connection is lost with the player and cannot be re-established without a power cycle.

all sources work normally provided they are selected prior to power cycle.
all sources have been successfully connected but have never switched successfully in the same session.
all methods of switching have been applied.
setting the squeezecenter_address to any other squeezebox server address results in the same behaviour.

bridging: 0
hostname: Squeezebox
interface: 0
lan_gateway: 0.0.0.0
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0
server_address: 0.0.0.0
squeezecenter_address: 89.202.121.131 (mysqueezebox.com)
squeezecenter_name:
wireless_SSID: my wireless
wireless_channel: 0
wireless_keylen: 1
wireless_mode: 0
wireless_region_id: 14
wireless_wep_key_0:
wireless_wep_key_1:
wireless_wep_key_2:
wireless_wep_key_3:
wireless_wep_on: 0
wireless_wpa_cipher: 3
wireless_wpa_mode: 1
wireless_wpa_on: 1
wireless_wpa_psk: my password

does anything sound alarms here?

Mnyb
2010-01-17, 22:17
Ok correct me if I'm wrong but is not lan ip mode= 1 static
If you are using DHCP set lan ip mode= 0

If you are intending to use static ip none of settings below should be 0.0.0.0 you must fill in the correct oip,dns etc for your network.
If you are using DHCP these will be set by your router.

lan_gateway: 0.0.0.0
lan_ip_mode: 1
lan_network_address: 0.0.0.0
lan_subnet_mask: 255.255.255.0
primary_dns: 0.0.0.0
secondary_dns: 0.0.0.0

ronin
2010-01-18, 11:36
you stand corrected, lan_ip_mode=1 is DHCP.

why can't i switch sources in iPeng without losing the connection entirely?

pippin
2010-01-18, 11:47
you stand corrected, lan_ip_mode=1 is DHCP.

why can't i switch sources in iPeng without losing the connection entirely?

That's what I would like to understand, too.
iPeng doesn't talk to the player directly. It tells the server to which the player is _currently_ connected to connect it to the new server and the actual switch is then initiated by the server (the current one).

I have no idea what the server does, then.

I can reproduce cases in which the switch doesn't work (e.g. when I use an ambiguous URL when connecting from over the internet but then usually the plkayer stays connected to the original server.

jkeny
2010-01-18, 20:49
Sorry guys, is any of this an answer to my question about discover not working when SBR is connected directly to a PC? Should I get the on-screen PC message "LAN connected" when I plug in the ethernet cable?

Please help!

As I said this SBR connects to modem/router, so nothing wrong with the hardware or cable!

rgough
2010-01-19, 11:42
I am using Net::UDAP version 1.0.x on Windows 2000 (won't work on Windows 7, even with the --local-address option).

Periodically, sometimes after days with no problems, the server will lose connectivity with the receiver. I have found that issuing a "reset" command from the UDAP shell (in the "configuration" sub-shell) will bring it back to visibility by Squeezebox Server (and iPeng).

I have spoken with Logitech and, of course, they do not support my configuration (without the controller). They did however suggest I perform a "reupdate" of the firmware (it's at the latest version), but could not tell me how.

Is there a way to do this with Net::UDAP?

Any other ideas for resolving this problem?

I have had the receiver nearly 30 days, and reluctantly am on the verge of returning it. When it works, it's wonderful, but when it doesn't, it's very frustrating.

Thank you for any assistance you can provide.

cira
2010-01-26, 09:45
Got the UDAP tool to work but it does lose the connection from time to time requiring me to set it up again. It was a sinch when the ipeng remote gave you the IP of the receiver, however with the newest ipeng update it no longer gives you that info.

How do you get the IP of the receiver. Additionally, i'm assuming it drops because it is not assigned a static IP. Once i figure out the IP that it is, how do i permanently assign it to that?

thanks for any help

nico
2010-01-30, 02:37
Hi all,

Just like to report my findings using Net::UDAP to configure a SBR on a wired LAN with DHCP-assigned ipaddr to point to the SqueezeNetwork and stream music from there.

The perl code doesn't seem to work on Mac OS X Leopard. It seems the discovery mechanism is the problem. Nothing seems to happen when I ran `discover'. No info messages showing any activity. Also tried running broadcast_test.pl on OS X but that also didn't work.

However, I tried again from a Windows XP machine and all went smoothly. To point the SBR to the SqueezeNetworks service I just did a DNS lookup of www.squeezenetwork.com and used the first ip addr in the result (66.151.159.227).

In summary, these are the commands I used:


set interface=1
set lan_ip_mode=1
set lan_gateway=192.168.253.254
set primary_dns=192.168.253.17
set secondary_dns=210.130.1.1
set server_address=66.151.159.227
set squeezecenter_address=66.151.159.227
save_data
reset


After that, I was able to see and control the SBR on mysqueezebox.com. How awesome is that! Thanks very much for the tool.

ericj
2010-01-30, 06:05
Did you try the version and command line switch described here:
http://forums.slimdevices.com/showpost.php?p=503786&postcount=146

Worked like a charm and continues to work for me.

nico
2010-01-30, 19:59
No, I didn't see that post, but it looks totally relevant and probably solves the issue on OS X. I bookmarked it and will certainly try it next time I need to configure the SBR. Thanks for the tip.

soloz2
2010-03-21, 11:41
Is there maybe an Idiots guide to using this software to configure a receiver? I can't seem to figure it out.

Main rig running Win 7 x64, will be running server on my WHS box.

robinbowes
2010-03-22, 16:52
Which part are you having trouble with?

What have you tried? What results did you get? Did you see any error messages?

http://catb.org/~esr/faqs/smart-questions.html

R.

soloz2
2010-03-25, 04:04
I downloaded the software direct so I should have the latest version. I opened the port in my firewall and connected the receiver to the same switch my PC is connected to. However, I was unable to get the software to connect to the receiver.

Then I saw someone on avs recommend downloading a package that would automatically connect to the software. udap_shell_1_0_0.exe I followed the instructions, but the receiver never did anything ie (flash or change color when supposed to)

My PC is running Win 7 Pro x64, slim server is running on my WHS box. Do I need to configure it from the same machine that is running the server?

robinbowes
2010-03-25, 04:43
What version did you download? Please be specific.

Does it have the --local-address option? If not, grab the latest 1.0.x branch version that does [1].

What output do you see when you run udap_shell.pl?

R.

[1] https://projects.robinbowes.com/Net-UDAP/trac/changeset/131/branches/1.0.x?old_path=%2F&old=131&format=zip

ziphnor
2010-03-27, 02:47
Im also having problems on Win 7 x64.

I am using the 1.0x version and ActivePerl 5.10.1.1007.

Here is my output:


C:\netudap>perl scripts/udap_shell.pl --local-address 192.168.1.34

UDAP> discover

UDAP>


If i run broadcast_test.pl i get:



C:\netudap\scripts>broadcast_test.pl
Can't locate IO/Interface/Simple.pm in @INC (@INC contains: C:/Perl/site/lib C:/
Perl/lib .) at C:\netudap\scripts\broadcast_test.pl line 8.
BEGIN failed--compilation aborted at C:\netudap\scripts\broadcast_test.pl line 8.


The only Simple.pm files i can find in the perl folder are not located under IO and seem completely unrelated.

Any help would be appreciated.

robinbowes
2010-03-27, 03:04
ziphnor,

Is 192.168.1.34 the address of the machine on which you are running udap_shell.pl?

Have you made sure the firewall is allowing incoming 17784 udp, and broadcast messages?

Ignore broadcast_test.pl; it only works if you have IO::Interface::Simple installed, and that doesn't work on Windows.

R.

ziphnor
2010-03-27, 03:25
Is 192.168.1.34 the address of the machine on which you are running udap_shell.pl?


Yes. (i have also tried without specifying the address).



Have you made sure the firewall is allowing incoming 17784 udp, and broadcast messages?


The windows firewall is turned off.

Thank your answering so quickly by the way. I hope to solve this soon as my girlfriend is a bit upset that our music and radio isnt working :)

EDIT: Perhaps i should mention that i have used netudap several times before without problems, but since then i have installed Win 7 x64 on my desktop pc.

robinbowes
2010-03-27, 03:30
A couple more ideas...

Is the SBR connected to the same network segment as the computer on which you are running udap_shell?

Did you factory reset the SBR (press and hold the button until it flashes red quickly) ?

R.

ziphnor
2010-03-27, 04:02
Is the SBR connected to the same network segment as the computer on which you are running udap_shell?


Its on the same wired LAN, connected to my desktop via 2 switches. However, it is not responding to pings on its usual IP address since i did the factory reset (even though the routers DHCP server is setup to always give the same ip to the squeezebox).



Did you factory reset the SBR (press and hold the button until it flashes red quickly) ?


Yes, it is currently flashing red slowly, is that correct?

Btw, i seem to remember the old versions of net-udap outputting a broadcast message on the console when running discover. When i run discover it returns immediatly without output.

robinbowes
2010-03-27, 04:29
Well, I just downloaded and installed the latest 1.0.x trunk version (r131) onto a 32-bit Windows 7 machine which has ActivePerl 5.10.1 Build 1006 on it.

It seems to work OK, ie. it displays "Broadcasting adv_discovery message..."

Note, it does *not* do this if I don't specify the --local-address option.

Are you *sure* that's the right IP address?

What's the output from "ipconfig /all" ?

R.

ziphnor
2010-03-27, 04:35
Well, I just downloaded and installed the latest 1.0.x trunk version (r131) onto a 32-bit Windows 7 machine which has ActivePerl 5.10.1 Build 1006 on it.


Im on 64-bit Windows 7, not 32bit, perhaps that makes a difference?



It seems to work OK, ie. it displays "Broadcasting adv_discovery message..."

Note, it does *not* do this if I don't specify the --local-address option.

Are you *sure* that's the right IP address?

What's the output from "ipconfig /all" ?


The output is:



C:\netudap>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : ptpc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-24-1D-D3-B6-75
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2588:4e5a:68a7:cc86%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.34(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 27. marts 2010 10:24:03
Lease Expires . . . . . . . . . . : 30. marts 2010 10:24:03
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 234890269
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-87-9E-B7-00-24-1D-D3-B6-75

DNS Servers . . . . . . . . . . . : 89.150.129.4
89.150.129.10
89.150.129.4
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Anchorfree HSS Adapter
Physical Address. . . . . . . . . : 00-FF-67-26-8D-45
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{D15A0E43-379C-4782-A445-AF95731F7272}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:73bc:2:c0d6:a547:5651(Preferr
ed)
Link-local IPv6 Address . . . . . : fe80::2:c0d6:a547:5651%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{67268D45-BD1E-4D6D-AA65-ACAE412F1308}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

robinbowes
2010-03-27, 04:44
OK, can you take this to the net-udap mailing list [1]. I'll need some debugging output from you.

Can you edit src/Net-UDAP/lib/Net/UDAP/Log.pm and change "info" to "debug" here:

use Log::StdLog {
handle => *STDERR,
level => 'info',
format => \&std_log_format,
};

Then run "udap_shell.pl --local-address=192.168.1.34", and do a "discover".

Post the output to the mailing list.

R.

robinbowes
2010-03-27, 04:48
BTW, I have to head out shortly, so I may not get back to you for a while.

R.

robinbowes
2010-03-27, 04:55
I forgot the mailing list details:

http://lists.projects.robinbowes.com/mailman/listinfo/net-udap

R.

ziphnor
2010-03-27, 05:40
OK, can you take this to the net-udap mailing list

It seems to have solved itself now, i turned my computer off completely and now suddenly it works. Perhaps some of my network settings hadnt been applied properly before that (though im sure i did a restart) or maybe my squeezebox just needed another restart.

So sorry for wasting your time...

I hope its okay if i dont post on the mailing list, since there is nothing to report.

robinbowes
2010-03-27, 08:36
No probs, glad it's sorted.

However, if you posted to the mailing list you would have seen this:

_______________________________________________
Net-UDAP is free software - you do not have to pay for it.
However, if you found it useful, please consider donating:
https://projects.robinbowes.com/Net-UDAP/trac#Donations

;)

R.

Mnyb
2010-03-27, 09:12
No probs, glad it's sorted.

However, if you posted to the mailing list you would have seen this:

_______________________________________________
Net-UDAP is free software - you do not have to pay for it.
However, if you found it useful, please consider donating:
https://projects.robinbowes.com/Net-UDAP/trac#Donations

;)

R.

What kind of donation would persuade you to do an GUI version that is "proper" program not a script :) It's time for my yearly but kind reminder of " where is the GUI version please " or integration with sbs in the best of worlds .
Thanks yet again for the scripts as that is the only way to setup an receiver in my network (even with the controller present).

Hmm I think about about another donation hmm

robinbowes
2010-03-27, 10:46
I did start on a Squeezebox Plugin, but haven't done any work on it for some time.

A GUI version would be a fairly big undertaking.

Unfortunately, I'm rather busy at the moment with $real_job so both are rather unlikely in the short term.

R.

Mnyb
2010-03-27, 11:32
I did start on a Squeezebox Plugin, but haven't done any work on it for some time.

A GUI version would be a fairly big undertaking.

Unfortunately, I'm rather busy at the moment with $real_job so both are rather unlikely in the short term.

R.

Well I cant outbid a real jobb :) $$
Spare time get so much more valuable when you have non of it.

fixxx
2010-04-07, 16:05
Hi,

My receiver is not being discovered in the UDAP script.

Both receiver and laptop wired to my airport extreme
In the airport extreme opened port 17784 to my laptop's ip

restarted everything several times, but not working.

Any tips?

tcutting
2010-04-07, 16:26
Are you putting the Receiver into configuration mode by holding the button down until LED starts fast red flassing?

fixxx
2010-04-07, 21:54
Yes, tried that several times as well

edit

and it works! the UDAP script with the local ip added did the trick

Navier
2010-04-25, 07:06
I have managed to configure the Receiver without the Controller and it works flawlessly.

But, recently I want the receiver to work as a Bridge, but setting the parameter bridging=1 doesn't seems to work at all...
do I need to change other settings?
How about the wireless_mode set to 1 (AdHoc)? Would this do the trick?

Mnyb
2010-04-25, 07:18
I have managed to configure the Receiver without the Controller and it works flawlessly.

But, recently I want the receiver to work as a Bridge, but setting the parameter bridging=1 doesn't seems to work at all...
do I need to change other settings?
How about the wireless_mode set to 1 (AdHoc)? Would this do the trick?

No.

it can only bridge from ethernet to wifi

not wifi to ethernet (it's not an AP)

I think you must have the thing you want to brifge inserterd in the ehternet port ? but I may be wrong.

ottoinct
2010-05-26, 08:03
Help! I'm using udap_shell_1_0_0.exe and had no trouble setting up my old laptop (which I still have) to work with the squeezebox (the duet without remote). Now I'm trying to get it to discover the squeezebox on the new laptop and it does not find it. I've checked all the network configs, disabled firewalls, re-enabled firewalls, double-checked settings, and am stumped! Running XP on both laptops. Router, firewalls no different.

Any suggestions I should double check? Or options I should try? Thank you!

Friedl58
2010-06-20, 12:52
The Net-UDAP worked fine for me. I could configure my receiver. The only problem I have is that for the wireless_wpa_psk=(64 digits) only 55 digits are accepted, the other 9 are simply cut away.
Is this a known limitation or was ist my fault ?

Gerry123
2010-06-23, 00:25
The Net-UDAP worked fine for me. I could configure my receiver. The only problem I have is that for the wireless_wpa_psk=(64 digits) only 55 digits are accepted, the other 9 are simply cut away.
Is this a known limitation or was ist my fault ?

WPA can be anything as long as it's at least 8 chars. It's WEP that is 64 digits.

Friedl58
2010-06-23, 04:26
WPA can be anything as long as it's at least 8 chars. It's WEP that is 64 digits.

That is not true. WPA2 (AES) allows a PreSharedKey between 8 and 63 ASCII characters or a string of 64 hexadecimal digits.
http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access

But this does not solve my Problem.

flattermann
2010-06-23, 04:40
The Net-UDAP worked fine for me. I could configure my receiver. The only problem I have is that for the wireless_wpa_psk=(64 digits) only 55 digits are accepted, the other 9 are simply cut away.
Is this a known limitation or was ist my fault ?

Is there any special (=non ASCII) character at position 56?

Friedl58
2010-06-23, 07:48
No, the sequence 50 to 60 is gS:sgI=0h%

Friedl58
2010-06-23, 09:42
Must correct, the last 7 chrs are cut.

Friedl58
2010-06-25, 10:35
Is there a possibility to bring a SB Boom into Init mode and configure via UDAP ?

flattermann
2010-06-25, 12:55
Is there a possibility to bring a SB Boom into Init mode and configure via UDAP ?

If you hold the "+" button while powering on the Boom, it should do a factory reset and be in config mode.

pedro
2010-07-01, 07:44
As I was trying to configure a receiver using Net::UDAP, I encountered and ultimately resolved problems where I'd get the yellow light (cannot find network) or the blue light (found network, but cant find squeezecenter). This post may help those who encounter similar problems, particularly as my final solution contradicted one of the 'sample usage/configuration examples' on Robin's website (I'm not saying that his website is wrong - just the example that corresponded to my network configuration did not work for my particular case)

Firstly my network setup: Wireless, DHCP, WPA1, TKIP

The sample configuration from Robin's website did *NOT* work for me:
set interface=0 wireless_mode=0 wireless_region_id=14 wireless_SSID=MySSID wireless_wpa_on=1 wireless_keylen=1 wireless_wpa_psk="Top Secret!" lan_ip_mode=1 squeezecenter_address=192.168.1.150

Specifically, setting the wireless_keylen to 1 as suggested led to the yellow light problem. When I left the wireless_keylen as the default 0, it worked fine. This kinda makes sense to me because variation in the wireless_keylen is a characteristic of WEP networks (which can have a 64-bit or 128-bit key - or even 256-bit according to wiki), whereas WPA uses a 256-bit key. By setting wireless_keylen to 1, I guess I was trying to tell the receiver that my WPA network had a 128-bit key, which makes no sense (as far as I can tell from wiki).

Once that was solved, my set up worked for a bit, until my router decided to change the IP of my computer (which it was always liable to do as my set up is DHCP). That meant that the squeezebox light turned blue. To solve this I started again from factory settings, but this time didn't set the squeezecenter_address. Instead, I set the value of the squeezecenter_name field. This should be set to the name that you have given your Music Library in the Library Tab of the Squeezebox Server control panel. If you have not set this name, then the squeezecenter_name field should be set to the network name of the computer on which the squeezecenter server is running.

Another observation is that the Fields command of Net::UDAP suggests that wireless_wpa_cipher should be 2 for TKIP. However, whenever I set this to 2, it would always revert to 3, despite my router saying that my encryption type is TKIP.

So, I don't set any IP addresses during the Net::UDAP configuration, but once I had configured my receiver with Net::UDAP , I could use Net::UDAP again to verify that the squeezebox receiver had correctly attained all the necessary IP addresses automagically (for my DHCP set up and with certain Net::UDAP configuration settings).

My settings were as follows:
set interface=0 wireless_mode=0 wireless_region_id=14 wireless_channel=6 wireless_SSID=MySSID wireless_wpa_on=1 wireless_wpa_psk="Top Secret!" lan_ip_mode=1 squeezecenter_name=MYCOMPUTER

For me, even some of these settings were unnecessary (eg. wireless_wpa_on, lan_ip_mode and wireless_mode) because they were already set to the right values by factory presets. Note also that the values of some of the other parameters are vital (e.g. wireless_keylen=0), but I did not have to include them above because they were already set by the factory presets.

Sorry for the essay, but I included all my findings and inferences in case it helps others troubleshoot any problems they have.

(Edited 6 Jul with latest findings on squeezecenter_name)

Friedl58
2010-07-16, 06:03
Is there a possibility to bring a SB Boom into Init mode and configure via UDAP ?

I got answer fom Robin:

"Yes. Simply navigate to Squeezebox Setup, ie. as if you were about to
set up networking. Net-UDAP should be able to discover & configure the
Boom just like any other Squeezebox."

It worked like a charm, without any network patchcable.
Thank you !

robinbowes
2010-07-16, 06:06
I got answer fom Robin:

"Yes. Simply navigate to Squeezebox Setup, ie. as if you were about to
set up networking. Net-UDAP should be able to discover & configure the
Boom just like any other Squeezebox."

It worked like a charm, without any network patchcable.

I'm surprised it works without a network patch cable - did you already have the Boom configured to connect to a wireless network and then went into config mode?

R.

Friedl58
2010-07-16, 07:21
... - did you already have the Boom configured to connect to a wireless network and then went into config mode?

Yes the two Booms were already connected with another logical WLAN, parallel to my normal WLAN, but with a much shorter WPA-PSK.

Presumably this is the reason why I did not nead any patchcable.

I am very happy now, because I can use one WLAN for all my devices. And the WPA-PSK will never drive me crazy again.

I will have to find a way to tell the WPA-PSK to the PS3 of my childs then its perfect.

FreeMinded
2010-07-19, 13:16
Hi all

I just got myself a Receiver today to add to my existing SqueezeCenter Setup consisting of an Synology DS-107+ running the SB Server, a SB3 and SB Boom.

For setting up the brand new Receiver I connected (by wire) the laptop running Net-UDAP (on Kubuntu 10.04) and the receiver to a spare router. So they are on the same subnet. The receiver seems to be in init mode with the red light flashing slowly.
But running discover in Net::UDAP doesn't discover the device. Actually nothing at all seems to happen. I immediately get a new line with the UDAP> prompt. List shows an empty list.

As I'm running (K)ubuntu there shouldn't be a firewall in the way. I didn't find a way to test if the port 17784 is really open. netstat shows the port like this
udp 0 0 0.0.0.0:17784 0.0.0.0:*

Does anyone have an idea what could be wrong? Any help is appreciated.

Cheers,
FM

robinbowes
2010-07-19, 14:22
Please post your questions on the Net-UDAP mailing list:

http://lists.projects.robinbowes.com/mailman/listinfo/net-udap

Thanks,

R.

Friedl58
2010-07-20, 05:31
For setting up the brand new Receiver I connected (by wire) the laptop running Net-UDAP (on Kubuntu 10.04) and the receiver to a spare router.

First, be shure, to use the latest Revision, which is 1.0.x Rev.136
https://projects.robinbowes.com/Net-UDAP/trac/browser/branches/1.0.x

There is a --local-address option to the udap_shell.pl script which might solve your problem.

Use it like this:

udap_shell.pl --local-address a.b.c.d

Where a.b.c.d is the local address of your machine.

FreeMinded
2010-07-22, 04:05
First, be shure, to use the latest Revision, which is 1.0.x Rev.136
https://projects.robinbowes.com/Net-UDAP/trac/browser/branches/1.0.x

There is a --local-address option to the udap_shell.pl script which might solve your problem.

Use it like this:

udap_shell.pl --local-address a.b.c.d

Where a.b.c.d is the local address of your machine.

Great! Thanks for your help. The download link points to an older version. And with the --local-address argument it worked.

robinbowes
2010-07-22, 04:13
Great! Thanks for your help. The download link points to an older version. And with the --local-address argument it worked.

Which download link? Sounds like I need to update something...

R.

wahla21
2010-08-07, 07:00
Hi!

I am a pure novice in this.
I am trying to set up my Squeezebox receiver via NEt:Udap
It all goes fine and all values are good.
Then after reset the receiver only goes to Yellow light.
What am I doing wrong????

Cheers

robinbowes
2010-08-07, 07:19
Hi,

Yellow light means wireless is not connected [1].

Depending on the Net-UDAP version you are using, you may be having problems with the WEP key (if you are using WEP). If you are, try using the latest version on the 1.0.x branch [2]. If you are not using WEP, check your wireless key.

R.

[1] http://wiki.slimdevices.com/index.php/SBRFrontButtonAndLED
[2] http://projects.robinbowes.com/Net-UDAP/trac/browser/branches/1.0.x

wahla21
2010-08-07, 08:07
Hi and thanks!

But I am using WPA-PSK (TCIP) key.
What can it be?

Thanks

robinbowes
2010-08-07, 08:10
Can you post the commands you used to configure your SBR?

R.

wahla21
2010-08-07, 08:30
discover

conf 1

set interface=0 wireless_mode=0 wireless_region_id=14 wireless_SSID=MySSID wireless_wpa_on=1 wireless_keylen=1 wireless_wpa_psk="Top Secret!" lan_ip_mode=1 squeezecenter_address=192.168.1.150

save_data

reset

taken from here:
https://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage
Under Wireless, WPA1, DHCP

I obviously change the SSID to mine, and the password shall change too right? not keep "Top Secret!"
my password is all capital letters

wahla21
2010-08-07, 09:41
Ok,

Ive managed to get the receiver to blue, so its connected to my network.
What now? I cant find it with Squeezecommander...

If I add an additional server in Squeeze Commander, it asks for ip address and port. What port shall I put in for the receiver?



Shall I put in the MAC address of the receiver too?

Cheers

flattermann
2010-08-07, 09:59
192.168.1.150 is the address of your PC running SBS?

If yes, try to set both server addresses to this IP:

discover
conf 1
set server_address=192.168.1.150 squeezecenter_address=192.168.1.150
save_data

If you are using WLAN, you need to remove the LAN cable now and reboot
the Receiver.


If I add an additional server, it asks for ip address and port. What port shall I put in for the receiver?

You do not need to add the Receiver in SqueezeCommander!

Once the Receiver is connected to your local SBS, it will
automatically appear in SqueezeCommander.

Edit: I'm not sure if that changes anything, but I would also explicitly specify that you are using WPA1/PSK/TKIP:
set wireless_wpa_on=1 wireless_wpa_mode=1 wireless_wpa_cipher=1

robinbowes
2010-08-07, 10:09
192.168.1.150 is the address of *my* SqueezeboxServer!

You need to change that to the IP of *your* machine running Squeezeboxserver.

Squeezecommander should then see your SBR.

R.

05mattjax
2010-08-12, 14:17
Could somebody help me please. I am able to switch my player sucessfully to Squeezebox Server but when I try to switch it to mysqueezebox.com the player (SB Receiver) holds a blue light. I can then switch back to Squeezebox Server no probs. I feel it may have something to do with the Net Udap set up. I use iPeng on my Touch. By the way if I turn my Receiver off and on at the mains when the blue light is lit the player will then sucessfully connect to mysqueezebox.com.

Regards, Matt

flattermann
2010-08-12, 14:28
Could somebody help me please. I am able to switch my player sucessfully to Squeezebox Server but when I try to switch it to mysqueezebox.com the player (SB Receiver) holds a blue light. I can then switch back to Squeezebox Server no probs. I feel it may have something to do with the Net Udap set up. I use iPeng on my Touch. By the way if I turn my Receiver off and on at the mains when the blue light is lit the player will then sucessfully connect to mysqueezebox.com.

I've got the same problem with my Receiver (configured with Net::UDAP and SqueezeConfig).

I think it's because of the missing "credentials" field in the UDAP message.
(AFAIK Net::UDAP and SqueezeConfig both send 32 zero-bytes as "credentials"...)

Unfortunately, I don't know how to calculate the correct credentials...

05mattjax
2010-08-22, 13:13
I've got the same problem with my Receiver (configured with Net::UDAP and SqueezeConfig).

I think it's because of the missing "credentials" field in the UDAP message.
(AFAIK Net::UDAP and SqueezeConfig both send 32 zero-bytes as "credentials"...)

Unfortunately, I don't know how to calculate the correct credentials...

I actually got this working which was very strange. Was great that everyting worked without unplugging the receiver. But I have now switched to a wired connection )changed the settings in the received accordingly) and the problem is back? Very unhappy.

Hokie02
2010-08-28, 13:50
Is there any way to have the SBR look for the server (my laptop) by MAC ID and not by IP address? Since my router is DHCP my laptop tends to get different IP addresses from time to time and the SBR then fails to see it because it's looking for a specific IP. I can then use Net:UDAP to update the IP to current IP but I don't think I should have to do this every time! Any way to have it discover the server directly as long as it's on the network?

digital_davem
2010-09-01, 05:07
Hi

I posted this on the udap mailing list but repeated here in case it didn't get through

-------------------

Hi

I expect you are fed up with the same old ignorant newbie questions but I am at a lost as to what else to do.

I have just purchased the receiver only part of the Duet with a view to controlling it with my ipod touch. I understand this is possible with apps like the ipenq. I also understand that the official handset is required for setting up a new squeezebox receiver but that the net::udap utilility was created to emulate the handset and allow you to do it from your PC without the controller handset.

So. here's where I'm at:

1. I have broadband through O2, using a re-branded Thomson ethernet/wireless router/adsl box.

2. I have a PC running Windows Vista and Ubuntu linux connected to the router using a cable.

3. I have installed the Squeezecentre v7 software on the PC (under windows)

4. I downloaded and installed this UDAP windows executable: slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe

5. I connected the SBR to the O2 router using a cable

6. I used a browser on the PC to open the router admin page and check it could see the SBR. It does, althought the status field says "Inactive" (the status field for the connection to my PC says "Active").

7. I checked the light on the SBR. It is slowly flashing red about once every 7 or 8 secs

8. I ran the UDAP executable program on my PC. It opened a command line with the prompt Udap>.

9. I typed "discover" at the prompt

10. A bunch of messages appeared on the screen (about a dozen lines) saying something to the effect that the program expected something to be returned with a length of 6 characters but was getting 0 length responses.

11. Prompt re-appears

12. I typed "list"

13. Some underlined headings appeared on the screen but no further information

14. I'm completely stuck.

As you may have gathered, I am not TCP/IP networking savvy nor a programmer. I have tried to follow any forum posts or references I can google but most of the instructions, advice, tips and examples are somewhat over my head. I have dabbled with some rudimentary javascript and asp classic before but mainly I am a html/css coder and I have an IT team at work to deal with all the technical stuff, so although this Squeezebox stuff sounded straight forward enough at first sight, I very quickly got in above my head.

I would prefer not to have to buy the handset, so if someone could hold my hand I would be extremely grateful.

Thanks very much

Dave

Friedl58
2010-09-01, 05:21
4. I downloaded and installed this UDAP windows executable: slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe


I think you'd better use the latest available build 139 from the original source.
http://projects.robinbowes.com/Net-UDAP/trac/browser/branches/1.0.x

And then get it at:

Download in other formats:
* Zip Archive

Everything that is important, you can find here. http://projects.robinbowes.com/Net-UDAP/trac/wiki

Maybe you should use the local adress option
--local-address 192.168.1.5

And dont forget to install the Pearlinterpreter 4Win.

Mnyb
2010-09-01, 05:35
Also disable your firewall while doing the udap thing

digital_davem
2010-09-01, 05:39
Hi

Thanks for the quick reply.

I understood everything down to just before here...




Maybe you should use the local adress option
--local-address 192.168.1.5

And dont forget to install the Pearlinterpreter 4Win.

... after that it all goes hazy. I'm guessing you are talking about downloading source code and "compiling" or somesuch? Don't know how to do stuff like that, although it seems faintly reminiscent of what I did on a Pascal programming primer in about 1921 ;-)

digital_davem
2010-09-01, 12:42
Sorry for replying to my own message...

I've downloaded the source zip file.

I also downloaded and installed something called ActivePerl.

I strongly suspect that the downloads have to come together now to make an executable file. Don't know how to do this. I guessed run the perl.exe file and it rather unhelpfully gave me an empty dos box. Tips would be very handy right now...

Thanks

Dave


Hi

Thanks for the quick reply.

I understood everything down to just before here...



... after that it all goes hazy. I'm guessing you are talking about downloading source code and "compiling" or somesuch? Don't know how to do stuff like that, although it seems faintly reminiscent of what I did on a Pascal programming primer in about 1921 ;-)

Friedl58
2010-09-02, 01:35
No compiling necessary.
After the installation of ActivePearl your WinPC understands Pearl scripts.
Just run the Script udap_shell.pl --local-address 192.168.x.x (Your machines IP)
You can put the script wherever you want, but I suggest a simple path.
c:\scripts\

And again, everything that is important, you can find here. http://projects.robinbowes.com/Net-UDAP/trac/wiki

digital_davem
2010-09-02, 05:27
Hi

Thanks for this, however...

The first time I installed the perl program, the installation failed (in part). A directory called c:\perl was created and the files were installed but a lot error messages appeared saying that the install couldn't update the registry or path.

So I downloaded another installion based on an msi file and that seemed to work. I tested the install by typing perl -v (as it told me to do) at a prompt and it correctly identified the perl program.

This gave me confidence but according to the instructions on the active site, to run a perl script, I just click on it. When I tried this by clicking on the udap_shell program, all that happens is there is very brief flash of an empty dos box appearing then disappearing. And that's it. Very discouraging.

Your suggestion below is somewhat different, and any fledging confidence I had is disappearing rapidly. This is quite difficult to understand; everyone's help, whilst well-meaning is full of assumptions about background understanding. Are you are saying that I need to do more than just click on the .pl file to run it? Such as create another command line script file that contains the command "udap_shell.pl --local-address 192.168.x.x"? If so, how do I create such a file, what do I name it and how to I run it? Or have I completely misunderstood your advice.

Sorry about sounding so ignorant - but that really is my level of knowledge ;-)

ps

I think I need to do this step by step. One thing I would like to verify before messing with software is that my network is actually running properly. When I take the SBR out of the box and power it up and plug it in, I really expected some kind of feedback it is working. There is a red light on the front but it is not flashing like the instructions suggest. It is a steady light except it blinks once about every 10 seconds. Is this normal?

Secondly, when I plug any network device into my router via cable, a light on the ethernet socket on the router flashes to indicate there is traffic on the cable. When I plug the SBR in, there is no light. Is this normal for an unsetup box or does this indicate trouble.

Thirdly, when I access the administrator panel for the router, it has a screen called Home network that displays a picture of the router and all the wired and wireless devices connected to it. I can see an entry that I think is the squeeze centre software running on my main PC emulating a wireless device, but the router does not show an entry for the wired SBR. Is this also what you would expect for an unconfigured SBR or does it indicate trouble?





No compiling necessary.
After the installation of ActivePearl your WinPC understands Pearl scripts.
Just run the Script udap_shell.pl --local-address 192.168.x.x (Your machines IP)
You can put the script wherever you want, but I suggest a simple path.
c:\scripts\

And again, everything that is important, you can find here. http://projects.robinbowes.com/Net-UDAP/trac/wiki

TheLastMan
2010-09-02, 06:08
Such as create another command line script file that contains the command "udap_shell.pl --local-address 192.168.x.x"? If so, how do I create such a file, what do I name it and how to I run it? Or have I completely misunderstood your advice.

Open notepad
(from the Start menu, choose "Run" type notepad into the field and press return).

Type the following as the first line, replacing the "x.x" with the last two numbers in the ip address with the correct ones for the computer you are trying to connect to.


udap_shell.pl --local-address 192.168.x.x

For instance, in my case, this would be

udap_shell.pl --local-address 192.168.1.65
(if you don't know how to find the ip address of the computer, let us know)

Save the notepad document as udap.bat, note that you are replacing the .txt extension with .bat.

Save it to the same folder as udap_shell.pl

Double click on it and the command should run and open a Perl command line box. Follow Robin Bowes instructions from that point.

Let us know how you get on.

digital_davem
2010-09-02, 09:22
ps

I note you are running the same Naim 42/110 as I am (I'm also using the flatcap psu). Can't say it sounds any different to the japanese AV amp it replaced but it's fun to pretend be 1980s flat earth hardcore.

digital_davem
2010-09-02, 12:16
Hi

Reporting back.

It didn't work. When I clicked the udap.bat file, a dos box appeared on the screen for abot half a second, then vanished and that was it. While it was on the screen I could see that it was echoing back the command in the file but nothing very interesting happened.

Follow-up edit:

I have repeated the whole process on another computer (an xp netbook)and exactly the same thing happened - just a flash of dos prompt then nothing.


Open notepad
(from the Start menu, choose "Run" type notepad into the field and press return).

Type the following as the first line, replacing the "x.x" with the last two numbers in the ip address with the correct ones for the computer you are trying to connect to.


udap_shell.pl --local-address 192.168.x.x

For instance, in my case, this would be

udap_shell.pl --local-address 192.168.1.65
(if you don't know how to find the ip address of the computer, let us know)

Save the notepad document as udap.bat, note that you are replacing the .txt extension with .bat.

Save it to the same folder as udap_shell.pl

Double click on it and the command should run and open a Perl command line box. Follow Robin Bowes instructions from that point.

Let us know how you get on.

Friedl58
2010-09-02, 13:09
Well, no assumptions.

You downloaded the zipfile from here http://projects.robinbowes.com/Net-UDAP/trac/browser/branches/1.0.x

The zipfile contains three folders \doc \scripts \src

Extract them to C:\NetUDAP\

On the desktop make a rightclick -> New -> Link

Insert C:\NetUDAP\scripts\udap_shell.pl --local-address 192.168.1.65

The link shold now point to:
C:\NetUDAP\scripts\udap_shell.pl --local-address 192.168.1.65

Give the link a Name for instance (NetUDAP 1.0.x)and thats is it.
Now you can doubleclick on this link a DOSbox opens and the script executes.

Any further questions ? ;-)

digital_davem
2010-09-02, 14:06
Ok, that nearly worked and with a slight mo, it did.

The extraction process put the three folders several folders down in the structure so I cut and paste them back to the location of the shortcut. And it now runs the perl andgives me a udap> prompt.

That's a relief, passed the first hurdle.Thank you very much. Don't know why the previous method didn't work but I suppose it's just one moe mystery.

Now to hook up the cable and see if this version runs better than the exe.

Report back soon


Well, no assumptions.

You downloaded the zipfile from here http://projects.robinbowes.com/Net-UDAP/trac/browser/branches/1.0.x

The zipfile contains three folders \doc \scripts \src

Extract them to C:\NetUDAP\

On the desktop make a rightclick -> New -> Link

Insert C:\NetUDAP\scripts\udap_shell.pl --local-address 192.168.1.65

The link shold now point to:
C:\NetUDAP\scripts\udap_shell.pl --local-address 192.168.1.65

Give the link a Name for instance (NetUDAP 1.0.x)and thats is it.
Now you can doubleclick on this link a DOSbox opens and the script executes.

Any further questions ? ;-)

digital_davem
2010-09-03, 02:46
I now have the squeezebook set up on a wired connection and working. Thanks to everyone for your help. Next job is to re-do for wireless.

I must confess however that I am still baffled by the perl business. Creating a desktop shortcut to kick off the script worked while the other methods didn't. Why was this? Also, I did the setup using my XP netbook. When I tried to replicate the process on my vista PC it didn't work - same issue, a dos box flashed on the screen briefly (no Udap prompt) then terminated. Could it have anything to do with this IP address parameter that is on the end of the perl command? What does it do and why must it by 192.168.1.65?




Ok, that nearly worked and with a slight mo, it did.

The extraction process put the three folders several folders down in the structure so I cut and paste them back to the location of the shortcut. And it now runs the perl andgives me a udap> prompt.

That's a relief, passed the first hurdle.Thank you very much. Don't know why the previous method didn't work but I suppose it's just one moe mystery.

Now to hook up the cable and see if this version runs better than the exe.

Report back soon

Friedl58
2010-09-03, 03:31
What does it do and why must it by 192.168.1.65?

It hast to be the IP of the machine, the script is working on. Working on another machine with another IP you must use the IP of that certain machine.

To find out, follow this instruction:

On the Desktop klick Start -> Run
Write-> command
and press Enter/or click OK
A DOSbox opens.
At the commandline write-> ipconfig /all
Then press enter.
Now you all the informations about network config are revealed, including the machines IP.

digital_davem
2010-09-03, 05:13
The script was running on my laptop. How did you know what the right ip address was?

I did guess that the parameter might change with machine so I tried using the PC's ip address but it didn't work. Are there still issues with UDAP running on Vista?



It hast to be the IP of the machine, the script is working on. Working on another machine with another IP you must use the IP of that certain machine.

To find out, follow this instruction:

On the Desktop klick Start -> Run
Write-> command
and press Enter/or click OK
A DOSbox opens.
At the commandline write-> ipconfig /all
Then press enter.
Now you all the informations about network config are revealed, including the machines IP.

Friedl58
2010-09-03, 06:39
Are there still issues with UDAP running on Vista?

Maybe, but I am hooked on XPPro, because of this Vista sideeffects of the UAC.

digital_davem
2010-09-06, 06:03
Job finished!

SBR is now running nicely wirelessly and controlled by Ipeng on an Ipod.

Only (insignificant) glitch is that when I stop playing music there is no obvious way to switch it off. And when I later return to play more, the ipod won't work until I power down the SBR and re-start it. Takes only a couple of seconds, so not important but if there is an elegant way around this, it would be good to know.

Once again, thanks to everyone for all the advice.

Next challenge is how to get music organised.

Cheers

Dave



I now have the squeezebook set up on a wired connection and working. Thanks to everyone for your help. Next job is to re-do for wireless.

I must confess however that I am still baffled by the perl business. Creating a desktop shortcut to kick off the script worked while the other methods didn't. Why was this? Also, I did the setup using my XP netbook. When I tried to replicate the process on my vista PC it didn't work - same issue, a dos box flashed on the screen briefly (no Udap prompt) then terminated. Could it have anything to do with this IP address parameter that is on the end of the perl command? What does it do and why must it by 192.168.1.65?

roloenni
2010-10-06, 23:31
I have connected the SBR to my network with wire.
After having set up the SBR with UDAP I am able to control it with a laptop connected to the network with wire.
I am not able to control the SBR if the laptop is connected to the network with wi-fi.
I have turned off the firewall and antivirus app but the result is the same.
Do I need to set up the SBR as wireless to control it from a wi-fi device?

My goal is to hook up the SBR with wire and control it with a wi-fi device.

robinbowes
2010-10-07, 05:46
Do I need to set up the SBR as wireless to control it from a wi-fi device?

No, that should not make any difference.

As long as SqueezeboxServer can communicate with the SBR and your laptop can communicate with SqueezeboxServer then it will work just fine.

R.

jamesg1979
2010-10-15, 12:15
I seem to be stuck at the first hurdle!
Extracted the zip file to c:/ changed directory on CMD cd c:/
Run the "scripts/udap_shell.pl" and get 'scripts' is not recognised as an internal or external command...

Any ideas?

jamesg1979
2010-10-16, 13:53
OK now got a bit further on.
Downloaded the exe.
Ran all the commands, list shows all the items that I've added.
Reset resets the SBR but then goes straight back into config mode..

Any ideas?

jgctx
2010-11-27, 14:50
Ok I am not a programmer but I am in the need of help.

I own a squeezebox portable unit that I use an iphone app called ipeng to control over a wireless network and via the cellular network. It works great so I bought the squeezebox receiver to use on my home stereo. I thought I would be able to use ipeng to control it but that is not an option. I also tried squeezecenter to control, does not work.

I then found this forum, but I am not a programmer and need help understand how to do this via a computer. It does not look easy or simple. I assume there is not a gui interface to activate the receiver so I can use a iphone/ipad app to access it. Any help would be great.

Thanks, JC

garym
2010-11-27, 15:58
Ok I am not a programmer but I am in the need of help.

I own a squeezebox portable unit that I use an iphone app called ipeng to control over a wireless network and via the cellular network. It works great so I bought the squeezebox receiver to use on my home stereo. I thought I would be able to use ipeng to control it but that is not an option. I also tried squeezecenter to control, does not work.

I then found this forum, but I am not a programmer and need help understand how to do this via a computer. It does not look easy or simple. I assume there is not a gui interface to activate the receiver so I can use a iphone/ipad app to access it. Any help would be great.

Thanks, JC

can't help on your main question, but once you do get the receiver setup on your home system you WILL be able to use ipeng to control. But correct, you'll need either Net::UDAP or a SB CONTROLLER to initally setup the receiver.

flattermann
2010-11-28, 07:29
I own a squeezebox portable unit that I use an iphone app called ipeng to control over a wireless network and via the cellular network. It works great so I bought the squeezebox receiver to use on my home stereo. I thought I would be able to use ipeng to control it but that is not an option. I also tried squeezecenter to control, does not work.

Well, you need a 3rd party software (Net::UDAP [PC] or SqueezeConfig [Android]) to setup the receiver once.

Once it's initially setup, you can use any controller software (e.g. iPeng) to control the Receiver.

I'll try to guide you through the setup process, but I need some information for that:
(With "PC" I mean the PC that you'll use to setup the Receiver. It may be the same computer as your SqueezeBoxServer.)

- Which OS are you using on your PC (Windows, Linux, Mac)?
- How do you want to configure your Receiver (LAN or WLAN)?
- For WLAN, which kind of encryption do you want to use (WEP, WPA, WPA2)?
- What's the IP address of your PC?
- What's the IP address of your SqueezeBoxServer?

Squeezemenicely
2010-12-01, 15:23
Hi Flattermann,

I am completely new to Squeezebox, got my receiver today. Already lovin it.

I got it running via lan using UDAP, but really want to use wifi.

I have tried many times with different instructions, but I am simply too stupid and cannot get it to work.

I am running Squeezeserver on my Synology Nas and my wifi network is secured with WPA2.


BTW, I am using iPeng for iPhone.

Hope you can help me, maybe I can even send you all my details via PM?

robinbowes
2010-12-01, 15:45
You could always try the "official" Net-UDAP mailing list:

http://lists.projects.robinbowes.com/mailman/listinfo/net-udap

R.

Squeezemenicely
2010-12-01, 16:05
[QUOTE=robinbowes;592103]You could always try the "official" Net-UDAP mailing list:

/QUOTE]


Thanks, still hoping someone can help me here, I am sure there have already been hundreds of Receivers been set up with WPA2 from this forum.

If I get no answer I will try the list.

This is the line I used for the setup:

set interface=0 server_address=192.168.178.40 wireless_SSID=audio wireless_region_id=14
wireless_wpa_cipher=1 wireless_wpa_mode=2 wireless_wpa_on=1 wireless_wpa_psk=48523332521

flattermann
2010-12-01, 16:20
Thanks, still hoping someone can help me here, I am sure there have already been hundreds of Receivers been set up with WPA2 from this forum.

If I get no answer I will try the list.

Ok, if you managed to configure the receiver for LAN mode, that means that Net:UDAP is already working for you. Great!

What happens if you use the the WPA2 config commands from Robin's official Wiki page?
http://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage

set interface=0 wireless_mode=0 wireless_region_id=14 wireless_SSID=MySSID wireless_wpa_on=1 wireless_wpa_mode=2 wireless_wpa_cipher=3 wireless_wpa_psk="Top Secret!" lan_ip_mode=1 squeezecenter_address=192.168.1.150

(Remember that the Receiver must be connected to your LAN while using Net:UDAP, even if you want to setup a WLAN connection!)

Replace MySSID, the PSK and 192.168.1.150 by the actual values of your network.

Squeezemenicely
2010-12-01, 16:26
What happens if you use the the WPA2 config commands from Robin's official Wiki page?



Hi,
I had also tried that config string, also did not work. I cannot see the receiver connecting to my router (fritzbox)

I also repeated the string a couple of times to make sure I had not made mistakes.

Any idea?

Squeezemenicely
2010-12-01, 16:29
my info that needs to be put into the receiver is:


SSID: Xberger
PSK: 453226982
WPA2
Squeezecenter: 192.168.178.40

flattermann
2010-12-01, 16:33
Hi,
I had also tried that config string, also did not work. I cannot see the receiver connecting to my router (fritzbox)

I also repeated the string a couple of times to make sure I had not made mistakes.

Any idea?

Hmm, what's the color of the Receiver's LED when you use this string?

(Remember to remove the LAN cable and restart the receiver after using the "save_data" command in NetUDAP.)

Squeezemenicely
2010-12-01, 16:35
Hmm, what's the color of the Receiver's LED when you use this string?

(Remember to remove the LAN cable and restart the receiver after using the "save_data" command in NetUDAP.)

It was green. I had also taken off the Lan cable - but maybe after I had restarted, I am not sure anymore. I will retry tomorrow.

So the string from the wiki is the right one?

Thanks for your help.

flattermann
2010-12-01, 16:39
It was green. I had also taken off the Lan cable - but maybe after I had restarted, I am not sure anymore. I will retry tomorrow.

So the string from the wiki is the right one?

Thanks for your help.

Yes, IIRC, I used the same string for my setup.

Please try this string again and tell us if it worked:

set interface=0 wireless_mode=0 wireless_region_id=14 wireless_SSID=Xberger wireless_wpa_on=1 wireless_wpa_mode=2 wireless_wpa_cipher=3 wireless_wpa_psk="453226982" lan_ip_mode=1 squeezecenter_address=192.168.178.40

I can't try it with my Receiver right now, because I'm not at home, but I can also re-check it tomorrow, if it still does not work for you.

PS: Green is good (at least better than yellow). That means that the Receiver joined your WLAN successfully, but was unable to get an IP via DHCP. In this case, using a static IP may do the trick.

Squeezemenicely
2010-12-02, 03:03
Please try this string again and tell us if it worked:





It worked! Thankyou so much!!!!

I put in the PSK without the "" before, since that is how it was done in the other instruction pdf I had found, that had been released by the magazine AUDIO.

I am glad I had not given up and asked for help here.

It is really easy setting the receiver up, if you have the right instructions.

So for all new squeezers out there trying to set up their receivers, only go by the wiki and ignore all other info, which might be outdated by now.

flattermann
2010-12-02, 08:28
It worked! Thankyou so much!!!!

I put in the PSK without the "" before, since that is how it was done in the other instruction pdf I had found, that had been released by the magazine AUDIO.

I am glad I had not given up and asked for help here.

It is really easy setting the receiver up, if you have the right instructions.

So for all new squeezers out there trying to set up their receivers, only go by the wiki and ignore all other info, which might be outdated by now.

Probably, a PSK without quotes is interpreted as hexadecimal value, but you have entered the PSK in your router as string.

Anyway, good to hear that it's working now!