Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 6 FirstFirst 12345 ... LastLast
Results 21 to 30 of 52
  1. #21
    Senior Member
    Join Date
    Feb 2011
    Location
    Cheshire, UK
    Posts
    4,158
    Quote Originally Posted by d6jg View Post
    i think the traceroutes are indicating a routing failure. Iĺd suggest running some further longer term jobs and then referring the results to your ISP.
    Note also that the DNS resolves a different address for mySb.com on the final traceroute and the only one that works.
    VB2.4 storage QNAP TS419p (NFS)
    Living Room - Joggler & SB3 -> Onkyo TS606 -> Celestion F20s
    Office - Pi3+Sreen -> Sony TAFE320 -> Celestion F10s / Pi2+DAC & SB3 -> Onkyo CRN755 -> Wharfedale Modus Cubes
    Dining Room -> SB Boom
    Kitchen -> UE Radio (upgraded to SB Radio)
    Bedroom (Bedside) - Pi2+DAC ->ToppingTP21 ->AKG Headphones
    Bedroom (TV) - SB Touch ->Sherwood AVR ->Mordaunt Short M10s
    Everything controlled by iPeng

  2. #22
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    17,906
    Could there be an IPv6 issue here - I had to turn off IPv6 DNS lookup because I kept getting timeout from my ISP. It meant every lookup was slow.

  3. #23
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    17,906
    Quote Originally Posted by Learnincurve View Post

    telnet bpa-code.github.io 443
    Trying 185.199.109.153...
    Connected to bpa-code.github.io.
    Escape character is '^]'.

    Could this point to a perl ssl issue? How do I check my perl modules?
    Testing 443 connectivity is not enough. I don;t know details but have seen many SSL failures/timeouts.

    SSL/TSL timeout is not just connect to a port but multistep negotiation of SSL/TSL version and exchange of stuff like certificates.

  4. #24
    Senior Member
    Join Date
    Sep 2015
    Posts
    156
    Thanks for all the good suggestions and well spotted d6jg regarding the IP address. I'll start with a more thorough investigation of DNS on the affected host, compared with the working one and take it from there.

  5. #25
    Senior Member
    Join Date
    Feb 2011
    Location
    Cheshire, UK
    Posts
    4,158
    Quote Originally Posted by Learnincurve View Post
    Thanks for all the good suggestions and well spotted d6jg regarding the IP address. I'll start with a more thorough investigation of DNS on the affected host, compared with the working one and take it from there.
    I'm not saying the DNS lookup is wrong - I don't think it is - I think mySB.com operates on Amazon cloud on a number of different servers which are probably load balanced.
    What I'm saying is that the affected host is getting a correct DNS address but that either the route to that server is broken or possibly that the target server is not responding correctly.
    Try changing the DNS servers on the affected host to another public non caching DNS server e.g. 8.8.8.8 or 8.8.4.4 and see if it then resolves to a different mySB server which you can traceroute to successfully.
    VB2.4 storage QNAP TS419p (NFS)
    Living Room - Joggler & SB3 -> Onkyo TS606 -> Celestion F20s
    Office - Pi3+Sreen -> Sony TAFE320 -> Celestion F10s / Pi2+DAC & SB3 -> Onkyo CRN755 -> Wharfedale Modus Cubes
    Dining Room -> SB Boom
    Kitchen -> UE Radio (upgraded to SB Radio)
    Bedroom (Bedside) - Pi2+DAC ->ToppingTP21 ->AKG Headphones
    Bedroom (TV) - SB Touch ->Sherwood AVR ->Mordaunt Short M10s
    Everything controlled by iPeng

  6. #26
    Senior Member
    Join Date
    Feb 2011
    Location
    Cheshire, UK
    Posts
    4,158
    Quote Originally Posted by d6jg View Post
    I'm not saying the DNS lookup is wrong - I don't think it is - I think mySB.com operates on Amazon cloud on a number of different servers which are probably load balanced.
    What I'm saying is that the affected host is getting a correct DNS address but that either the route to that server is broken or possibly that the target server is not responding correctly.
    Try changing the DNS servers on the affected host to another public non caching DNS server e.g. 8.8.8.8 or 8.8.4.4 and see if it then resolves to a different mySB server which you can traceroute to successfully.
    mysqueezebox.com has the following DNS servers - for testing you could point your affected host at one of them but it will only resolve mysqueezebox.com addresses

    dns.usw.mysqueezebox.com
    dns.use.mysqueezebox.com
    dns.euw.mysqueezebox.com

    If you point at that and lookup www.mysqueezebox.com it will resolve differently on each lookup

    Name:  2019-11-14 10_02_23-Command Prompt - nslookup.png
Views: 42
Size:  17.0 KB
    VB2.4 storage QNAP TS419p (NFS)
    Living Room - Joggler & SB3 -> Onkyo TS606 -> Celestion F20s
    Office - Pi3+Sreen -> Sony TAFE320 -> Celestion F10s / Pi2+DAC & SB3 -> Onkyo CRN755 -> Wharfedale Modus Cubes
    Dining Room -> SB Boom
    Kitchen -> UE Radio (upgraded to SB Radio)
    Bedroom (Bedside) - Pi2+DAC ->ToppingTP21 ->AKG Headphones
    Bedroom (TV) - SB Touch ->Sherwood AVR ->Mordaunt Short M10s
    Everything controlled by iPeng

  7. #27
    Senior Member
    Join Date
    Sep 2015
    Posts
    156
    Quote Originally Posted by d6jg View Post
    mysqueezebox.com has the following DNS servers - for testing you could point your affected host at one of them but it will only resolve mysqueezebox.com addresses

    dns.usw.mysqueezebox.com
    dns.use.mysqueezebox.com
    dns.euw.mysqueezebox.com

    If you point at that and lookup www.mysqueezebox.com it will resolve differently on each lookup

    Name:  2019-11-14 10_02_23-Command Prompt - nslookup.png
