Fingbox has 2 IP addresses

tango_golf
tango_golf Member Posts: 1
edited December 14, 2020 in Fingbox #1
Hello - a network scan is showing that single MAC address (with a manufacturer of Domotz Limited) has two IP addresses. Why would this be when I have a single Fingbox. How do I change so that there is only one IP address? 

Answers

  • Thing
    Thing Member Posts: 1
    First Comment Photogenic
    edited December 10, 2020 #2

    Hello there, I have the same problem this ip address is not the router ip. Can someone explain why a fingbox should have two or multiple ip addresses.

  • Robin_from_Fing
    Robin_from_Fing Administrator, Fing Team Posts: 4,882
    250 Answers 2500 Comments 500 Likes 100 Awesomes
    admin
    Hi @Thing @tango_golf
    We recently found out that there is a minor issue within the App that is mixing the source of information across discovery rounds. This cause devices to be correctly identified on the first scan round (until 50% of the scan), but then something goes wrong with the detection of devices from the ARP table and the app fallback to IP only ARP entries mapped over the Fake MAC address: 02:00:00:00:00:00
    This MAC address creates a new Node in the network and all the detected IPs are collapsed on it. This issue affects Android 10 and Android 11 only, so far we detected it only on Samsung devices but it may happen on others too, and it’s due to some new limitations introduced by Google. We fixed the problem already and we will release a new version of the app shortly which will cover the fix. 

    Robin (Admin at Fing)
    Getting Started? Please refer to Community guidelines & Community User Guides. HAPPY POSTING!!!
    Thing
  • SRP
    SRP LAMember Posts: 117
    100 Comments 25 Agrees 25 Likes 5 Awesomes
    ✭✭✭
    edited April 27, 2021 #4


    Update: Ignore that. ARP spoofing of blocked devices was creating the additional addresses for the Fingbox.

    @Robin this appears to still be occuring on non Fingbox based scans for my Fingbox from the app with my Pixel 5 and Android 11.

    Do you think this is the same issue occuring again or if it could be some other cause?