FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › Connect fails:NSLU2 / Soundbridge Radio / HomeMusic / M1001
- This topic has 6 replies, 2 voices, and was last updated 15 years, 5 months ago by Anonymous.
-
AuthorPosts
-
05/11/2008 at 9:54 PM #2684AnonymousInactive
Hi,
(apologies for posting this on the Roku FF forum also)
I have been struggling with connection problems described here http://forums.rokulabs.com/viewtopic.php?t=18148
Summary is that I can see the library, but when I connect to it I get
“Connection to server failed”
>OK< All configurations will play internet radio fine (?) I thought the problems were due to multicast on my router but I tried a wired M1001 and had the same result. My configuration is: NSLU2 with OpenWRT 7.09 installed
mt-daapd-svn-1696 installed as optware
Netgear DG834G v3 V4.01.40 firmware (upgraded from 4.01.06, also tried 4.01.28)
Pinnacle SoundBridge Radio 3.0.52 beta firmware (wireless)
Pinnacle SoundBridge Homemusic 3.0.52 beta firmware (wireless)
Roku Soundbridge M1001 3.0.44 firmware (wired via router and by direct crossover cable).Does anyone have any ideas please?
06/11/2008 at 10:08 AM #17841AnonymousInactiveAs noted in http://forums.rokulabs.com/viewtopic.php?t=18188 I can see the admin page … Bonjour service is stopped?
06/11/2008 at 7:38 PM #17842fizzeParticipantThe admin page always sais that.
OpenWRT on the NSLU2? Now that’s a new one. 😉
Check multicast settings on your router. It’s most likely that the router isnt forwarding broadcasts / multicasts.
You could verify this with a PC on the LAN or WLAN, runnig tcpdump or wireshark to see the absence of those packets.
Is there an alternate firmware for the Netgear? Your chances might be better there.
06/11/2008 at 8:41 PM #17843AnonymousInactiveThanks for the reply…
OpenWRT on the NSLU2? Now that’s a new one. Wink
It’s pretty good, you can fit quite a lot on the internal flash (although with what i have installed, i had to put mt-daapd on external storage as optware).
Check multicast settings on your router. It’s most likely that the router isnt forwarding broadcasts / multicasts.
I thought that which is why I tried a borrowed M1001, over wires first through router and then via crossover – same outcome. I was under the impression that the SBs use multicast to establish the ip of the server – it can see the server (appears on the SB library list) just can’t connect.
You could verify this with a PC on the LAN or WLAN, runnig tcpdump or wireshark to see the absence of those packets.
That’s a good idea … prove it either way I guess.
Is there an alternate firmware for the Netgear? Your chances might be better there.
Tried V4.01.40 firmware latest (upgraded from 4.01.06, also tried 4.01.28) there were reports of the DG834G working at 4.0.20 which is no longer available.
07/11/2008 at 9:35 AM #17844fizzeParticipantOk, if they can see the server that means that multicasts packets are ok.
You dont run iptables on your slug, do you?
07/11/2008 at 9:40 AM #17845AnonymousInactiveI had not configured it and did not expect any rules to be configured, but iptables -L gives
Chain INPUT (policy DROP)
target prot opt source destination
DROP all — anywhere anywhere state INVALID
ACCEPT all — anywhere anywhere state RELATED,ESTABLISHED
DROP tcp — anywhere anywhere tcp option=!2 flags:SYN/SYN
input_rule all — anywhere anywhere
LAN_ACCEPT all — anywhere anywhere
ACCEPT icmp — anywhere anywhere
ACCEPT gre — anywhere anywhere
REJECT tcp — anywhere anywhere reject-with tcp-reset
REJECT all — anywhere anywhere reject-with icmp-port-unreachableChain FORWARD (policy DROP)
target prot opt source destination
DROP all — anywhere anywhere state INVALID
TCPMSS tcp — anywhere anywhere tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU
ACCEPT all — anywhere anywhere state RELATED,ESTABLISHED
forwarding_rule all — anywhere anywhere
ACCEPT all — anywhere anywhereChain OUTPUT (policy DROP)
target prot opt source destination
DROP all — anywhere anywhere state INVALID
ACCEPT all — anywhere anywhere state RELATED,ESTABLISHED
output_rule all — anywhere anywhere
ACCEPT all — anywhere anywhere
REJECT tcp — anywhere anywhere reject-with tcp-reset
REJECT all — anywhere anywhere reject-with icmp-port-unreachableChain LAN_ACCEPT (1 references)
target prot opt source destination
ACCEPT all — anywhere anywhereChain forwarding_rule (1 references)
target prot opt source destinationChain forwarding_wan (0 references)
target prot opt source destinationChain input_rule (1 references)
target prot opt source destinationChain input_wan (0 references)
target prot opt source destinationChain output_rule (1 references)
target prot opt source destination07/11/2008 at 9:56 AM #17846AnonymousInactiveI removed the rules
/etc/init.d/firewall stop
on OpenWRT, success … its now working.
Thanks for the suggestion I hadn’t even considered the firewall … as its a router distro I should have!!!
Many thanks
-
AuthorPosts
- The forum ‘Setup Issues’ is closed to new topics and replies.