STBs self-assigning private IPs, need STB passwords
ConsultingSvcs
Enthusiast - Level 3

My STBs seem to be self-autoassigning IPs in the 169.254.0.0/16 range which is problematic because I have a firewall between the STBs and the ONT with outgoing rules that are IP-based. Thus I'd like to get into the configuration for each to either assign static IPs or properly configure DHCP. I've located a configuration page at port 8082 for each of the STBs but haven't been able to determine the password and username. Can someone enlighten me?

0 Likes
1 Solution

Correct answers
Re: STBs self-assigning private IPs, need STB passwords
prisaz
Legend

I have seen this with the Motorola devices. Unlike Cisco that get two identifiable IP addresses from the DHCP in the router, the Motorola boxes use an automatically assigned IP address for the MOCA to do broadcasts for communications between the STBs. So the Motorola theoretically also use two IP addresses, just not visible to most. If you run wireshark on your network, it is very visible.  These as far as I know can not be set. They are almost like the IP addresses range that would be set by series of PCs that don't have static IPs, or IPs set by DHCP. I was annoyed by the constant broadcasts and logging on my firewall.

I know my profile now says I have Extreme 50/20 and Cisco, at the time of this thread I had motorola. Not sure what you are looking to accomplish, but this was my issue with Motorola and the constant broadcasts and traffic on 169. I believe it is just used between the boxes, and if you want the CID or remote DVR to work, you must use Verizon's supported functions. Good luck getting Verizon's back door password into the STB., because I do not think that will happen.

See this thread.

http://forums.verizon.com/t5/FiOS-Internet/MOCA-Broadcast-and-Multicast-on-LAN-from-the-MOCA-network...

Solution for me.

http://forums.verizon.com/t5/FiOS-Internet/MOCA-Broadcast-and-Multicast-on-LAN-from-the-MOCA-network...

Funny now that I have two real IPs on the Cisco boxes, I still get the stupid broadcasts.

 The Internet Assigned Numbers Authority (IANA) has reserved 169.254.0.0-169.254.255.255 for Automatic Private IP Addressing. As a result, APIPA provides an address that is guaranteed not to conflict with routable addresses.

So these are used between the STBs and do not go out on the Internet. I believe it may be intentional for them to be configured this way. But with the constant broadcasting, and local trafic, I too found it very annoying.

View solution in original post

Re: STBs self-assigning private IPs, need STB passwords
lasagna
Community Leader
Community Leader

So, where is the Verizon supplied router in your configuration?

As you reference your own firewall, I'm going to assume you removed the Verizon router from the picture and this is where your problem originates.  When you have TV services involved, the Verizon router really needs to be in the picture as you need the bridging capabilities it provides to enable to the STB's to function.

The STB's do automatically DHCP addresses from the local network -- however, they don't talk to the ONT for this.  They use MoCA (ethernet over Coax) to speak to a local network device which hands out the address -- the Verizon router is a MoCA enabled device which bridges the Coax ethernet LAN with the wired/wireless ethernet LAN also provided by the router (and on which a DHCP server is listening).

If you've removed the Verizon router, you've removed the necessary bridge to the local LAN in order for the boxes to get their path to the internet.

You need to bridge the Coax network back to the local LAN again -- either by returning the Verizon router to the configuration or installing a MoCA adapter (ActionTec HME2200/ECB2200 for instance).

Note that by removing the Verizon router, you will not have any of the remote Verizon service capabilities (remote DVR, etc.) the require inbound mapping thru your router.   While conceptually these could be made to work, Verizon depends on being able to remotely configure the router to set them up and if it doesn't see a Verizon router to speak with, will refuse to setup the services.

Re: STBs self-assigning private IPs, need STB passwords
ConsultingSvcs
Enthusiast - Level 3

