Bridge mode

---

@skymeat wrote:
Can you explain technically why it's not available with a static?

---

Yeah, bridge mode disables all routing capabilities of the gateway and essentially turns it into a regular retail cable modem. Comcast uses specific routing technologies to allow customer-assigned static IPs onto their network, and bridge mode disables these technologies.

If your gateway has been provisioned properly with your static IP, you should be able to configure any of your own devices with your static IP information and just plug it into the gateway's ethernet ports. The gateway will allow all traffic to/from static IP devices. Make sure that the gateway's firewall settings (available at http://10.1.10.1 ) are configured to "Allow all traffic through" - this should be a checkbox on one of the configuration pages.

The gateway is your ethernet handoff, in essence.

Not sure if this will help anyone else, but this is the sort of search I was doing before starting:

multiple (5) static IPs, QoS router behind Cisco modem and NOT in bridge mode.

For those that haven't figured it out, they have set the modem up to pass the public/static IPs through to the LAN side, so if you have a device that answers to your static IPs on the LAN side, the comcast modem will pass the traffic to it (out of the box, as configured during install).

That is, you assign the provided public IP/NETMASK/DNS to either a computer or a route in another router on the LAN side of the comcast modem and it will make it appear as if it is directly connected to the internet.

You can either filter the ports in the comcast modem, or disable the firewall and pass everything to those IPs.

In my case, I clamped down the comcast firewall as tight as possible, defaulting to block, passing only those ports I need for services I provide.  This is redundant as the QoS router also blocks all but those ports served, but the sooner I stop bad traffic the better as far as I am concerned.

So, the comcast router passes my 5 static IPs to an internal router (Netgear proSafe) that is itself in NAT mode.  It maps WAN->LAN by treating the Comcast (Cisco) LAN side as "the internet".  So, I have NAT rules for each open port:

PORT, PUBLIC_STATIC_IP, INTERNAL_IP, QoS_RULE

This allows me to prioritize various types of traffic as needed (an throttle nuissance, but reuired traffic).  It does make some bold assumptions about how the comcast modem is responding to the internal router stalling it, but so far it seems to behave itself (i.e. not lock up and do nothing on other ports while waiting for a throttled port). 

Using this method you can also have DHCP clients that are NOT behind the QOS router (i.e. connected to the comcast LAN side in parallel with the internal router), but that just complciates things and potentially removes the benfit of QoS.

Hope that helps, it would have helped me understand what I was doing last week getting setup.  It is odd that comcast has such a sizeable hunk of hardware without even crude QoS.  Seems like a huge oversight.