I started looking at, (or trying to figure out that jivelite segfault I
was getting on desktop on final setup screen).... Rather than running a
local LMS, I stopped that, started jivelite and it didn't discover the
other two servers on the local network. OK, then I notice that
squeezelite started without "-s <server>" option doesn't discover
either. 

/var/log/squeezelite/squeezelite.log

Code:
--------------------
    
  [14:34:20.035341] discover_server:699 sending discovery
  [14:34:25.040514] discover_server:699 sending discovery
  [14:34:30.045692] discover_server:699 sending discovery
  [14:34:35.050875] discover_server:699 sending discovery
  
--------------------


On the desktop box, I have 3 network interfaces. loopback, ethernet
(p6p1), and wi-fi (wlp0s18f2u2).

Code:
--------------------
    
  lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10<host>
  loop  txqueuelen 0  (Local Loopback)
  RX packets 32264  bytes 483086388 (460.7 MiB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 32264  bytes 483086388 (460.7 MiB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
  p6p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
  inet 192.168.0.60  netmask 255.255.255.0  broadcast 192.168.0.255
  inet6 fe80::226:18ff:fe18:a45  prefixlen 64  scopeid 0x20<link>
  ether 00:26:18:18:0a:45  txqueuelen 1000  (Ethernet)
  RX packets 251227  bytes 112298235 (107.0 MiB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 385616  bytes 522332066 (498.1 MiB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
  wlp0s18f2u2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
  ether 20:4e:7f:d8:88:f1  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
--------------------


As you can see, ethernet interface is connected and has IP. The wi-fi
interface is not associated with an access point and does not have an
IP. What I suspect is happening, (but I've run out of time, so will have
to return to this with wireshark later to prove my theory), is that both
jivelite and squeezelite are sending out discovery on the wi-fi
interface and not wired.


------------------------------------------------------------------------
JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069
View this thread: http://forums.slimdevices.com/showthread.php?t=99395

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

Reply via email to