G3100 - Non-existent STB IP in the middle of DHCP Range
RanHug00
Enthusiast - Level 1
Under "Advanced" in the "Security & Firewall" -> "Port Forwarding" area, under "Rules List", there is a rule which has no provision for deletion that sends UDP port 63145 to the local LAN's host ".100".  A little web searching reveals this is a "traditional" IP for Fios' set-top-box.  I don't have no STB of any kind.
 
My DHCP address pool goes from ".2" through ".254", and thus ".100" is eventually assign-able.  I have no host on the LAN statically assigning itself to ".100", so the G3100 will never know not to assign that IP to a DHCP request.  It's my understanding that I cannot make a DHCP reservation of ".100" on the G3100 for a mythical MAC address while still maintaining a DHCP pool that includes the "100" address.  [I'm sorta hoping I'm wrong on this.]
 
I no longer remember how the G3100 initially allocated the DHCP pool, and it may well have been either ".2" through ".99" or perhaps ".101" through ".254", both of which would be coherent designs after assuming everyone would have a STB and pre-assigning ".100" for it.
 
- Is there a secret way to delete the seemingly hardwired rule for UDP 63145 to host ".100"?
- With the rule left in-place, would some future assignment of IP ".100" to an arbitrary network device like a PC or phone cause problems with Verizon [or with the device itself] when UDP 63145 traffic arrives and perhaps doesn't get the expected response?
- Will Verizon even try UDP 63145 traffic if I am not registered as having a Set-Top-Box?
 
Should I just truncate my DHCP pool to one side of ".100" and move on?
 
Thanks!
Labels (1)
0 Likes
Reply
1 Solution
RanHug00
Enthusiast - Level 1

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.

View solution in original post

1 Reply
RanHug00
Enthusiast - Level 1

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.