- This topic has 14 replies, 4 voices, and was last updated 17 years, 7 months ago by
.
-
Posts
-
I have a Pinnacle M1001 Soundbridge running against Firefly version svn-1515 on Fedora Core 5.
When I power up the Soundbridge first time, it configures the network, gets an IP address issued and finds Firefly no problem. However, once I switch into standby, say overnight and power up, it can’t see Firefly. I have found that the easiest solution is to reboot from the system configuration menu and then it finds FireFly no problem.
Whenever I run iTunes on Windows machines on my net, it always finds the FireFly database.
Not sure where to start looking to fix this. mDNS is all setup and was a problem initially but, not an issue any longer.
Many Thanks for any advice,
Martin Main
I guess that you’ve set a DHCP lease time which is finite.
One other thing might be that multicasts arent forwarded properly by your wireless router.How is your soundbridge connected to your music-server? And by what means?
Thanks for feedback.
I have an entry in dhcpd.conf tied to the MAC address, so although the lease will get renewed it will always end up with the same IP.
At the Soundbridge end I have a DLink DWL2100AP setup to connect to my main hub which is a DLink DI-624. The DI-624 has multicast streams enabled, there is no equivalent setting on the DWL2100AP. I am using this because it has more HP to connect upstairs where I have the DI-624 i.e. I am using the wired ethernet port on the Sounbridge as it could not find the DI-624 through its own wireless LAN.
Thanks,
Martin
Ok, so DHCP is not an issue. If you have a static DHCP entry, you might as well set up a client lease time of 0 (zero) 😉
So you have 1 wireless AP (upstairs) and one wireless-to-ethernet bridge, which the soundbridge plugs into?
Not too sure how to set lease times on a per machine basism but have adjusted this up to 2 weeks renewal time.
Confirm this is the network configuration I have.
I have not resolved this problem and after the period of time, the soundbridge needs a reboot. However, I have attempted to try svn-1528 and svn-1539 and when compiled under exactly the same environment as svn-1515, the soundbridge never sees the server at all.
@mmain wrote:
I have not resolved this problem and after the period of time, the soundbridge needs a reboot. However, I have attempted to try svn-1528 and svn-1539 and when compiled under exactly the same environment as svn-1515, the soundbridge never sees the server at all.
Are you compiling with –enable-avahi, or with –enable-howl?
Check to make sure you aren’t running another mdns responder, as you can’t run two. In fact, that would explain the other problem if you were already running an mdns responder and tried to run the built-in one.
I have compiled with –prefix=/usr –enable-mdns –enable-sqlite3 only on all three occasions. I don’t have any avahi or howl responders running.
Interestingly I had svn-1515 running and the soundbridge playing music and did a make install on svn-1539 and restarted. The soundbridge recovered and continued playing. However, I did a reboot from the soundbridge menu and it can’t see the server.
Was there some significant change beyond 1515?
@mmain wrote:
I have compiled with –prefix=/usr –enable-mdns –enable-sqlite3 only on all three occasions. I don’t have any avahi or howl responders running.
Interestingly I had svn-1515 running and the soundbridge playing music and did a make install on svn-1539 and restarted. The soundbridge recovered and continued playing. However, I did a reboot from the soundbridge menu and it can’t see the server.
Was there some significant change beyond 1515?
1528 changed to the new apple bonjour libraries. Does it show it registering rendezvous?
Try configuring it with –prefix=/usr –enable-sqlite3.
Don’t use –enable-mdns.
Tried this but no better off, still can’t see the server from the soundbridge. Log file output as noted.
2007-04-19 23:16:18 (b7ef56b0): Plugin loaded: rsp/svn-1539
2007-04-19 23:16:18 (b7ef56b0): Plugin loaded: daap/svn-1539
2007-04-19 23:16:18 (b7ef56b0): Starting rendezvous daemon
2007-04-19 23:16:18 (b7ef56b0): Starting signal handler
2007-04-19 23:16:18 (b7ef56b0): Initializing database
2007-04-19 23:16:22 (b7ef56b0): Starting web server from /usr/share/mt-daapd/admin-root on port 3689
2007-04-19 23:16:22 (b7ef56b0): Listening on port 3689
2007-04-19 23:16:22 (b7ef56b0): Starting server thread
2007-04-19 23:16:22 (b7ef56b0): Registering rendezvous names
2007-04-19 23:16:22 (b7ef56b0): Serving 22206 songs. Startup complete in 4 seconds
- The forum ‘Setup Issues’ is closed to new topics and replies.