pavowren wrote: 
> 1) huh? but the output device is in the Pi, not NUC. have i missed
> something awful?
> 2) ifconfig's for RPi and NUC are shown below. as they are, all LMS
> functions work.
> however, for internet radio i must re-enable wifi on RPi. What is shown
> below is obviously without wifi.
> in attempts to avoid having to enable wifi on RPi,
> i tried to bridge the ethernet (eno1) on NUC and its wireless interface
> (which goes out to internet via the hotspot).
> i have not succeeded so far experimenting with
> /etc/network/interfaces...   
> 
> 
> RPi,
> pi@raspberryPi:~ $ ifconfig
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 192.168.1.23  netmask 255.255.255.0  broadcast
> 192.168.1.255
> inet6 fe80::7cfc:82aa:8dfb:d773  prefixlen 64  scopeid
> 0x20<link>
> ether b8:27:eb:fd:ab:5a  txqueuelen 1000  (Ethernet)
> RX packets 11261  bytes 1166993 (1.1 MiB)
> RX errors 0  dropped 1  overruns 0  frame 0
> TX packets 8921  bytes 795869 (777.2 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> 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 1000  (Local Loopback)
> RX packets 529  bytes 192450 (187.9 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 529  bytes 192450 (187.9 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> 
> NUC:
> groundie@NUCi:~$ ifconfig
> eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 192.168.1.150  netmask 255.255.255.0  broadcast
> 192.168.1.255
> inet6 fe80::85e6:82a9:77da:dfe1  prefixlen 64  scopeid
> 0x20<link>
> ether 94:c6:91:a7:02:de  txqueuelen 1000  (Ethernet)
> RX packets 14090  bytes 1303265 (1.3 MB)
> RX errors 0  dropped 1  overruns 0  frame 0
> TX packets 20814  bytes 2478165 (2.4 MB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 30
> device interrupt 16  memory 0xaeb00000-aeb20000  
> 
> 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 1000  (Local Loopback)
> RX packets 82239  bytes 5694590 (5.6 MB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 82239  bytes 5694590 (5.6 MB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> wlp0s20f3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 192.168.43.63  netmask 255.255.255.0  broadcast
> 192.168.43.255
> inet6 fe80::62ff:dc58:8e41:b76d  prefixlen 64  scopeid
> 0x20<link>
> ether 04:d3:b0:fc:a6:34  txqueuelen 1000  (Ethernet)
> RX packets 7341  bytes 7409306 (7.4 MB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 14382  bytes 2230853 (2.2 MB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Quite clearly the Pi has no route to the internet when not connected by
WiFI.

When only connected by LAN what is its default gateway? No in you info
above.
How are IP addresses obtained on the LAN? DHCP or Static. If DHCP where
from ?



VB2.4[/B] STORAGE *QNAP TS419P (NFS)
[B]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
------------------------------------------------------------------------
d6jg's Profile: http://forums.slimdevices.com/member.php?userid=44051
View this thread: http://forums.slimdevices.com/showthread.php?t=110232

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

Reply via email to