Re: [SlimDevices: SqueezeCenter] Force squeezeboxserver to bind to specific interface using Linux named netns

2018-10-31 Thread bpa


aidy_w wrote: 
> Is there a reason why the squeeboxserver does not integrate the same
> functions as the controller for the DUET products. Specifically UDAP. I
> have 2 DUET receivers and recently the controller failed, well not
> failed exactly but the only way I have it working is on the bench with
> wires hanging out of  it. If I hard reset the DUET receiver, the
> squeezeboxserver does not attempt to connect and configure them. Is this
> by design. It would be very useful if it did. In effect, without the
> controller the receivers become unusable.

The older players are quite dumb when running parametrs are controlled
by Squeezeboxserver  but the basic firmware sets up comms (i.e.
Ethernet, wireless) to Squeezeboxserver.  
Once basic comms are working, player on power up issues a Broadcast UDP
packet to find all the Squeezeboxservers available - there may be more
than one. 

With players with display such as SB-1/2/3, Boom - the display is used
to allow users to setup basic network params and to choose a LMS if more
than one.
Receiver has no screen so Duet controller an adhoc WiFI to setup
Receiver so that it communicate with a designated Squeezeboxserver.

the Net::UDAP script allows a user to setup a receiver - the network
paramater and to which Squeezeboxserver to connect.



bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=109668

___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter


Re: [SlimDevices: SqueezeCenter] Force squeezeboxserver to bind to specific interface using Linux named netns

2018-10-31 Thread slartibartfast


aidy_w wrote: 
> Dh, that works. My most sincere apologies. I had indeed made a
> simple mistake. I slipped a space between the directive and the address,
> because the daemon started even with the space in place, I assumed it
> was simply not responding I failed then to check netstat, which
> under this condition shows no process listening on port 9000. Running
> daemon no binding. Dh
> 
> So, finally, it was simple after all. Now I feel pretty stupid.
> 
> Having said that, I will stick with what I have done, there is a subtle
> reason. Because the netns is attached to a bridge in the root netns, its
> IP address is different and totally independent of the interface withitn
> the root netns. This means I don't have to consider it in any iptables
> rules with regard to traffic between it and its clients. It has clear
> unobstructed L2 visibility of my LAN. As its in the same subnet as all
> my other LAN traffic, my rules on the internet link can also remain
> exactly the same. 
> 
> It has been an interesting exercise.
> 
> As I probably have your attention, for the wrong reasons I'm
> sure.please allow me to ask another quick question. I wont open
> another topic just in case I am again being so dumb :/
> Is there a reason why the squeeboxserver does not integrate the same
> functions as the controller for the DUET products. Specifically UDAP. I
> have 2 DUET receivers and recently the controller failed, well not
> failed exactly but the only way I have it working is on the bench with
> wires hanging out of  it. If I hard reset the DUET receiver, the
> squeezeboxserver does not attempt to connect and configure them. Is this
> by design. It would be very useful if it did. In effect, without the
> controller the receivers become unusable.
> 
> Sorry again for wasting your time.
> Thanks for the help.
> AidanThis is the thread for net udap
https://r.tapatalk.com/shareLink?url=https%3A%2F%2Fforums%2Eslimdevices%2Ecom%2Fshowthread%2Ephp%3Ft%3D57861_tid=57861_fid=813_type=t

Sent from my SM-G900F using Tapatalk





slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View this thread: http://forums.slimdevices.com/showthread.php?t=109668

___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter


Re: [SlimDevices: SqueezeCenter] Force squeezeboxserver to bind to specific interface using Linux named netns

2018-10-31 Thread Mnyb

aidy_w wrote: 
> Dh, that works. My most sincere apologies. I had indeed made a
> simple mistake. I slipped a space between the directive and the address,
> because the daemon started even with the space in place, I assumed it
> was simply not responding I failed then to check netstat, which
> under this condition shows no process listening on port 9000. Running
> daemon no binding. Dh
> 
> So, finally, it was simple after all. Now I feel pretty stupid.
> 
> Having said that, I will stick with what I have done, there is a subtle
> reason. Because the netns is attached to a bridge in the root netns, its
> IP address is different and totally independent of the interface withitn
> the root netns. This means I don't have to consider it in any iptables
> rules with regard to traffic between it and its clients. It has clear
> unobstructed L2 visibility of my LAN. As its in the same subnet as all
> my other LAN traffic, my rules on the internet link can also remain
> exactly the same. 
> 
> It has been an interesting exercise.
> 
> As I probably have your attention, for the wrong reasons I'm
> sure.please allow me to ask another quick question. I wont open
> another topic just in case I am again being so dumb :/
> Is there a reason why the squeeboxserver does not integrate the same
> functions as the controller for the DUET products. Specifically UDAP. I
> have 2 DUET receivers and recently the controller failed, well not
> failed exactly but the only way I have it working is on the bench with
> wires hanging out of  it. If I hard reset the DUET receiver, the
> squeezeboxserver does not attempt to connect and configure them. Is this
> by design. It would be very useful if it did. In effect, without the
> controller the receivers become unusable.
> 
> Sorry again for wasting your time.
> Thanks for the help.
> Aidan

for configuration of a reciever without the controller there is the net
udap script by robin bowes there is a whole tread about that .
And for a time there was an Android app , but itÂ’s old and may not be
that easy to get going again.




Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3
sub.
Bedroom/Office: Boom
Kitchen: Touch + powered Fostex PM0.4
Misc use: Radio (with battery)
iPad1 with iPengHD & SqueezePad
(spares Touch, SB3, reciever ,controller )
server HP proliant micro server N36L with ClearOS Linux

