snarlydwarf;170695 Wrote: > That is true, and there is even a question on that bug report if there > is more than one bug being talked about... without being able to > reproduce it, who knows... Hence why I ignore all but the packet > dump. > > The only broken thing (from the SB anyway) that I see is the discover > from port 3483 to port 8900... that is backwards: it should be sending > to port 255.255.255.255:3483. > > No idea why it would do that, though that still doesnt answer the "why > is arp not replying?" .. but since the bug is supposedly related to > shutting the server down, perhaps that is related. > > What I see in the packet dump is that the SB is trying really hard to > connect to the server, getting no response. When rebooted it connects > to Squeezenetwork just fine, and when it is logged out of SN, it > connects to the local server. > > tbessie, do you know how to use ethereal or tcpdump to create a packet > capture so we can see what it is doing?
I haven't used them, but I can surely set them up/use them as needed. I'm a software developer myself, so I understand the intricacies of these sorts of problems, don't get me wrong. I just was under the (mistaken?) impression that the information Christopher had provided would be enough to set the DB developers on the right path. But I'll reread the bug report and this thread and see if I can produce a nice trace for y'all. - Tim -- tbessie ------------------------------------------------------------------------ tbessie's Profile: http://forums.slimdevices.com/member.php?userid=8521 View this thread: http://forums.slimdevices.com/showthread.php?t=31661 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
