G
Guest
Guest
Archived from groups: alt.video.ptv.replaytv (More info?)
Let me make one more suggestion. Assuming you have less than 50 devices
that use DHCP, set the DHCP range as 2-50 (or higher if you need to).
Then set the Static address in the RTV to end in something like .88. You
don't need to set the address reservation. The RTV should connect and
use the new address although it won't show up in the "Attached Devices"
list which is only for DHCP.
Now you have the best of both worlds and, if the IP assignment truly
was your problem, it should be fixed.
From:Larry Moss
moss@airigami.com
> On 2004-10-12, Tony D <nospam@nospam.com> wrote:
>
>> There is a well known bug that allows the hw and sw to have
>> different IP addresses. Replays should be configured with static ip
>> addressses on a network that has a DHCP server. The server should be
>> set for reserved ip for the Replay and the lease time set to a week
>> or so. By doing this you insure that when a Replay reboots all parts
>> of it get the same ip address. There is a possibility you have a
>> flaky network chip, but try this first. Also do not warm boot the
>> machine after you make all these changes. Unplug for 10 minutes.
>> When the unit starts up, it may take 5-10 minutes to boot for the
>> first time.
>
> I used the Replay on this network for quite a while before this
> problem cropped up. If my current problem is related to the bug
> you're talking about, I wonder why I never ran into it before.
>
> 1. So, here's what I've done after reading the whole thread:
>
> 2. Set the router (netgear wgr614) to reserve the IP address for MAC
> address of the RTV.
>
> 3. Set the RTV to dynamic addressing (the way it was).
>
> 4. Unplugged RTV for a while.
>
> 5. Rebooted. RTV got the IP it was supposed to.
>
> As before, it worked for about 10 minutes. Then it disappears from
> the network. So, I went back and did the whole thing again, but
> changed (3) to the same static IP that the router is set to give it.
> Same thing happens. It starts up fine. 10 minutes later, it fails.
>
> The only thing I didn't do is change the lease time. It doesn't
> appear that the router will let me do that. I'm not sure what the
> length of the lease is, but that seems awfully short.
>
> I suppose another thing to try is to turn off DHCP on the router
> completely just to see what would happen. I can't keep it that way,
> but it might be worth the experiment. the problem is, I've got a 1
> year old in the house and finding time that I can do anything is
> impossible. I get to try one experiment a day, it seems.
>
> thanks again for the help.
>
> --
> Larry Moss, http
/www.airigami.com
> PO Box 23523, Rochester, NY 14692, (585) 359-8695
> Airigami: The art of folding air in specially prepared latex
> containers.
Let me make one more suggestion. Assuming you have less than 50 devices
that use DHCP, set the DHCP range as 2-50 (or higher if you need to).
Then set the Static address in the RTV to end in something like .88. You
don't need to set the address reservation. The RTV should connect and
use the new address although it won't show up in the "Attached Devices"
list which is only for DHCP.
Now you have the best of both worlds and, if the IP assignment truly
was your problem, it should be fixed.
From:Larry Moss
moss@airigami.com
> On 2004-10-12, Tony D <nospam@nospam.com> wrote:
>
>> There is a well known bug that allows the hw and sw to have
>> different IP addresses. Replays should be configured with static ip
>> addressses on a network that has a DHCP server. The server should be
>> set for reserved ip for the Replay and the lease time set to a week
>> or so. By doing this you insure that when a Replay reboots all parts
>> of it get the same ip address. There is a possibility you have a
>> flaky network chip, but try this first. Also do not warm boot the
>> machine after you make all these changes. Unplug for 10 minutes.
>> When the unit starts up, it may take 5-10 minutes to boot for the
>> first time.
>
> I used the Replay on this network for quite a while before this
> problem cropped up. If my current problem is related to the bug
> you're talking about, I wonder why I never ran into it before.
>
> 1. So, here's what I've done after reading the whole thread:
>
> 2. Set the router (netgear wgr614) to reserve the IP address for MAC
> address of the RTV.
>
> 3. Set the RTV to dynamic addressing (the way it was).
>
> 4. Unplugged RTV for a while.
>
> 5. Rebooted. RTV got the IP it was supposed to.
>
> As before, it worked for about 10 minutes. Then it disappears from
> the network. So, I went back and did the whole thing again, but
> changed (3) to the same static IP that the router is set to give it.
> Same thing happens. It starts up fine. 10 minutes later, it fails.
>
> The only thing I didn't do is change the lease time. It doesn't
> appear that the router will let me do that. I'm not sure what the
> length of the lease is, but that seems awfully short.
>
> I suppose another thing to try is to turn off DHCP on the router
> completely just to see what would happen. I can't keep it that way,
> but it might be worth the experiment. the problem is, I've got a 1
> year old in the house and finding time that I can do anything is
> impossible. I get to try one experiment a day, it seems.
>
> thanks again for the help.
>
> --
> Larry Moss, http

> PO Box 23523, Rochester, NY 14692, (585) 359-8695
> Airigami: The art of folding air in specially prepared latex
> containers.