Home of the Squeezebox™ & Transporter® network music players.
Page 103 of 123 FirstFirst ... 35393101102103104105113 ... LastLast
Results 1,021 to 1,030 of 1222
  1. #1021
    Quote Originally Posted by garym View Post
    One is always controlling LMS and LMS then sends instructions to the players. So Material Skin will be talking to the LMS (on one of the rPi). Then LMS will send commands via your network to the other rPi serving as a player. Keep in mind that one could have a dozen players. But they are all talking to the single LMS in your network (and you only need to control that single LMS to control all the players)
    Quote Originally Posted by kidstypike View Post
    The Pi that has LMS installed is your server. The other Pi is just a player and can be selected from the players list in material, material will list all players connected to your network.
    Thank you Kidstypike & Gary,

    Sorted the problems, everything works fine as of now.

    One thing though, currently running both RPI's on Wifi. As expressed earlier, I want to run the server on a wired connection (ethernet). Should I just disable WIFI on the "SERVER" PI & insert the ethernet cable? Will my IP address remain the same eg: 192.xxx.x.4, having assigned this IP address as static IP base on MAC Address of my router?

  2. #1022
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    6,293
    From memory, it is technically possible to have Ethernet and WiFi working at the same time … in which case they would have different MAC addresses. In that case, simply tell your router to fix that at .1.4 as well (if it allows duplicates).
    I think the player will find it anyway unless you configured Squeezelite to connect to a specific IP address.
    Paul Webster
    Author of "Now Playing" plugins covering Radio France (FIP etc), PlanetRadio (Bauer - Kiss, Absolute, Scala, JazzFM etc), KCRW, ABC Australia and CBC/Radio-Canada
    and, via the extra "Radio Now Playing" plugin lots more - see https://forums.slimdevices.com/showt...Playing-plugin

  3. #1023
    Member sciurius's Avatar
    Join Date
    Nov 2007
    Location
    52.88504N 06.85904E
    Posts
    82

    WiFi / Ethernet conflict?

    Hi,

    I migrated piCoreplayer from RPi1 to RPi3 and now I'm running into a strange issue.

    I have disabled on-board WiFi and BT and use an USB WiFi (rtl8192cu). Eth0 and Wlan0 are set to DHCP. AFAIK, support for the rtl8192cu is still in-kernel.

    When booting without network cable (the intended use case) I see a DHCP query and it gets 192.168.1.23 and name picky. On the console it reports that startup has finished and that I can connect to

    http://192.168.1.33 (eth0)
    http://192.168.1.23 (wlan0)
    http://picky.local (mdns)

    Note that 192.168.1.33 is the IP of the ethernet interface used for the initial configure. Since it is started without cable connected, there's only wlan0.

    But it doesn't respond on the 23 address. No ping, web, etc..

    When I plug in the ethernet cable, I can access it via the wlan address (web, ssh and ping), and after a couple of seconds I see a DHCP for the ethernet.
    Disconnect the cable and it is unreachable again.

    I must be overlooking something trivial, but what?
    LMS 8.2 on RPi4 - PiCorePlayer 8.0.0 (SqueezeLite) on RPi1, moving to 8.2.0 on RPi3.

  4. #1024
    Junior Member
    Join Date
    Jan 2021
    Location
    Essex, UK
    Posts
    25
    Quote Originally Posted by Narcos View Post
    ... One thing though, currently running both RPI's on Wifi. As expressed earlier, I want to run the server on a wired connection (ethernet). Should I just disable WIFI on the "SERVER" PI & insert the ethernet cable? Will my IP address remain the same eg: 192.xxx.x.4, having assigned this IP address as static IP base on MAC Address of my router?
    You are running a streaming system just as I do. My server (LMS, no Squeezelite) is connected to the Local Area Network via Ethernet with the WiFi turned off. My player (Squeezelite, no LMS) is connected to the LAN via WiFi.

    However, please note that an IP address is the address of an interface to a box and not the box itself. One IP address per interface means that your DHCP server should assign an IP address to a box's WiFi interface MAC address (if enabled) and another (different) one to the box's (different) Ethernet interface MAC address.

    I think your DHCP server is set up to specifically allocate ".4" to the MAC address of the WiFi interface. I think this will not be assigned to the Ethernet interface with a different MAC address. I think you will get a different IP address. I suggest you should add a new allocation to your DHCP server's setup to assign a different IP address to the different Ethernet MAC address or allocate ".4" but delete the same allocation to the WiFi MAC address.

  5. #1025
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    5,350
    Quote Originally Posted by sciurius View Post
    Hi,

    I migrated piCoreplayer from RPi1 to RPi3 and now I'm running into a strange issue.

    I have disabled on-board WiFi and BT and use an USB WiFi (rtl8192cu). Eth0 and Wlan0 are set to DHCP. AFAIK, support for the rtl8192cu is still in-kernel.

    When booting without network cable (the intended use case) I see a DHCP query and it gets 192.168.1.23 and name picky. On the console it reports that startup has finished and that I can connect to

    http://192.168.1.33 (eth0)
    http://192.168.1.23 (wlan0)
    http://picky.local (mdns)

    Note that 192.168.1.33 is the IP of the ethernet interface used for the initial configure. Since it is started without cable connected, there's only wlan0.

    But it doesn't respond on the 23 address. No ping, web, etc..

    When I plug in the ethernet cable, I can access it via the wlan address (web, ssh and ping), and after a couple of seconds I see a DHCP for the ethernet.
    Disconnect the cable and it is unreachable again.

    I must be overlooking something trivial, but what?
    Hi Johan

    I think the driver has gone


    Significant changes

    • Kernel 5.15.35
      • Removed out of tree Realtek wifi drivers from Kernel. If you see a warning on the insitu update, you should not proceed until you build your driver—see pCP Kernels.

    • RPi Firmware Apr 26, 2022 (Does not affect RPi4 bootloader)
    • Squeezelite 1.9.9-1392
    • Image includes Mediatek wifi firmware.
    • Various bug fixes and web interface updates.


    I just tried it with a simialr dongle and no wi-fi. If you connect a screen and watch the printout there is no IP address.

    It does still work on the raspberry PIOS.

    I installed Buster lite 32 bit.

    I used the raspberry pi imager tool, set the SSH and Wi-Fi configuration, locales before making the image (click the gear wheel icon).

    Removed the reader and then re-inserted it and edited the config file to stop the onboard wi-fi- and BT.

    Saved

    Removed the reader and put the card in the pi and booted without Ethernet.

    I had plugged in a screen and keyboard.

    The pi came up and started. I ran an update and upgrade; ready to go.

    ronnie

  6. #1026
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    5,350
    Quote Originally Posted by Paul Webster View Post
    From memory, it is technically possible to have Ethernet and WiFi working at the same time … in which case they would have different MAC addresses. In that case, simply tell your router to fix that at .1.4 as well (if it allows duplicates).
    I think the player will find it anyway unless you configured Squeezelite to connect to a specific IP address.
    with pCP, If the Wireless in enabled , connecting the ethernet disables the wireless. and becomes the default connection.

    ronnie

  7. #1027
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    5,350
    Quote Originally Posted by sciurius View Post
    Hi,

    I migrated piCoreplayer from RPi1 to RPi3 and now I'm running into a strange issue.

    I have disabled on-board WiFi and BT and use an USB WiFi (rtl8192cu). Eth0 and Wlan0 are set to DHCP. AFAIK, support for the rtl8192cu is still in-kernel.

    When booting without network cable (the intended use case) I see a DHCP query and it gets 192.168.1.23 and name picky. On the console it reports that startup has finished and that I can connect to

    http://192.168.1.33 (eth0)
    http://192.168.1.23 (wlan0)
    http://picky.local (mdns)

    Note that 192.168.1.33 is the IP of the ethernet interface used for the initial configure. Since it is started without cable connected, there's only wlan0.

    But it doesn't respond on the 23 address. No ping, web, etc..

    When I plug in the ethernet cable, I can access it via the wlan address (web, ssh and ping), and after a couple of seconds I see a DHCP for the ethernet.
    Disconnect the cable and it is unreachable again.

    I must be overlooking something trivial, but what?
    I think it should work; but doesn't



    dmseg

    [ 3.636175] usb 1-1.5: New USB device strings: Mfr=0, Product=1, SerialNumber=0
    [ 3.636185] usb 1-1.5: Product: USB2.0 Hub
    [ 3.636786] hub 1-1.5:1.0: USB hub found
    [ 3.637073] hub 1-1.5:1.0: 4 ports detected
    .
    [ 4.112269] usb 1-1.5.1: New USB device found, idVendor=045e, idProduct=0750, bcdDevice= 1.10
    [ 4.112283] usb 1-1.5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 4.112293] usb 1-1.5.1: Product: Wired Keyboard 600
    [ 4.112301] usb 1-1.5.1: Manufacturer: Microsoft
    [ 4.150933] input: Microsoft Wired Keyboard 600 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.0/0003:045E:0750.0001/input/input0
    .
    [ 4.381023] usb 1-1.5.2: New USB device found, idVendor=045e, idProduct=00cb, bcdDevice= 1.04
    [ 4.381045] usb 1-1.5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 4.381055] usb 1-1.5.2: Product: Microsoft Basic Optical Mouse v2.0
    [ 4.381063] usb 1-1.5.2: Manufacturer: Microsoft
    [ 4.386284] input: Microsoft Microsoft Basic Optical Mouse v2.0 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/0003:045E:00CB.0003/input/input2
    .
    [ 8.450260] usbcore: registered new interface driver rtl8192cu
    .
    [ 8.128833] cfg80211: Loading compiled-in X.509 certificates for regulatory database
    [ 8.177731] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'

    -----------------------------------------------------------------------------------------------------------------------------------------

    Loaded modules

    Module Size Used by
    rtl8192cu 86016 0
    rtl_usb 20480 1 rtl8192cu
    rtl8192c_common 65536 1 rtl8192cu
    rtlwifi 118784 3 rtl_usb,rtl8192c_common,rtl8192cu

    mac80211 827392 3 rtl_usb,rtlwifi,rtl8192cu
    libarc4 16384 1 mac80211
    sha256_generic 16384 0
    cfg80211 790528 2 mac80211,rtlwifi
    raspberrypi_hwmon 16384 0
    rfkill 32768 3 rtlwifi,cfg80211
    hid_microsoft 16384 0
    ff_memless 16384 1 hid_microsoft



    ronnie

  8. #1028
    Member
    Join Date
    Sep 2008
    Location
    Barcelona
    Posts
    84
    Quote Originally Posted by Narcos View Post
    Thank you Kidstypike & Gary,

    Sorted the problems, everything works fine as of now.

    One thing though, currently running both RPI's on Wifi. As expressed earlier, I want to run the server on a wired connection (ethernet). Should I just disable WIFI on the "SERVER" PI & insert the ethernet cable? Will my IP address remain the same eg: 192.xxx.x.4, having assigned this IP address as static IP base on MAC Address of my router?
    Nope, IP address will change because each network interface has its own MAC address. You'll have to assign 192.xxx.x.4 to the MAC of the wired connector.

  9. #1029
    Member sciurius's Avatar
    Join Date
    Nov 2007
    Location
    52.88504N 06.85904E
    Posts
    82
    Quote Originally Posted by Man in a van View Post
    Hi Ronnie,
    I think the driver has gone
    I'm quite sure it has not. The rtl8192cu is still in-kernel.
    LMS 8.2 on RPi4 - PiCorePlayer 8.0.0 (SqueezeLite) on RPi1, moving to 8.2.0 on RPi3.

  10. #1030
    Member sciurius's Avatar
    Join Date
    Nov 2007
    Location
    52.88504N 06.85904E
    Posts
    82
    Quote Originally Posted by Man in a van View Post
    with pCP, If the Wireless in enabled , connecting the ethernet disables the wireless. and becomes the default connection.
    That could be an explanation.

    I re-installed 8.2.0 and configured without using the ethernet cable and now it boots and runs fine. It is a tad faster than the old RPi1 (30 seconds versus 60seconds or so).
    LMS 8.2 on RPi4 - PiCorePlayer 8.0.0 (SqueezeLite) on RPi1, moving to 8.2.0 on RPi3.

Tags for this Thread

Posting Permissions

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