Re: Dlink DI-624 and IPV6

That is interesting...what version of the firmware are you currently running=
?

Also, are you pointing your clients at it for DNS resolution?

Mike B.

Quoting Piet van Weel <pmvw <at> outwardfocus.net>:

> Interesting...
>
> I had a similar issue with a DLINK and upon talking with dlink they
> were saying that the rebooting was caused by the UPNP configuration in
> the DLINK router. Apparently their UPNP system isn't very PNP friendly.
> They said if I turned it off it would stop the rebooting. I did, and it
> did.
>
> BTW: I do have IPV6 running on a couple of the MS boxes here.
>
> Piet
>
> barsalou wrote:
>> *WARNING* My conclusions here are based on observation, not any =3D20
>> specific facts related to the unit or from what I could find on the =3D20
>> internet, but I thought I'd share the info anyway.
>>
>>
>> Recently I decided to switch from Centos to Ubuntu (7.1 - Edgy).
>>
>> First of all, this was not painless.  These two distros are =3D20
>> significantly different.
>>
>> Luckily for me the Ubuntu crowd documents things reasonably well.
>>
>> This change is important to state because at the time of the =3D20
>> changeover, my DI-624 started to reboot itself and seemingly random =3D20
>> intervals.
>>
>> It turns out that in some way the IPV6 that is setup automatically on =3D=
20
>> new Ubuntu installs causes this problem for the DI-624.
>>
>> The DI-624 is configured to be a DNS caching server for my internal netwo=
rk.
>>
>> My personal guess is that The DI-624 didn't handle IPV6 DNS resolution =
=3D20
>> well and that caused the unit to loose its mind and reboot...which is =3D=
20
>> better than the unit just stopping all together.
>>
>> So turning off IPV6 on all my machines (Macs, PC with Vista, my Ubuntu =
=3D20
>> server) cleared the problem right up.
>>
>> I probably could have also solved the problem by creating a DNS =3D20
>> caching server to handle the ipv6 requests, but didn't want to spend =3D2=
0
>> the time.
>>
>>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.