Wozzagonebush

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Wozzagonebush's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I've got it working by setting pi-hole ip to 192.168.1.2 br0, pointing to unbound br0 192.168.1.3#53
  2. Could someone share a working config of both unbound and pi-hole please? I have tried all the suggestions here but have not had any success. # dig pi-hole.net @127.0.0.1 -p 5335 ; <<>> DiG 9.11.5-P4-5.1+deb10u6-Debian <<>> pi-hole.net @127.0.0.1 -p 5335 ;; global options: +cmd ;; connection timed out; no servers could be reached #
  3. This works very well on my Optus wireless broadband which is double NAT, if anyone else is interested
  4. First time poster here; please be kind! I have 2 docker apps running well, Forked-DAAP and Logitech Media Server (LMS). LMS has the ShairTunes2 plugin which makes my Squeezebox players look like AirPlay devices and this works fairly well using iTunes to send music to my Squeezebox. I am trying to get DAAP to recognise the Squeezeboxes as AirPlay devices and have edited the conf file thus: ... # AirPlay/Airport Express device settings # (make sure you get the capitalization of the device name right) airplay "Family Room" { # forked-daapd's volume goes to 11! If that's more than you can handle # you can set a lower value here # max_volume = 11 ... I have also tried "Family Room 00:04:20:12:75:03" which is how the ShairTunes2 plug in reports the Squeezebox. Neither configuration results in the "Airplay" devices being visible in Forked-DAAP. Unfortunately I don't own any real Airplay devices, however my Apple TV and Chromecast audio dongle both show up as a devices in Forked-DAAP. Is my configuration correct and should this work? TIA