Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Drew wrote:
ifconfig eth0 promisc
from the dns-323.
Worth a shot, anyway. No firewall on that thing, is there?
-- Ron
so i take it i have to telnet into the 323 and apply that command. i will give it a shot, but i am just as you are and being a skeptic. stay tuned
and no, i have no firewalls anywhere
Offline
If you got debian on your dns-323 you should see multicasts like this if you do a tcpdump:
09:12:57.923899 IP TECRA.5353 > 224.0.0.251.5353: 0 [2a] [4q] PTR? _appletv-pair._tcp.local.[|domain]
09:12:58.790241 IP TECRA.5353 > 224.0.0.251.5353: 0*- [0q] 3/0/0[|domain]
Offline
well, tried the ifconfig eth0 thing in telnet and came back saying .. no such device.. and i dont have debian installed
Offline
I very strongly doubt that there is an issue on the DNS side. However either your firewall/router is acting up or there is somekind of fw software running on your pc...
Offline
fickle wrote:
well, tried the ifconfig eth0 thing in telnet and came back saying .. no such device.. and i dont have debian installed
OK....
Telnet to DNS-323.
Type ifconfig egiga0 promisc
This should put it into promiscuous mode. The DNS is a gigabit ethernet....eth0 is wrong.
I put this line into my fun_plug. My server now works, after I reboot the DNS...but it does then drop out after a period of use! So....it does work but not as it should.
I'm now leaning towards it being a issue with my router.....I'm still working on it!
Stay tuned.
Offline
ill give that shot and report back the findings
cheers
Offline
well, i gave it a shot..
ifconfig egiga0 promisc works as a command but did nothing in the end
then tried a new router / switch.. nothing .. and to rule out a software firewall, borrowed a laptop from my work (no firewall in it, windows or other) and nothing.
in the end, i think its firefly that is blocking UPNP. looks like i may have to just remove firefly all together.
so my new question, how does one remove firefly?
cheers
Offline
Fickle,
My Firefly works when I do a cold re-boot of the 323. I can see it in iTunes. I can play from it. BUT...when I access it from my MAC iTunes, or add a CD to the 323 (via iTunes) the server stops.
I have something from Ron Pedde to try to see if it is the Firefly server stopping or if it is the network doing something. Unfortunately I have to install Debian to execute the commands. This is a challenge and will take me a couple of nights to get my head around. You may want to try it. This is the instructions from Ron:
> It seems that when the firefly database is refreshed it disappears
> from the network. After a hard boot the fireflyer server returns....
>
When it appears when it first starts but then disappears later, that's
almost always (well, unless the server crashed) multicast issues.
What's the model on the wireless router?
When it disappears, you can check to see if it's still running from
the console of the dns-232 with something like this:
ron@debian-server:~$ ps auxw | grep -i "mt-daapd"
nobody 2536 0.1 4.0 4096 1228 pts/0 S 22:15 0:00 /usr/
sbin/mt-daapd
nobody 2537 0.7 5.0 8192 1556 pts/0 S 22:15 0:00 /usr/
sbin/mt-daapd
nobody 2538 0.0 5.0 8192 1556 pts/0 S 22:15 0:00 /usr/
sbin/mt-daapd
nobody 2539 0.0 5.0 8192 1556 pts/0 S 22:15 0:00 /usr/
sbin/mt-daapd
nobody 2540 0.0 5.0 8192 1556 pts/0 S 22:15 0:00 /usr/
sbin/mt-daapd
ron 2542 0.0 1.5 1552 460 pts/0 S+ 22:15 0:00 grep -i
mt-daapd
You can see five processes running mt-daapd. That's what it looks
like when it's running. Otherwise, it would look like:
ron@debian-server:~$ ps auxw | grep -i "mt-daapd"
ron 2542 0.0 1.5 1552 460 pts/0 S+ 22:15 0:00 grep -i
mt-daapd
So you can verify if it's a network issue or the server crashing by
seeing if it's still running when it disappears off the network.
Unless you are running a very recent nighly, my bet is on the network.
-- Ron
Offline
Fickle,
Where did you buy your 323 from? HT in Melbourne? If so....it may be a problem with the batch that they got as that is where I got mine from.
Offline
i have yet to do the cold reboot. i will give that a shot tonight
may have to look into the debian thing as well, but im no linux guy
Offline
You don't need a debian install to check if the mt-daapd server is still running
The 'ps' command is available from the busybox v1.6.1 binary in fonz's v.03 fun_plug
Type the 'ps' command that Ron Pedde suggested from the telnet prompt
to see if the mt-daapd server is running.
Offline
mig wrote:
You don't need a debian install to check if the mt-daapd server is still running
The 'ps' command is available from the busybox v1.6.1 binary in fonz's v.03 fun_plug
Type the 'ps' command that Ron Pedde suggested from the telnet prompt
to see if the mt-daapd server is running.
Thanks for that...
Right. Have done it and this is the response. Have sent it to Ron to get feedback...if you can see anything....many, many thanks:
Ron,
This is the response when it is running:
1330 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1331 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1360 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1361 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
This is the response after it stopped:
1330 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1331 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1360 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1361 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1480 root grep -i mt-daapd
So....there were four running at the beginning and five after it fell over.
Don't know what this means....
Drew
Offline
I think you could be mis-interpreting the 'ps' output
The first number in the output of the 'ps' command is the process ID.
This is a unique integer assigned, by the kernel, to each process started on the system.
So, when you could see the iTunes server, there were 4 mt-daapd processes running
IDs: 1330, 1331, 1360, 1361
After the iTunes server was not visible, the same 4 mt-daapd processes were still running
IDs: 1330, 1331, 1360, 1361
The additional process in the second 'ps' output (id 1480) is the grep command itself.
Offline
Thanks Mig. That means that the Firefly server is still running and it is a network issue....OR could it be that if the Firefly database is changed or accessed by another computer on the network it becomes corrupted (in some way)? I think this is probably not the reason.
More than likely it is the network not doing multicast properly - that is Ron's suggestion - even though the DNS-323 is now set to promiscuous multicast.
I am using a DLink DSL-604T router/modem. This is where I thought the problem was three weeks ago....and I guess this confirms it.
And so the journey to getting this working continues....
Offline
Success.
Ron confirmed that the server was running fine. It had to be the network!
After just concentrating on the router...I went back to the basics and looked for the multicast settings. I was told by DLink that the router is set to multicast all the time and they said do not worry about that!
Well...it turns out there is a setting for the IGMP. This needs to be turned on! It was off as a default. I recall turning this on and off previously, but this was before putting the DNS-323 in promiscuous mode and it made no difference. So it seems the combination of putting the DNS-323 in promiscuous mode and enabling the IGMP setting on the router has got the router multicast and Firefly working properly.
I'm very impressed with Firefly Running an XP, Mac, and also streaming to an AV Receiver. All at once....
Thankyou a bunch Ron!
Andrew.
Offline
glad to see you got yours working Drew, now my turn. been out a few days so now i need to catch up .. will have to look into my router for IGMP .. though i dont think i saw a setting for it anywhere on the router.. but i will have a 2nd look
cheers
Offline
What type of router do you use?
Offline
hey Drew,
its an Linksys WRT350N (technically i have two routers, the other is a Cisco 1751) but i am sure this is not the issue, i would think its my linksys.. .. my cisco is only used for NATTING externally to internally ... my linksys is to connect local devices.. then off to the cisco for internet access
cheers
Offline
Go to "The Security Tab - Firewall" page 29 of manual
Filter Multicast. Multicasting allows for multiple transmissions to specific recipients at the same time. If
multicasting is permitted, then the Router will allow IP multicast packets to be forwarded to the appropriate
computers. Select Enabled to filter multicasting, or Disabled to disable this feature.
Make sure that multicasting is enabled (by that I mean ON as the manual is not very clear that it is ON if it is enabled or disabled....not very well written)
Also....what was your result after Telneting to 323 and running the command:
ps auxw | grep -i "mt-daapd"
You should get result like this:
1330 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1331 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1360 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
1361 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
This will see if you have Firefly running as a server. If it is...then it is the network as mine was....and as Ron said....that suggest multicast isn't working properly...and he was right.
Also you will need to make sure you have the line:
ifconfig egiga0 promisc
in your fun_plug to enable promiscuous mode. I put it before the line that starts Firefly.
This is the total of all changes that got my server running Good luck.
Offline
jeez drew, you drew up more on my router than i could find within the help manual
i do recall some of the stuff you mentioned, and yes, somewhat .. difficult to understand
ill run these commands tonight and modify my router accordingly
stay tuned
and thanks
Offline
well, tried what you mentioned within my router .. in fact i have disabled SPI firewall all together & made sure that no filtering is enabled within that same tab
Filter Anonymous Internet Requests
Filter Multicast
Filter Internet NAT Redirection
Filter IDENT (Port 113)
no checkboxes are checked for the above within the router .. also did the egaga0 thing within telnet to the 323 and still nothing on the network..
i did do the ps auxw thing and i got a similar result as you did ...
/ # ps auxw | grep -i "mt-daapd"
20787 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
20788 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
20794 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
20795 root /mnt/HD_a2/lnx_bin/mt-daapd -c /mnt/HD_a2/lnx_bin/mt-daapd.conf
2779 root grep -i mt-daapd
/ #
so still the same result as last time.. no 323 on the network. going to call Linksys to find out what is wrong
thanks
Offline
Well...your Firefly server is running. So that is good.
When you do a complete shutdown of the 323 and then restart - does the Firefly server appear in iTunes? If it does, and then disappears, this is pretty much as conclusive as you can get that it is a network issue and multicasting isn't working as it should.
One other thin I noticed in the router is that you have the ability to turn on UPnP and have the router act as a media server. I would try changing the settings in this tab. UPnP turned on - then off - remembering to do a total shutdown in between each different setting you try. I think it is important to shutdown completely and restart. Try UPnP on, and the media server off - I think you can do that as well in the UPnP tab (from memory it is @ page 36 of manual).
Best of luck....
Offline
swapped out to a different router, still same issue. this is an older router with very little functionality in respect to firewall. i have removed or disabled any firewall rule within this old router and still the same issue arises.
i do agree that it is not the 323 that is the issue (based on trouble shooting from prior posts .. thanks Drew), just cant identify what the real culprit is..
the search goes on
Offline
fickle wrote:
swapped out to a different router, still same issue. this is an older router with very little functionality in respect to firewall. i have removed or disabled any firewall rule within this old router and still the same issue arises.
i do agree that it is not the 323 that is the issue (based on trouble shooting from prior posts .. thanks Drew), just cant identify what the real culprit is..
the search goes on
did you manage to find out about the issue?
Thanks!
Offline
nope.. still unable to get this working
Offline