Views: 42
Size:  17.0 KB

    There do seem to be multiple issues, or at least multiple levels.

    One is the DNS, which, as I said before, I can't get my head around on Ubuntu 18.10: It uses Netplan, but the conf file refers to the old NetworkManager, which refers to something else again (I can't remember what now). I gave up trying to find the .conf files at that point and just did a systemd-resolv, which indicated that DNS was resolution was coming from my LAN-wide DNS (which was expected). There is almost certainly caching going on, both locally, and on my LAN-wide DNS, but the lookups seem to be consistent for each host, tho not between hosts. One explanation would be my local cache, and another that the LAN-DNS is screwed, and the hosts that are working have a different DNS set up. I need to check both of those this evening.

    The next, as you correctly point out is routing and that that is broken for some of the addresses that are being resolved. If all the resolved addresses belong to working hosts, then there might be a problem further out, but this looks like a wider problem than just mysqueezebox.com . LMS updates are not being retrieved from repos.squeezecommunity.org and I'm having trouble with sourceforge. There are also logging errors for stream metadata from BBC. If loading the spotty and YouTube plugins is also dependent on a network connection, then there are problems with those routes as well. All this is strange if the problem is with my ISP, as the same URLs work consistently from other hosts in my network, all going out from the same gateway/FW and consistently fail to work from the LMS host. Still, absolutely worth further checking.

    The last point is (still) SSL, as many of the errors are HTTPS related, but until we rule out the first two, it looks as if the problem is host-/LAN- rather than LMS-related. As such it's probably off-topic to the forum, so maybe I should not waste more of your time.

    Thanks again for all your help.

  8. #28
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    17,906
    Quote Originally Posted by Learnincurve View Post
    but this looks like a wider problem than just mysqueezebox.com . LMS updates are not being retrieved from repos.squeezecommunity.org and I'm having trouble with sourceforge.
    mysqueezebox stuff looks to be HHTTPS related.
    Ignore any sourceforge errors - that site generates errors all by itself so you cannot deduice anything from sourceforge communications.

    There are also logging errors for stream metadata from BBC.
    Any examples ?

    Using BBCiplayer ? if so , BBC metadata uses LMS standard http/https communications, audio stream use a custom http/https package to support http 1.1. Any problem with audio ?

  9. #29
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    17,906
    EDIT: Probably not as useful as I first thought - absolutely no logging when using BBCIPlayer streams.

    Depending on how desperate you are to confirm/refute a https problem.

    I just checked how to enable some Perl module IO::Socket::SSL logging when LMS accesses a https URL. It generates lots of messages to console (i.e. LMs must be run form a commandline) - most of which are "normal".

    The LMS file Slim/Networking/Asynch/Socket/HTTPS.pm

    The file should be edited to add " qw(debug3)" - it can be debug0, debug1, debug2, debug3 and debug4 - different levels

    It is a small file - change is highlighted in red.

    Code:
    package Slim::Networking::Async::Socket::HTTPS;
    
    # $Id$
    
    # Logitech Media Server Copyright 2003-2011 Logitech.
    # This program is free software; you can redistribute it and/or
    # modify it under the terms of the GNU General Public License, 
    # version 2.
    
    use strict;
    
    BEGIN {
    	# Force Net::HTTPS to use IO::Socket::SSL
    	use IO::Socket::SSL qw(debug3);
    }
    
    use base qw(Net::HTTPS::NB Slim::Networking::Async::Socket);
    
    sub new {
    	my ($class, %args) = @_;
    	$args{'Blocking'} = 0;
    	return $class->SUPER::new(%args);
    }
    
    sub close {
    	my $self = shift;
    
    	# remove self from select loop
    	Slim::Networking::Select::removeError($self);
    	Slim::Networking::Select::removeRead($self);
    	Slim::Networking::Select::removeWrite($self);
    	Slim::Networking::Select::removeWriteNoBlockQ($self);
    
    	$self->SUPER::close();
    }
    
    1;
    Last edited by bpa; 2019-11-14 at 07:51.

  10. #30
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    17,906
    Different approach - similar to the "telnet 443" but more complete.

    Perl uses OpenSSL package to make a connection. The following command will make a secure connection using OpenSSL libraries, certs etc . to www.mysqueezebox.com
    Code:
    openssl s_client -connect www.mysqueezebox.com:443
    Generates lots of text ending wiuth "Verify return code: 0 (ok)" not sure what a bad connection will look like - I'm guessing a non zero code.

    edit:

    Additional level of detail from s_client - more detail is provided on the interaction to set up a connection.
    Code:
    openssl s_client -state -connect www.mysqueezebox.com:443
    openssl s_client -state -bio -connect www.mysqueezebox.com:443
    Last edited by bpa; 2019-11-14 at 09:43.

Posting Permissions

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