An unfamiliar connected-device name can be a renamed household device; a label alone is not proof of intrusion.
Before you change anything
This is a diagnostic entry point. The source supports the general check, not a confirmed root cause for your device.
What to check first
Which observed symptom, exact model and firmware changed before the failure?
Record the exact model, hardware revision, firmware and recent change before adjusting settings. If you cannot answer the question, keep the cause open.
Narrow the likely path
| Observation | Next check |
|---|---|
| Gaming NAT warning | Classify upstream routing and CGNAT before opening ports. |
| Firmware or restart issue | Check the precise revision, power and vendor recovery instructions. |
| Security or DHCP issue | Record current settings, local address ranges and device identity before altering access. |
Decision after the first test
Compare device MAC/vendor details privately with your own inventory and disconnect one known device at a time before blocking it.
Use a documented next step
Verify before escalating
After each change, repeat the exact failed task. If the result is unchanged, restore the previous setting and use the official support link for your exact hardware revision. Don’t assume a menu or capability from a related model.
Official sources
- AT&T DMZ+ article with BGW210/BGW320 passthrough section (full_text; checked 2026-11-01)
Check your exact US model, hardware revision, and firmware on the linked support page before changing settings.