I have the ActionTec installed on the LAN as a MoCA-LAN bridge to provide on-demand and TV guide (I don't use DVR). That's all the ActionTec does though; DHCP, WLAN, NAT, DNS, etc are all on dedicated devices. The firewall is configured to open up the requisite ports for communications between the bridge/STBs and Verizon and on-demand and the guide work fine.

More importantly though, my DHCP server is leasing IPs to the STBs over the MoCA bridge and they're accepting them, using them to communicate with Verizon, and respond to LAN traffic sent to those addresses (192.168.0.0/24 range). The strange part is that the STBS are also assigning themselves a second IP, apparently on the same interface (same MAC as the 192.168 address at least), but in the 169 range. And they respond on that address as well. What??

My firewall denies anything that is not explicitly allowed, so it denies all the traffic from the 169 addresses, which hasn't been a problem for STB functionality. Nevertheless, I don't like this mystery traffic or strange IP range on my LAN. Any ideas what's going on here? Also, any ideas what is on that configuration page at port 8082 on the STBs? I have a feeling I could correct this issue if I could get into that config page.

0 Likes
Re: STBs self-assigning private IPs, need STB passwords
jackmcgann
Specialist - Level 1

Are the STB's in question Cisco devices?

They are known to require two IPs.

0 Likes
Re: STBs self-assigning private IPs, need STB passwords
ConsultingSvcs
Enthusiast - Level 3

No they're just the regular Motorola HD boxes.

0 Likes
Re: STBs self-assigning private IPs, need STB passwords
prisaz
Legend

I have seen this with the Motorola devices. Unlike Cisco that get two identifiable IP addresses from the DHCP in the router, the Motorola boxes use an automatically assigned IP address for the MOCA to do broadcasts for communications between the STBs. So the Motorola theoretically also use two IP addresses, just not visible to most. If you run wireshark on your network, it is very visible.  These as far as I know can not be set. They are almost like the IP addresses range that would be set by series of PCs that don't have static IPs, or IPs set by DHCP. I was annoyed by the constant broadcasts and logging on my firewall.

I know my profile now says I have Extreme 50/20 and Cisco, at the time of this thread I had motorola. Not sure what you are looking to accomplish, but this was my issue with Motorola and the constant broadcasts and traffic on 169. I believe it is just used between the boxes, and if you want the CID or remote DVR to work, you must use Verizon's supported functions. Good luck getting Verizon's back door password into the STB., because I do not think that will happen.

See this thread.

http://forums.verizon.com/t5/FiOS-Internet/MOCA-Broadcast-and-Multicast-on-LAN-from-the-MOCA-network...

Solution for me.

http://forums.verizon.com/t5/FiOS-Internet/MOCA-Broadcast-and-Multicast-on-LAN-from-the-MOCA-network...

Funny now that I have two real IPs on the Cisco boxes, I still get the stupid broadcasts.

 The Internet Assigned Numbers Authority (IANA) has reserved 169.254.0.0-169.254.255.255 for Automatic Private IP Addressing. As a result, APIPA provides an address that is guaranteed not to conflict with routable addresses.

So these are used between the STBs and do not go out on the Internet. I believe it may be intentional for them to be configured this way. But with the constant broadcasting, and local trafic, I too found it very annoying.

Re: STBs self-assigning private IPs, need STB passwords
ConsultingSvcs
Enthusiast - Level 3

Thanks prisaz, that was exactly what I was looking for and answers my primary question.

I'm still a little concerned about that web interface at port 8082, particularly why Verizon needs it and what they (or someone with more nefarious purposes) could use it for on my network. I just don't like having things I can't access on my own network. That said, it should be fairly difficult for someone to get at the STBS from outside considering that traffic isn't forwarded by my firewall.

Re: STBs self-assigning private IPs, need STB passwords
prisaz
Legend

@ConsultingSvcs wrote:

Thanks prisaz, that was exactly what I was looking for and answers my primary question.

I'm still a little concerned about that web interface at port 8082, particularly why Verizon needs it and what they (or someone with more nefarious purposes) could use it for on my network. I just don't like having things I can't access on my own network. That said, it should be fairly difficult for someone to get at the STBS from outside considering that traffic isn't forwarded by my firewall.


I agree, so I have a linux box as a second firewall, and Verizon is the DMZ. My network is my network, Nothing should have access without my knowing it, or allowing it.

0 Likes