[slim] Re: DHCP oddities...

2006-01-30 Thread MrC
Malor (and others), I can confirm that the bug was resolved. -- MrC MrC's Profile: http://forums.slimdevices.com/member.php?userid=468 View this thread: http://forums.slimdevices.com/showthread.php?t=20496

Re: [slim] Re: DHCP oddities...

2006-01-30 Thread dean blackketter
No, it will be in firmware 30 when that is released. The bug will be marked resolved at that point. Probably a day or two. On Jan 30, 2006, at 10:33 AM, Malor wrote: Excellent. (that was fast!) Is the updated firmware in the nightly 6.2.X build? -- Malor

[slim] Re: DHCP oddities...

2006-01-30 Thread Malor
Excellent. (that was fast!) Is the updated firmware in the nightly 6.2.X build? -- Malor Malor's Profile: http://forums.slimdevices.com/member.php?userid=1961 View this thread:

[slim] Re: DHCP oddities...

2006-01-29 Thread Malor
Pfarrell, I don't think you read my original post correctly. That's what I am already doing. You're describing my home network almost exactly. The problem is that there is a bug in the Squeezebox firmware. When it makes a DHCP request with bridging enabled, it does so with the *wrong MAC

[slim] Re: DHCP oddities...

2006-01-29 Thread Malor
Version 29 of the firmware is even worse. The players are both now requesting DHCP addresses with the MAC address 00:00:00:00:00:10. So they both get handed the same IP address by the server (I'm not sure why this didn't happen before; perhaps they were slightly different and I just didn't see

[slim] Re: DHCP oddities...

2006-01-29 Thread Michaelwagner
I see that the severity on the bug is Normal. According to the bug's life definitions, I think it should be one of these: Critical crashes, loss of data, severe memory leak Major major loss of function -- Michaelwagner

Re: [slim] Re: DHCP oddities...

2006-01-29 Thread dean blackketter
I've found and fixed the problem, look for it in the forthcoming firmware v30. ___ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss

[slim] Re: DHCP oddities...

2006-01-29 Thread Malor
Great! when it's available, let me know, and I'll be happy to test it. Thanks! -- Malor Malor's Profile: http://forums.slimdevices.com/member.php?userid=1961 View this thread:

[slim] Re: DHCP oddities...

2006-01-28 Thread Browny
Just a guess but your Linksys might be getting upset with the Squeezebox not presenting a Name to register with. While this is unusual in a network environment it works fine on both the DHCP servers I've used. See the thread below: http://forums.slimdevices.com/showthread.php?t=19120 --

[slim] Re: DHCP oddities...

2006-01-28 Thread MrC
Malor, This is a bug I discovered and reported. See: http://bugs.slimdevices.com/show_bug.cgi?id=2221 -- MrC MrC's Profile: http://forums.slimdevices.com/member.php?userid=468 View this thread:

[slim] Re: DHCP oddities...

2006-01-28 Thread Michaelwagner
MrC Wrote: Malor, This is a bug I discovered and reported. See: http://bugs.slimdevices.com/show_bug.cgi?id=2221 This bug is specifically about bridging. Are you bridging? -- Michaelwagner Michaelwagner's

[slim] Re: DHCP oddities...

2006-01-28 Thread Malor
Yes, I'm bridging with both units. I just turned it on with the second one, and noticed this issue while troubleshooting it getting the wrong IP address. The possibility that it might be the bridging just hit me about ten minutes ago... in fact, it was that thought that prompted me to log in

Re: [slim] Re: DHCP oddities...

2006-01-28 Thread Pat Farrell
Malor wrote: Other than turning off bridging or going to static addressing, are there any other workarounds I could try? This isn't a critical problem, and I can wait for a fix if it'll be awhile before one shows. How about running a DHCP server that you can configure to assign fixed IP

[slim] Re: DHCP oddities...

2006-01-28 Thread MrC
It was pretty clear to me from your MAC address that you had bridging enabled, and were encountering the bug I submitted and researched. There is new firmware (v29) just updated today. Perhaps you can download tonight's 6.2.2 or 6.5 build and test it out to see if its fixed. I've already