US Cable Support > Time Warner Internet Services > [TWC] DDW3611 DHCP Server Question

[TWC] DDW3611 DHCP Server Question

Realistically, the easiest way to do this is to bridge the modem. That way each port gets a separate public IP (as they're all internal right now) and passthrough the fifth to a MAC address via your 3rd party router.

reply to dballing
Are you paying for 5 statics or wifi with TWC?

You mention router, dhcp server, and modem... You are just using the 3611 right?

Yes, I'm paying for 5-statics/WiFi.

The DDW3611 is, in fact, all of those things, right? Sorry if I confused matters by using different terms for various aspects of the same box.

But yes, I am (in this case) using ONLY the DDW3611 in its "off the shelf" configuration (well, OTS for the bits that matter, I tweaked WHICH 192.168.XXX subnet I'd be using for private IPs, and I set the WiFi up so it would actually get me my full 50x5 bandwidth).

reply to dballing
If you are paying for statics and WIFI I believe the modem will have the statics available for any host, the host needs to be config'd for the static. The wifi will add advanced gateway services, so the modem will act as a router and hand out 192's to any PC set to dhcp.

Are you seeing a pattern with wifi hosts vs wired?

No, it's really seemingly random.

It's happily handing 192 addresses to hosts on both WiFi and Wired, and the same with the public IPs. (at least right up until I put the dummy "Static DHCP Leases" in the config, which convinced it not to hand them out any more).

reply to dballing
If your paying for statics, and the modem has been scripted for the statics, there is no way the modem will hand out a public ip or one of the statics to any host config'd with dhcp.

Something just doesn't sound right.

It happily was. In fact the DHCP server config in the Ubee even specifically knows about both sets of IPs:

»www.megacity.org/scrap/ubeepubpriv.png

reply to dballing

reply to dballing
184's are not static IPs, they are used for the private IPs to be translated into a public IP.

Anything that was pulling a 184. was a dhcp host on your network, until you assigned the a static to that host.

reply to DrDrew
So, amusingly, I tried using the DHCP Static Leases to actually "meet my needs" and here's what happens:

- If I put a MAC Address/Public-IP combo in there, the devices will simply fail on their next renewal. Unfortunately, I don't have any good DHCP client logging to see the interexchange to see what part of the process is falling over.

- If I put a Public-IP in there, with the default 00:00:00:00:00:00 MAC address, EVEN IF I don't have it "Active", the DDW will not assign that IP address to a DHCP client.

Jabbu: the 184-net IPs *are* my "static" (aka public) IPs assigned by TWC. Yes, clients on my net were DHCP'ing and getting 184-net IP addresses, until/unless I statically assigned that 184-net IP address to some host.

The problem comes from having a number of devices I don't *want* to get assigned a 184-net address (I want my printer, for example, to be sitting in 1918-space, not hanging on a public IP), and having a number of devices I specifically *want* to be getting a public IP (a VOIP phone, for example).

The DHCP server built into the DDW will happily hand out a 184-net address to a DHCP client, we'll call it "randomly", but if I use the DHCP Static Leases to try and force it to give a certain 184-net address to a certain MAC-addressed client, it fails to do so in a functional manner.

Since you have 5 static IPs, assign them statically on the devices that need them. You might want to put them in the DDW just so it doesn't try to hand them out to dynamic DHCP clients, although if it pings IPs before handing them out like many DHCP servers are configured to do, it shouldn't hand them out if they're statically configured on active devices.
--
Two is one, one is none. If it's important, back it up... Somethimes 99.999% availability isn't even good enough.

reply to dballing
What state are you in? The whole east region does not have one account with a static IP of 184.

These have always been dynamic IPs for TWC BC.

reply to DrDrew

reply to Jabbu

Your right, I can't recall ever seeing a modem scripted with statics hand one out to a dhcp host, but I also can't recall being in any network without a router with statics.