Camera Network Addressing in Alvin 77511: Keeping Cameras Findable After Outages and Router Swaps

What camera network addressing actually covers

An IP camera is located by a four-part identity: its IPv4 address, a subnet mask defining which neighbors it reaches directly, a default gateway for everything else, and a DNS server that turns names into numbers. The recorder stores each channel as an address, a port and a login. Change any one and the channel goes dark while the camera hangs on the wall, powered and healthy.

Cameras are only part of the list. A complete addressing job accounts for:

• Every camera, with its web port, its RTSP video port (554 unless changed) and any vendor management port.
• The recorder, which on PoE models has two interfaces: one facing your LAN and an internal one serving the cameras on its back panel.
• Managed PoE switches, where the system uses them. Unmanaged switches carry no address and need none.
• Wireless bridge radios feeding a detached garage or shop.
• Video doorbells and Wi-Fi cameras, addressed by your router rather than the recorder.

Done carelessly, addressing produces the intermittent outage that sends people shopping for cameras they do not need.

The four events that knock Alvin camera systems off their addresses

On the Brazoria County side of Houston the same short list of triggers keeps recurring, each exploiting a shortcut taken at install.

1. The power comes back all at once

After an outage like the long one that followed Hurricane Beryl in 2024, the router, switch, recorder and cameras all boot together. A camera set to DHCP may ask for an address before the router can answer; some models then settle on a factory fallback or a self-assigned 169.254.x.x address until rebooted. Routers that hold their lease table only in memory can also hand a camera a new number while the recorder keeps knocking on the old one.

2. The internet provider swaps the gateway

A replacement modem-router frequently ships with a different private range from the unit it replaces, for instance 10.0.0.x where the old one used 192.168.1.x. Anything typed in by hand on the old range is now stranded on a subnet that no longer exists. Depending on which devices were fixed and which were automatic, either the recorder loses its cameras or the phone app loses the recorder.

3. Someone adds a camera at the shop or garage

New cameras arrive with a factory default address, and units of the same brand usually share the same one. Connect a second camera without changing it and two devices now claim one number. Other equipment on the network keeps revising which hardware answers for that address, so both channels flicker between live and offline.

4. The recorder gets replaced

A new recorder may assign a different internal range on its PoE ports, or it may be another brand that can reach the existing cameras only through ONVIF, the cross-brand standard, which must be enabled on each camera with its own credentials. Channels never migrate by themselves.

Symptom, likely cause, and the permanent fix

That last row matters. Not every offline tile is an address problem, and re-addressing a camera whose real fault is a cracked outdoor connector just adds a second problem to the first.

Static addresses, DHCP reservations, and when we use each

There are three legitimate ways to pin a camera to one address, each with its own failure mode.

Static, set on the camera itself. The camera never asks the router for anything, so a slow boot cannot move it. The risk is choosing a number inside the router’s automatic range, where a phone or smart TV eventually receives it too. Fixed addresses live outside the pool. If the router lends out .100 through .199, cameras might occupy .20 through .59.

DHCP reservation, set on the router. The router recognizes the camera’s MAC address and always gives it the same number, and changes happen centrally. But reservations live inside the router, so a gateway swap or factory reset wipes them.

Plug-and-play behind the recorder. Cameras connected to the recorder’s own PoE ports sit on a private internal subnet that the recorder manages. Nothing competes for those addresses, so it is the most stable arrangement for a simple single-brand system; the cameras’ own web pages are reachable only through the recorder.

For Alvin homes and small shops we generally favor fixed addresses outside the pool, recorded on a written map, because storm outages and provider equipment changes happen often enough on this side of the metro that a reservation-only design tends to get tested the hard way.

Detached garages, metal shops and the far end of the yard

Plenty of Alvin properties, from the older lots near the town center to acreage on the rural edges, have a detached garage or a metal building that someone eventually wants covered. The camera out there reaches the network over buried Cat6 in conduit, a fiber run, or a point-to-point wireless bridge, and each option changes the addressing picture.

• Wireless bridges pass camera traffic transparently, yet each radio carries a management address, and out of the box the pair often share one. We give each radio its own number in the infrastructure block.
• A spare home router used in the shop instead of a switch creates a second network, and the cameras behind it vanish from the recorder’s view.
• Metal walls block Wi-Fi. A Wi-Fi camera mounted on a steel building may keep dropping and rejoining, which looks like an address fault and is really a signal problem. Hard-wiring or a bridge solves it; changing IP settings does not.

What an addressing call in Alvin looks like

1. Inventory. We scan the network and match every device by MAC address to its location and recorder channel.
2. Read the router. LAN range, DHCP pool, reservations, and any second router quietly running its own network.
3. Draft the plan. Blocks for infrastructure, recorders, cameras and future growth, all outside the automatic pool.
4. Move cameras one at a time. Each camera is re-addressed, its recorder channel updated, and video confirmed on both the main stream and the substream before the next one is touched.
5. Set gateway, DNS and time. Every device gets a correct gateway and DNS server, and the recorder syncs time so footage carries accurate timestamps.
6. Close the doors. Default passwords go, router UPnP is switched off, and remote viewing runs through the manufacturer’s app or a VPN.
7. The outage test. With your permission, we cut power to the router, switch and recorder together and confirm that every channel returns without anyone touching a setting. It separates a system that survives storm season from one needing a visit after every outage.
8. Hand over the map. You get the address list on paper and in digital form, with a copy labeled on or near the recorder.

What affects the cost, and the shortcuts that bring us back

You get an itemized quote after an on-site estimate. The main factors:

• How many cameras, bridges, switches and doorbells need to be touched.
• Whether cameras sit behind the recorder’s PoE ports or on a separate switch, and whether brands are mixed and must be joined over ONVIF.
• Whether the camera passwords are known. If they are not, each camera needs a factory reset, which can mean ladder work at the soffit.
• Outbuilding links that need re-addressing or repair before the cameras beyond them can be reached.
• Whether your provider’s gateway allows its LAN range and DHCP pool to be changed.

The mistakes behind most repeat calls: fixed addresses parked inside the DHCP pool; a gateway or DNS field left blank; bridge radios still on their shared default; a camera’s address changed without updating the recorder channel; no battery backup, so boot order is random every outage; and no written record, so the next person starts from zero.

Related services

Frequently asked questions