4

Fing reports Network netmask (prefix length) is not tuned correctly

My fingbox keeps reporting the following:

Network netmask (prefix length) is not tuned correctly

Home network is too wide: 192.168.4.0/22, up to 1024 devices

Is there a way to fix this on my Eero Pro?  I don't see a way for Fing to ignore the alerts.

 

More info:

Code 406: Network netmask (prefix length) is correctly configured

Failure case: Network netmask (prefix length) is not tuned correctly

Network check: information are gathered from your current network

 

Technical definition

The check verifies that your network subnet mask (or network prefix length) is not oversized. Although networking standards recommend to always prefer multicast and broadcast when searching for networking services and devices, many modern IoT devices have still been using unicast sweeps to find peers: this means that lookup, onboarding, pairing or service usage when you have a big network will make the device lookup for the service on a very big number of possible devices, instead of just 256/512. A good example of this is also Windows workgroup: NetBIOS is unicast, so lookup of other PC and printers in a big network takes much longer. The same happens as well to network monitoring software like Fing, Fingbox, and so on: these apps leverage ARP-sweep or ping or similar, so the time taken by a network discovery is proportional to the network size.

What it means for me

A subnet mask is a number that defines the range of (IP) addresses available within a network. It uses the same format as IP address, but in negative format, e.g. 255.255.255.0 is a typical Class C mask including a range of 256 addresses. An alternate form to express it is as network prefix length, meaning how many bits of the network address are stable: a class C network is /24, meaning that 24 bits, first 3 bytes of the address, are not varying.

How I can fix this

An oversized network is much slower than a correctly sized one. E.g. a home network with dozen devices not being a Class C is definitely not tuned correctly. In order to fix it you don't have to change your local PC configuration but rather login into the router configuration and edit it. To make sure every device gets the new updated configuration you should also power cycle or reconnect all connected devices.

23 replies

null
    • julesmoretti
    • 2 yrs ago
    • Reported - view

    Same issue here. No idea why. restarted network, troubleshooted ISP... Changed DNS... nothing.

    • Ranger756
    • 2 yrs ago
    • Reported - view

    OK, but where can I access this field to edit it? I don't see anyplace in the Eero app that gives access to this. Trying to log in directly to the eero is denied...

    • Calion
    • 2 yrs ago
    • Reported - view

    Has this been addressed? I’m getting the same error.

    • Calion
    • 2 yrs ago
    • Reported - view

    *bump*

    • Luella
    • 2 yrs ago
    • Reported - view

    I appreciate what you did.    
        

      • Luella
      • 2 yrs ago
      • Reported - view

      Luella 

      Thanks again >> MCDVOICE

    • eero_support
    • 2 yrs ago
    • Reported - view

    Hello everyone,

    Based off what the OP posted it looks like you just need to change the subnet mask to change it to a class C. I didn't see a list of any troubleshooting steps taken so far so I will suggest changing to manual IP which is in Settings -> Network Settings -> DHCP & NAT. Select Manual IP and you will be able change the subnet to 255.255.255.0 which should solve this. Can anyone give this a try and let me know if the device is still reporting the message?

      • Calion
      • 2 yrs ago
      • Reported - view

      James After changing DHCP & NAT from Automatic to Manual IP and changing the Subnet IP from 192.168.0.0 to 255.255.255.0, tapping Save, and tapping Reboot, I received the following message: “We couldn’t update your settings. We ran into an issue updating your settings. Please check to make sure you entered the right values and try again."

      • Calion
      • 2 yrs ago
      • Reported - view

      Calion Am I doing something wrong here? Should I be changing the Subnet *mask*, not the Subnet IP, to 255.255.255.0? To be honest, I’ve never been quite clear on what these settings do.

       

      • Deb
      • 1 yr ago
      • Reported - view

      James or Calion - Any confirmation as to whether or not this solves the issue? I'm seeing the same thing on my Fing and it doesn't look like this was fully resolved here...?

      • Calion
      • 1 yr ago
      • Reported - view

      Deborah I never got clarification on whether he was referring to the Subnet IP or the subnet mask, so no. 

      • Calion
      • 1 yr ago
      • Reported - view

      James Could you clarify the above? I am having difficulty following your instructions. 

      • bigtree
      • 1 yr ago
      • Reported - view

      Calion He is referring to the subnet mask.  By default, it is 255.255.0.0.  Change it to 255.255.255.0.

      • bigtree
      • 1 yr ago
      • Reported - view

      James yes, this resolves the problem, thank you.

    • PKBris
    • 1 yr ago
    • Reported - view
    bigtree said:
    He is referring to the subnet mask.  By default, it is 255.255.0.0.  Change it to 255.255.255.0.

     I am getting the same issue/notification from Fing. When I do the above in Manual IP and enter the 250.250.250.0 it says I also need to enter Subnet IP as well? Note that when I change setting to Manual IP the lease range is all blank (subnet mask, subnet IP, starting IP and Ending IP are all blank. Am I supposed to be entering something in these others as well? If so then what please?

      • bigtree
      • 1 yr ago
      • Reported - view

      PK 255.255.255.0 not 250.250.250.0.  Subnet IP can be 192.168.0.0 if that is what you have your IP address prefix set to. Other values can work, but I am using 192.168.0.20 for the starting IP and 192.168.0.254 for the ending IP.

      • PKBris
      • 1 yr ago
      • Reported - view

      bigtree thanks for your input. I followed your advice and it now seems ok. So much for Eero settting it up automatically to the best settings. Mind you, I cant see that it has made any difference to speeds and such :-)

    • Calion
    • 1 yr ago
    • Reported - view

    Odd. My Subnet IP is the same as my IP address prefix: 192.168.0.0. The starting is 192.168.0.20, and the ending is 192.168.0.254  I didn't set or change any of that. Maybe leave it on Automatic, restart the eero, and try again?

    • varocketry
    • 9 mths ago
    • Reported - view

    SO how and where do I log in to access the EERO router and make these changes.  Is it locked by the cable company?  Or is there something I have access to.

    Is there a LAN IP address to access it?

      • Michael_eero_support
      • 9 mths ago
      • Reported - view

      varocketry There is not.  The eero cannot be logged in directly over the network.  An eero is controlled via the eero app.  When you setup the network you would have downloaded the eero app, created an account and setup the network.  If the network was setup by an ISP or a custom installer they should have transferred it to your data so you can create an account.

      If necessary give eero support a call so we can check into the network (make sure to have a serial number handy) so we can help you get logged in.

      • varocketry
      • 9 mths ago
      • Reported - view

      Michael_eero_support  Thanks. I do have the app installed.  I will look closer to find those required settings.

      • Michael_eero_support
      • 9 mths ago
      • Reported - view

      varocketry You will find the DHCP settings in eero app->Settings->Network Settings->DHCP & NAT.

      If you let us know what IP address range you are wanting to use we can provide the numbers you would need to stick in.

    • bradmyers
    • 2 mths ago
    • Reported - view

    Same issue happening with me.  I'm running a 255.255.252.0  (/22).  192.168.4.1 gateway.. up through 192.168.7.255.  Everythings working, although Cox internet keeps dropping and I'm not sure if it's potentially related to this.  All internal communications continue to work with out any problems.

Content aside

  • 4 Likes
  • 2 mths agoLast active
  • 23Replies
  • 820Views
  • 15 Following