http://people.xiph.org/~xiphmont/demo/neil-young.html

Mnyb's Profile: http://forums.slimdevices.com/member.php?userid=4143
View this thread: http://forums.slimdevices.com/showthread.php?t=109668

___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter


Re: [SlimDevices: SqueezeCenter] Force squeezeboxserver to bind to specific interface using Linux named netns

2018-10-31 Thread slartibartfast


aidy_w wrote: 
> Hi,
> Hey sorry, I didn't intend to upset anyone. Yes, I suppose when I wrote
> my initial post I was somewhat frustrated. 
> 
> Having said this, I found both the bindAddress and AllowedHosts in the
> prefs file and I tried setting them as required. I tried setting them
> individually and I tried setting them to simultaneously, but nothing
> worked. In fact sometimes the daemon would not start after making
> changes to these setting even when the configured values where perfectly
> ligitimate. Still other times the daemon would start and even though the
> bind address and allowed hosts where set correctly for my network. The
> daemon would still log messages saying it would not respond to 'non'
> local hosts. The traffic to and from the built in http server was going
> directly between my local subnet and the server, both ends clealry using
> private address space. netstat was showing the daemon always bound to
> 0.0.0.0:9000 never to any specific address However the servers log file
> was constantly saying it was replying to the address on my public
> Internet interface.
> 
> Thenas I said. if I brought down the public interface. Then started
> the daemon, it would start and be happy to talk to internal clients, it
> would continue this way so long as the public interface was down. If I
> re-enabled the public interface, it would carry on working for a short
> time, but then within 10-15sec it would switch back to rejecting traffic
> with 403 forbidden.
> 
> I really did try.
> 
> So having gone through this quite thoroughly, I gave up and put it in a
> netns. Now it works.
> 
> If you like and you think I have made some mistake. I will test a little
> again. But I already spent a day messing with the standard install with
> no luck. The another day getting netns to work. So I'm kinda resigned to
> this config now. In fact I'm somewhat happier with it as I know the
> daemon is fully constrained. I'm not normally paranoid, but when a
> server starts and does not seemingly do what you tell it to do, I do ask
> what else might it be doing.
> 
> It works just fine inside a netns. Yes its complicated but at least I
> gained a little useful knowledge. :)
> 
> Over to you.
> AidanIn all the things you tried did you try adding the httpaddr parameter to

/etc/default/logitechmediaserver

Sent from my SM-G900F using Tapatalk





slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View this thread: http://forums.slimdevices.com/showthread.php?t=109668

___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter


Re: [SlimDevices: SqueezeCenter] Force squeezeboxserver to bind to specific interface using Linux named netns

2018-10-30 Thread DJanGo


aidy_w wrote: 
> I did read your comment on this, but for the life of me I could not find
> this... you referenced files in your forum post that simply do not exist
> on my install, and this was a clean install direct from the .deb file of
> 7.9.2. So Yes I would have done if it was possible to locate it. Maybe
> you would like to give some better instruction as I agree this is far
> more complex.

Hi remember Michael has a lot more than 1 or 2 distrubutions in mind and
he may make some minor mistakes.

But you only had to look into some answers for your 'earlier posts'
(https://forums.slimdevices.com/showthread.php?108603-Access-to-settings-pages-is-now-restricted=923879=1#post923879)
to sort it out.
cheers



DJanGo's Profile: http://forums.slimdevices.com/member.php?userid=1516
View this thread: http://forums.slimdevices.com/showthread.php?t=109668

___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter


Re: [SlimDevices: SqueezeCenter] Force squeezeboxserver to bind to specific interface using Linux named netns

2018-10-30 Thread slartibartfast


aidy_w wrote: 
> I did read your comment on this, but for the life of me I could not find
> this... you referenced files in your forum post that simply do not exist
> on my install, and this was a clean install direct from the .deb file of
> 7.9.2. So Yes I would have done if it was possible to locate it. Maybe
> you would like to give some better instruction as I agree this is far
> more complex.
> 
> Having said this, I was frustrated by the fact the the daemon always
> decided to attempt to attach to the public interface every time I
> upgraded. I seem to have no control over this. Another point being, that
> now I can control traffic much better, I can isolate the traffic, assign
> clear A records against the service in bind, filter with tshark more
> easily and better understand exactly what the server is doing when it
> communicates with its clients, manage effectively any exchange between
> the daemon and other services on my server etc.. There are many reasons
> it is useful, but yes its complicated. But its clean.
> 
> 
> As a final note that I did not include in the original post if you want
> to enable the daemon at boot then you should add to the bottom of the
> squeezeboxserver_in_netns.service file.
> 
> [Install]
> WantedBy=multi-user.target
> WantedBy=systemd-networkd.target
> 
> then you can run:
> 
> systemctl enable squeezeboxserver_in_netns
> 
> and the service will run at boot time once the network is up and
> multi-user environment available
> 
> AidanThis reply told you which file to modify.

https://forums.slimdevices.com/showthread.php?p=923879

Sent from my SM-G900F using Tapatalk





slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View this thread: http://forums.slimdevices.com/showthread.php?t=109668

___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter


Re: [SlimDevices: SqueezeCenter] Force squeezeboxserver to bind to specific interface using Linux named netns

2018-10-29 Thread mherger


Looks like a rather complicated way to do what applying the --httpaddr
parameter would have done...



Michael

http://www.herger.net/slim-plugins - Spotty, MusicArtistInfo

mherger's Profile: http://forums.slimdevices.com/member.php?userid=50
View this thread: http://forums.slimdevices.com/showthread.php?t=109668

___
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter