Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18
  1. #11
    Junior Member
    Join Date
    Dec 2018
    Posts
    5
    Quote Originally Posted by mherger View Post
    >
    mysqueezebox.com is being used for artwork resizing, internet radio, and
    probably to get some of the other menus, too.
    Is it possible to stop these connections and just use a local LMS server (7.9.2 - 1542807489)?

    I've disabled every option that dealt with mysqueezebox.com on my LMS; I've also disabled a plugin providing mysqueezebox services: but the devices (all Radios) keep calling home...
    Code:
    > ec2-52-215-52-41.eu-west-1.compute.amazonaws.com:9000     <=> squeezebox02.XXXXXX:42445
    > ec2-52-208-195-129.eu-west-1.compute.amazonaws.com:9000   <=> squeezebox03.XXXXXX:39974
    > ec2-52-215-52-41.eu-west-1.compute.amazonaws.com:9000     <=> squeezebox01.XXXXXX:58582

  2. #12
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,118

    All my devices talk port 9000 outbound to Amazon AWSservers??

    >> mysqueezebox.com is being used for artwork resizing, internet radio, and
    >> probably to get some of the other menus, too.

    >
    > Is it possible to stop these connections and just use a local LMS server
    > (7.9.2 - 1542807489)?


    Yes, LMS 7.9 has a --nomysqueezebox parameter. Depending on what OS
    you're using this is more or less complicated to implement.


    > > ec2-52-215-52-41.eu-west-1.compute.amazonaws.com:9000 <=> squeezebox02.XXXXXX:42445
    > > ec2-52-208-195-129.eu-west-1.compute.amazonaws.com:9000 <=> squeezebox03.XXXXXX:39974
    > > ec2-52-215-52-41.eu-west-1.compute.amazonaws.com:9000 <=> squeezebox01.XXXXXX:58582


    That's a bit odd, as port 9000 would likely be a player connection, not
    LMS. Are squeezebox0X your various players? Above parameter won't help
    in that case.

    --

    Michael

  3. #13
    Senior Member pippin's Avatar
    Join Date
    Oct 2007
    Location
    Berlin
    Posts
    14,524
    Quote Originally Posted by mherger View Post

    That's a bit odd, as port 9000 would likely be a player connection, not
    LMS. Are squeezebox0X your various players? Above parameter won't help
    in that case.
    Yes, he wrote that these are the players.
    Probably an edited post again?
    ---
    learn more about iPeng, the iPhone and iPad remote for the Squeezebox and
    Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
    at penguinlovesmusic.com
    New: iPeng 9, the Universal App for iPhone, iPad and Apple Watch

  4. #14
    Junior Member
    Join Date
    Dec 2018
    Posts
    5
    Quote Originally Posted by mherger View Post
    Yes, LMS 7.9 has a --nomysqueezebox parameter.
    I'm using that option: it it set into /etc/default/logitechmediaserver
    Code:
    SLIMOPTIONS="--nomysqueezebox"
    Quote Originally Posted by mherger View Post
    Are squeezebox0X your various players? Above parameter won't help
    in that case.
    Yes, all Squeezebox Radios

    Quote Originally Posted by mherger View Post
    That's a bit odd, as port 9000 would likely be a player connection, not LMS.
    Indeed.
    I don't seem to be able to block those connections with the firewall: I will investigate further.

    Last but not least, I don't seem to be able to ssh into the players anymore: is there a way to reset the password or public key without a factory reset?

  5. #15
    Junior Member
    Join Date
    Dec 2018
    Posts
    5
    Finally I was able to determine the domain related to those IP addresses:

    Code:
    Name:      squeezenetwork.com
    Address 1: 34.244.221.118
    Address 2: 34.243.157.154
    Address 3: 52.208.195.129
    Address 4: 52.215.52.41
    Address 5: 34.247.12.245
    Address 6: 34.245.154.142
    It looks like I could stop the connections by adding the domain to a blacklist:
    Code:
    Server:		127.0.0.1
    Address:	127.0.0.1#53
    
    ** server can't find squeezenetwork.com: NXDOMAIN
    ** server can't find squeezenetwork.com: NXDOMAIN
    (...still not clear how they could cross the firewall...)

    It also looks like the players are "flooding" the local DNS server with many request per second: can this be avoided?

  6. #16
    Junior Member
    Join Date
    Dec 2018
    Posts
    5
    Quote Originally Posted by cris- View Post
    It also looks like the players are "flooding" the local DNS server with many request per second: can this be avoided?
    I've configured the DNS server to respond with the ip address of the local LMS when baby.squeezenetwork.com and www.mysqueezebox.com are requested;
    requests for other subdomains return a NXDOMAIN.
    This seems to have stopped the flooding.

    PS: also solved the problem with the ssh password by factory resetting...

  7. #17
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,118

    All my devices talk port 9000 outbound to Amazon AWSservers??

    > I've configured the DNS server to respond with the ip address of the
    > local LMS when baby.squeezenetwork.com and www.mysqueezebox.com are
    > requested;

    BTW: I believe that disabling all mysb.com interaction doesn't help
    anyone. One of the reasons why mysb.com is still alive is the fact that
    I can prove there's still a huge number of installations out there...

    Some calling home actually is useful.

    --

    Michael

  8. #18
    Junior Member
    Join Date
    Dec 2018
    Posts
    5
    Quote Originally Posted by mherger View Post
    >Some calling home actually is useful.
    Just an exercise for my paranoid-self

    I already start missing the album artworks...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •