Not getting an IP address

Yeah, tried that, and replacing the network cord, too. And disconnecting the house from the other network port.

Unfortunately, my router is in bridging mode, so I can't log in to the router.

Here are some simple diagnostic hints:

1.  Connect a different single system, not your Linux box, directly to the modem. The system should be configured for automatic address configuration (DHCP).

2.  Cycle the Modem power.

3.  Wait for the Modem to be reconfigured.

If your different single system does not eventually get an IP address, it is time to call Comcast. But, Wait...

Before you call Comcast, try using your browser to access the Modem management pages and print the various tabs for reference while talking to Comcast.

Yep, I do.

Just got off the phone with them.  She switched it from bridging mode to "normal", and I could get an IP address fine.  It just failed when in bridging mode.

Bridging was easier for my network, but I think I can deal with this setup by putting my home server on the DMZ, and changing my dynamic DNS service to use an external website instead of updating all of my DNS records with a 10.* address.

Apparently you have a Comcast-supplied Modem/Router.

Comcast support number is  1-800-391-3000.

Hello CyberKnight and welcome,

If your Linux Server network configuration is setup for dynamic IP access and is not using a staticIP address, then I would recommend that you use 10.1.10.2 through 10.1.10.9 for your dedicated network IP address. This is predicated on your Comcast Gateway's (CG) LAN DHCP server is default configured for the dynamic range of 10.1.10.10 through 10.1.10.199.

Your Linux Server NIC MUST be Enet connected to one of the CG LanPorts 1-4 for it to use one of the above recommended IP Addresses. Could you tell us a little more about your nextwork configuration because if your Linux Server is providing your intra-network DHCP Server, then you may be in a DHCP conflict situation. But this is not clear until you clarify.

Hope this helps you out.