Incorrect Hostname Reporting?

Comments

5 comments

  • Avatar
    Firewalla

    One possibility is somehow the devices changed IP addresses, and for a moment, the old IP was tied to a new device.  Are you using the production 1.961 code? or the beta 1.963?  

  • Avatar
    Stormy Daniel

    Production code. Both devices are DHCP, but I don't think either of them have been rebooted or have renewed leases in a long while. Ill keep an eye on them...

  • Avatar
    FF

    Same issue here:

    a number of devices are listed under their MAC-address vendor name instead of their hostnames.

    I also confirmed that that reverse dns lookup resolution works properly so if firewalla were to use the name provided by the router it wouldn't have any issues:

    nslookup 192.168.0.240 192.168.0.1
    240.0.168.192.in-addr.arpa name = foo.bar.mooo.com.

    setup:

    • router(with dhcp & dns ) = ASUS RT-AC88U = 192.168.0.1
    • firewalla plugged straight into the router running "experimental simple mode"
    • note: some devices are plugged into a TP-link switch in turns plugged into the ASUS router (as opposed to get plugged directly into the router's ports or wifi)

     

     

  • Avatar
    Firewalla

    Depends on the host, it may take a while for the true name to show up... we have 6 different mechanisms to "guess" the name of the device. 

  • Avatar
    FF

    That's interesting, can you please expand on these 6 methods?

    I would have expected to rely on the DNS from the DHCP server to be one of the first.

     

Please sign in to leave a comment.

Powered by Zendesk