I just installed a 6141 to replace the Oceanic (Time Warner) Ubee that I had set up in bridge mode so my AEX would provide NAT/DHCP
(Aside, the Ubee pretty much ***** doing NAT/DHCP)
The installation was easy, but the 6141 would reboot and my AEX would end up with "Double NAT"
I thought the 6141 was a "stupid cable modem" but it turns out that it can provide DHCP in the 192.168.0.0 range.
So my AEX was confused and the cable modem was confused.
FWIW: look here, you may find some interesting stuff.
http://192.168.100.1/
I plugged my laptop into the cable modem directly and it received a DHCP address directly from the Oceanic server. It was working fine and the 6141 was not rebooting. I was talking to the Oceanic tech at the time (using the Ubee as my eMTA [or whatever it is to get phone service]) I was wondering if the Ubee was somehow providing a DHCP address over the cable. (Note: One has to install a splitter on the Oceanic cable so that service is provided to both the Ubee and the 6141. NOT All splitters are the same. I "just happened" to purchase one that would support the 1GHz 6141 requirement)
After uselessly debating with the Oceanic Tech about where the DHCP address assigned to the AEX internet ethernet port was coming from and having my laptop connected directly to the 6141 (over en0) for about 30 minutes, when I moved the ethernet cable back to the 6141, it was able to obtain a DHCP from Oceanic. Things are now working "just fine". (I even sometimes get my 100M download, but that is a different issue to look at).
I found this links helpful:
http://www.dslreports.com/forum/r20910726-TWC-How-to-Disable-DHCP-on-Surfboard-M odem-
It specifically said to re-read the 6141 configuration concerning DHCP:
"When the Cable Modem is disconnected from the Internet, users on the LAN can be dynamically assigned IP Addresses by the Cable Modem DHCP Server."
Well, that means the 6141 was NOT syncing with Oceanic as tech support claimed.
This page provided some interesting information concerning Power Levels
http://forums.timewarnercable.com/t5/Connectivity/Please-remove-the-Motorola-Sur fboard-6141-from-your-list-of/td-p/12475
I find my power levels are currently 0dB. I think that's "good", but I'm not a Hardware guy.
I know my Signal/Noise are better than what is listed in this thread. So I'm just wondering what Oceanic did on "their side" to fix things
or if it just took the two systems that long to figure out what was happening.
Also, FWIW, when I first connected the 6141 to Oceanic (via the splitter) it came up right away. There was no problem with it rebooting until I connected the AEX. And it rebooted several times as soon as the AEX was plugged into the ethernet port on the 6141.
Sooo.... I'm suggesting that folks -may- have success if they plug a laptop into the 6141 and allow it to get a DHCP address from the cable provider. Let things stabilize for a bit. Then move the cable back to the AEX that is also configured for DHCP/NAT. "I have no evidence to back this up" (as a former Presidential candidate said) but things are working quite well at the moment.
I am looking for a way of turning off the automatic feature on the 6141 (IMHO a stupid idea that some engineer didn't think through very thoroughly.) The configuration page suggest that there are several manually configurable parameters. But I do not see how.
At this moment, I feel like the 6141 is going to have been a good move on my part.