TiVo Community Forum banner
1 - 9 of 9 Posts

· Registered
Joined
·
27 Posts
Discussion Starter · #1 ·
Does anyone know if the MM1000 moca adapter IP can be manually configured? Or is it DHCP?
The manual only makes mention of the IP address 192.168.0.2 for upgrading the firmware. I didn't see a any network configuration screens in the GUI, which was a bit disappointing.
 

· Registered
Joined
·
2,615 Posts
Does anyone know if the MM1000 moca adapter IP can be manually configured? Or is it DHCP?
The manual only makes mention of the IP address 192.168.0.2 for upgrading the firmware. I didn't see a any network configuration screens in the GUI, which was a bit disappointing.
Sorry no specific answer, but I doubt it. What are you hoping to accomplish by doing this, if one might ask?
 

· Registered
Joined
·
27 Posts
Discussion Starter · #3 ·
I guess I'm just curious how the MM1000 is getting its IP of 192.168.0.2 when connected direct to my laptop for firmware updates. Is it something like -
IF no DHCP acknowledgement THEN set IP to 192.168.0.2
IF DHCP acknowledged THEN obtain IP via DHCP

It's not imperative that it be set static for any purpose. I generally like to assign IPs to things like network bridges, media centers PCs, extenders, etc. Anything else like laptops, tablets, phones, etc. can just get whatever random IP the DHCP server spits out.
My home LAN has a /24 mask, which wouldn't play nice with the 192.168.0.x subnet used by the MM1000. If the "logic" I've mentioned above is accurate, then there will be no issue. Furthermore, if the unit does use DHCP, I could set a DHCP reservation on my router for the MM1000.

It's mostly about understanding this new device I'm adding to my LAN... and keeping tabs on everything on my LAN.
 

· Registered
Joined
·
2,615 Posts
I guess I'm just curious how the MM1000 is getting its IP of 192.168.0.2 when connected direct to my laptop for firmware updates. Is it something like -
IF no DHCP acknowledgement THEN set IP to 192.168.0.2
IF DHCP acknowledged THEN obtain IP via DHCP

It's not imperative that it be set static for any purpose. I generally like to assign IPs to things like network bridges, media centers PCs, extenders, etc. Anything else like laptops, tablets, phones, etc. can just get whatever random IP the DHCP server spits out.
My home LAN has a /24 mask, which wouldn't play nice with the 192.168.0.x subnet used by the MM1000. If the "logic" I've mentioned above is accurate, then there will be no issue. Furthermore, if the unit does use DHCP, I could set a DHCP reservation on my router for the MM1000.

It's mostly about understanding this new device I'm adding to my LAN... and keeping tabs on everything on my LAN.
The IP 192.168.0.2 is only used with a direct Ethernet connection to the adapter to a PC, you cannot reach it via your LAN. There is no reason to reserve an IP for the device itself, if you want to reserve an IP for a device connected to it, then do that. Your router is still the device which controls IP's on a MoCA network.
I believe you are over thinking this.
 

· Registered
Joined
·
492 Posts
The MM1000 is acting the same as a standard dumb ethernet switch, and isn’t assigned a DHCP address from your router that will appear on your router DHCP table, nor can you change the address on the MM1K.. You can access the diagnostics page from a router connected computer by changing the IP address on the PC to an open address in the same range 192.168.0.x segment of the underlying MM1K, but you will only be able to change configurations for the first controlling node that comes up, although node to node rates are displayed for all devices. Firmware updates or frequency channel changes have to be done one device at a time via direct connection.
 

· Registered
Joined
·
27 Posts
Discussion Starter · #6 ·
"I believe you are over thinking this."
Guilty... I tend to do that.

Both of your responses have cleared up my lack of understanding. Much clearer now.
I had envisioned the device would just pass traffic, as you suggested. I was just thinking it would have an IP on the LAN for configs and monitoring (besides the aforementioned IP).
Thank you both for the clarification.
 

· Registered
Joined
·
20 Posts
The devices all have a static address of 192.168.0.2. The reasons you'd want to access the devices are to enable encryption and/or change the frequency it operates on.

There are a couple of "hacks" I've found. One is that you can have two IP addresses on your computer, such that you can be on your normal home network and be connected to the 192.168.0.x network that the Motorola MoCA devices use for management access. Second, you can manipulate your computer's ARP table to be able to get to more than one of these devices without having to physically connect directly to them. I have 3 of these devices and use this to verify connectivity before and after working on my coax network.

First, find the MAC address of each of your devices and record these on your computer (you'll want to be able to cut and paste them so you don't make mistakes). This is listed on the bottom of each device.

Get your computer connected to the 192.168.0.x 255.255.255.0 ( /24 ) network (note you cannot use 192.168.0.2 - as that is what the Motorola MoCA devices are all using). This will vary depending on your OS. Hack #1: For Linux, I bind it as an additional IP address on my existing network interface (Windows and MacOS can do this as well). So I have my normal network IP statically assigned, plus I add a 192.168.0.5 /24 ( /24 is just bit-based mask notation for 255.255.255.0), and no default gateway for that IP.

Once you're on this network, try to ping 192.168.0.2. One of your Motorola MoCA devices will respond, but you don't know which. Look at your arp table. This command's flags will vary by OS, but for Linux it is:
apr -a

You can browse to whatever device first responded to the arp request (the arp request occurred when you did the ping) at http://192.168.0.2/

Here you can set a basic encryption key and enable encryption (available with firmware 1.0.0.8, but all of mine came with this firmware, or you can manually upgrade them to this version). Motorola MoCA encryption prevents a casual eavesdropper from accessing your MoCA network if you share the physical coax network.*

Ok, so the Hack #2 is manipulating your ARP table such that you can specify which IP:MAC association you want to have in place, which will then allow you connect to a specific Motorola MoCA device.

In Linux I paste these 3 lines all at once:
sudo arp -d 192.168.0.2
sudo arp -s 192.168.0.2 e4:90:7e:AB:CD:EF
arp -a


Here is a breakdown of what each does:
Delete the current ARP table association with 192.168.0.2
sudo arp -d 192.168.0.2
Statically set the ARP table association to the MAC address of a specific Motorola MoCA device:
sudo arp -s 192.168.0.2 e4:90:7e:AB:CD:EF
Review the ARP table to make sure it was set as expected:
arp -a

Then refresh my browser at http://192.168.0.2 and verify on the Device Info page that I'm talking to the right S/N and MAC address. Additionally, on the Node Info page I can see all of my MoCA nodes. So long as I always connect and power them on in the same order, the Node # remains the same.

Now say I want to talk to my second node, I just paste in the lines I have stored for it:
sudo arp -d 192.168.0.2
sudo arp -s 192.168.0.2 38:80:df:FE:CC:BA
arp -a


Here are some Motorola links, one of which has the latest firmware:
Support for MM1000 - Motorola Network
MM1000 Firmware Update - Motorola Network

*Coax network security: depending on your setup, you may be piggy-backing on the CableCo's neighborhood coax network, or be splitting a coax connection and connecting all of your home coax network to the same CableCo's network. One step better (or in addition to) the Motorola MoCA encryption is to use the PoE filter between the CableCo's network coax network and your home. The absolute best security is to just have two different physical coax networks. But this isn't always possible, and/or perhaps you share a building with roommates and don't trust them to be on your private networks, etc. Note: a dedicated adversary can just try all combinations of the 12-17 digit "Security Password" until they found the correct one. Physical security is king, as always.

Note: I'm not using any non-Motorola MoCA devices, so I don't know if the Motorola MoCA "Securty Password" is compatible with any other MoCA devices. However, there appears to be a MoCASec standard that uses 12-17 digit passwords, which matches what the Motorola is doing.
MoCASec Peer-to-Peer MoCA Link Security

The Tivo-branded bridges are just Actiontec ECB6000 devices and support MoCASec as show in a picture in this post:
Moca intermittent issues

Do the TiVo MoCA-based Minis support MoCASec? Nothing I can find when searching the tivo.com website mentions MoCASec or MoCA Security.
 

Attachments

  • Like
Reactions: krkaufman

· Lord of the Rings
Joined
·
7,867 Posts
You can switch the mm1000 to use DHCP:
MM1000 Bonded MoCA?

TL;DR: When you have access to its default 192.168.0.2, put this into your address bar: http://192.168.0.2/cmd.sh?ifconfig&auto

If you look at the post linked above, you can give it a new static IP address if you want instead.
Code:
ifconfig [ -stats ] | [ auto ] |
        [linklocal] |
        [<ipaddr> [<netmask> [<gw>]]]   -- Display or configure IP address
So I suspect (haven't tried) you could do:
http://192.168.0.2/cmd.sh?ifconfig&192.168.0.100&255.255.255.0
to set it to a different IP.

I also posted a Tampermonkey script to fix and enhance the Node Info page, which was otherwise pretty broken.
 

· Lord of the Rings
Joined
·
7,867 Posts
All MoCA-compatible TiVos support MoCA-sec, and they are compatible with MM1000's and other MoCA devices. I've used TiVo (Bolt and Mini), Netgear (MCA1001), Motorola (MM1000) and Verizon (MI-424, several revisions) hardware all on the same MoCA network with a security password and they all work fine together. Setting that password can be a pain, but once done, it just works.
 
1 - 9 of 9 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top