Tsudohnimh wrote:
I floated your article to the Comcast guy on Twitter and not surprisingly he said the problem lies with the modem. http://tr.im/2bs8

Quoted from him, "That is what happens when a modem is not connected to the network."

I don't but that at all. It doesn't begin to explain why the Modem ACK. Good luck trying to get further.

Keep us in the loop.

Thanks for trying but you can see why this is hopeless. In response to what he said:

1. I am not "off base." I know exactly what I am talking about. I used to be a senior engineer at a large ISP.

2. He did not carefully read what I wrote. I KNOW that the cable modems hand out 192.168.100.10 before they get connected to the cable network. I specifically discuss that in the text! That is not the problem that I have, and had he actually read what I wrote he wouldn't be confused about that. For the record, the problem is that after getting that IP from the cable modem, his network won't give me a real lease once the real cable network is connected.

3. That attitude from Comcast employees is exactly what makes this so frustrating. Their network must not be broken, therefore I must be "off base," therefore there is no reason to pay careful attention to what I'm saying. It is because they approach this with that sort of attitude that this problem will never be resolved.

RE: Comcast's DHCP is broken