Hello all
I'm writing to this list as I feel the current support I am getting will not help to resolve the issue.
I have been receiving NTL Broadband through a NTL:Home 120 Cable modem for the last 18 months. This has been routed through a Netgear WGR614 into my home network which consists of a Dualboot WinXP Pro/Gentoo Desktop, a CentOS (Redhat EL Clone) Mail server, and a WinXP Pro Wireless Laptop.
I will first describe the events as they have occured and then provide the more technical information.
Up until last Tuesday (8th March) all of this equipment had been working just fine together. On Wednesday I awoke to found that connectivity to the internet had ceased but that traffic to the local network was working fine. I reset the router, which has crashed in a similar way in the past, to find that the problem persisted. I rang NTL tech support that morning and was told that maintenance was being carried out and connectivity would return soon. That evening, the connection still was not working and I ran again. Only to be told that the maintenance was carried out from 12am that morning and had finished at 6am. A good 5 hrs before I had rang previously.
Confused, I set about debuging my network setup. Thinking that it was now a local problem. The modem was 'hard reset' to factory settings and the networked computers configured to use DHCP. This did not restore the internet. The router was now flashed to the latest firmware and the process was repeated. Again this was not effective. I proceed to remove the Router from the equation and connected the Modem directly to the Desktop machine. After a modem reset my external connection started to work correctly. Absolving NTL of any, and all responsibility. I had tracked the problem to the router. I proceeded to order a new one thinking that since it was almost a year old it was obsolete and a new one would be better then hours on the phone to the Netgear Tech support line.
Yesterday my new router arrived. A Netgear WGT624. I connected it all together, reset the Modem, powered on the Router, and finally the desktop machine. The result... It still does not allow an external connection.
Cue Tech Support. A call to NTL later, and I had confirmed that the responsibility was not theirs, the modem was functioning correctly according to their remote access software. Read on for reasons why I think NTL have more responsibility then they let on. I spent the better part of 7hrs on the phone to Netgear Tech support yesterday. Running through so many different configurations, firmwares, and combinations of resets on both routers that I have lost count. Currently Netgear have 'escalated' my case number and I am now expecting a call from them. As far as I can tell I've managed to completely stump the India based, read the process of a screen, techs and have now been handed over to someone who may or may not have a qualification in an IT related area.
Now for the technical details. Both routers are apparently able to use the NTL DHCP server to obtain all the correct connection information. On the status pages of both routers is shown the correct gateway and DNS IP's as well as an assigned IP address and netmask. They both appear to have correctly done what they need to do but neither of them route traffic to the internet. Both routers have had MAC masquerading turned on and off. Both have had 'hard resets' and upgrades of firmware. Both have had as many settings fiddled as are to be fiddled with. In short, although they appear to be set up just fine they do not work. Which is what has stumped the Tech support people.
Now for why I belive NTL is possibly responsible.
1. The connection loss occurred right after (or during) a period of maintenance. Up until this point I had had 11 months of reliable service from this setup.
2. A brand new Router, of a different model, failed to connect. With the exact same symptoms (Valid IP, Gateway, and DNS but no connection)
3. This is possibly (In my eyes) the most conclusive evidence yet:
In an attempt to temporarily connect the internet to the network I decided to install a second NIC in the CentOS server and route traffic through it. Redhat by default create everything you need to set this up with the minimum of fuss. Low and behold this new setup is still unable to route traffic to the net. Knowing something about the way Linux works I set about debuging the Network startup scripts. I narrowed the part where it all goes pear shaped down to one command.
Code:
[root@serverpie ~]# dhclient eth0
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on LPF/eth0/00:06:4f:00:ce:41
Sending on LPF/eth0/00:06:4f:00:ce:41
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.67.240.1
SIOCADDRT: Network is unreachable
bound to 82.24.5.75 -- renewal in 76257 seconds.
A quick bit of Googling later tells me that "SIOCADDRT: Network is unreachable" is a 'route' command error and that at this part of the dhclient process it is trying add the default route to the gateway. The gateway through which all forwarded traffic should be directed. Guess what? My CentOS box shows all the symptoms of my routers. It is able to create and manage a local network but it is not able to route traffic to the external interface.
I've got a theory. NTL have done something that, intentionally or not, stops certain DHCP clients from being able to add the nessesary routing commands.
This is everything I've got now. I know nothing more then this. If anyone can shed some light on the situation I would be more then grateful.
Thanks
Mr Wonka
P.S. I'm a Computer Science Student in my final year. 1. I don't need this right now. 2. Why do I get talked to by tech support people like I've only just figured out how to send email?