G3100 - Non-existent STB IP in the middle of DHCP Range
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solved! Go to Correct Answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The short answer is "never mind". I'd delete the thread if I could.
My initial searching didn't reveal keywords "Verizon Managed" and thus didn't find the discussion at Correct answer: "Verizon managed" devices / IP address range - Page 3 - Verizon Community. It is somewhat fascinating that the G3100 allowed me to set a DHCP range of 2 through 239, and additionally curious that the G3100 DHCP server is honoring my static reservations of IPs between 240 and 254 (which are outside the DHCP range). I do NOT have the devices "fixing" their own IP addresses.
I think the short summary is to assign your DHCP range as some subset of interest from .151 through .254. I've changed mine to be .151 through .239 with some otherwise "fixed" devices between .240 and .254, including the E3200 extender at .254.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The short answer is "never mind". I'd delete the thread if I could.
My initial searching didn't reveal keywords "Verizon Managed" and thus didn't find the discussion at Correct answer: "Verizon managed" devices / IP address range - Page 3 - Verizon Community. It is somewhat fascinating that the G3100 allowed me to set a DHCP range of 2 through 239, and additionally curious that the G3100 DHCP server is honoring my static reservations of IPs between 240 and 254 (which are outside the DHCP range). I do NOT have the devices "fixing" their own IP addresses.
I think the short summary is to assign your DHCP range as some subset of interest from .151 through .254. I've changed mine to be .151 through .239 with some otherwise "fixed" devices between .240 and .254, including the E3200 extender at .254.
