Cable Forum - View Single Post

Mr Wonka · 01-04-2005, 22:35

The saga continues....

My Netgear replacement arrived today. It's a brand new (as in sealed) WGR614 v5. Latest hardware edition as far as I know. It comes as a very fetching white and looks very Mac like. Far nicer then the v2 it replaced.

It doesn't work.

I've fiddled to death. MAC masquerading, static IP, Dynamic IP, MTU. You name it, it's been tweaked.

Looks like I'm going to stick with the DLink then. It has all the aesthetics of a 1980's Sony Walkman and the build quality of a Goodmans CD Player, but it works, so I can always shove it out of sight.

Some Technical stuff
It appears that although I can view the NTL Gateway IP through the interface the router does not route traffic to it. For instance; I can ping any IP on my subnet (Assuming the PC on that IP is on). So if my IP is 82.3.10.156, I can ping any of 82.3.10.*. Including the gateway. This is the exact sympton that my CentOS system suffered when it was connected. I think that it all boils down to the DHCP client not being able to correctly retrieve the gateway IP and set the appropriate routing information for it. Which is also what my manual tweaking on that system showed.

Who's To Blame
As the current Media channels seem keen on, blame has to be appropriated. I blame NTL. During the upgrades to higher speeds they have changed the DHCP implementation (at least in my area). Causing an imcompatibility with the DHCP client used by Netgear routers (Models WGR614, WGT814) and the version of DHClient used by CentOS (Redhat 4 EL).

What will be done
Absolutely nothing. NTL 'do not support home networks' so it's not their problem. Netgear can only change their DHCP implementation to fit. Which won't happen (at least any time soon). I will keep my DLink, flog my Netgear on EBay and then when the contracts up, consider moving to ADSL.

I hope some of this information will be of help to someone.

Thanks
Mr Wonka

Note to NTL Tech's
If any of this can be confirmed, that'd be great.

01-04-2005, 22:35	#16
Mr Wonka Inactive Join Date: Mar 2005 Location: Hampshire Age: 41 Services: NTL TV + 2MB CM Posts: 11	Re: NTL + Router = Hell The saga continues.... My Netgear replacement arrived today. It's a brand new (as in sealed) WGR614 v5. Latest hardware edition as far as I know. It comes as a very fetching white and looks very Mac like. Far nicer then the v2 it replaced. It doesn't work. I've fiddled to death. MAC masquerading, static IP, Dynamic IP, MTU. You name it, it's been tweaked. Looks like I'm going to stick with the DLink then. It has all the aesthetics of a 1980's Sony Walkman and the build quality of a Goodmans CD Player, but it works, so I can always shove it out of sight. Some Technical stuff It appears that although I can view the NTL Gateway IP through the interface the router does not route traffic to it. For instance; I can ping any IP on my subnet (Assuming the PC on that IP is on). So if my IP is 82.3.10.156, I can ping any of 82.3.10.*. Including the gateway. This is the exact sympton that my CentOS system suffered when it was connected. I think that it all boils down to the DHCP client not being able to correctly retrieve the gateway IP and set the appropriate routing information for it. Which is also what my manual tweaking on that system showed. Who's To Blame As the current Media channels seem keen on, blame has to be appropriated. I blame NTL. During the upgrades to higher speeds they have changed the DHCP implementation (at least in my area). Causing an imcompatibility with the DHCP client used by Netgear routers (Models WGR614, WGT814) and the version of DHClient used by CentOS (Redhat 4 EL). What will be done Absolutely nothing. NTL 'do not support home networks' so it's not their problem. Netgear can only change their DHCP implementation to fit. Which won't happen (at least any time soon). I will keep my DLink, flog my Netgear on EBay and then when the contracts up, consider moving to ADSL. I hope some of this information will be of help to someone. Thanks Mr Wonka Note to NTL Tech's If any of this can be confirmed, that'd be great.