Search the Community

Showing results for tags 'new'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 2 results

  1. New

    How to used
  2. Can I say up front that I love Domotz and think that it is sensational software in every respectI have put a lot of effort into setting it up, identifying all the devices on my network (over 40) and have set up a few alerts. Some devices have multiple MAC addresses (i.e. LAN and WiFi) all of which I captured (bringing the total to over 50 network devices). It gave me a great sense of confidence knowing exactly what was connected so I put a lot of effort into this process. Then yesterday I got the alert from hell which said "A new device branded XYZ has joined your network" The alertgave details like name, make and MAC address.This of course put me into a mad panicbecause I had a very good idea of what was on my network. Had my kid given the WiFi password to one of his mates? Had the network been compromised?Then an hour later I got a second alert, then a third.By the time I got home I went into lock-down mode. Changed passwords. Locked the network down to known MAC addresses. Interrogated my kid. Nothing. PRODUCT IDEA Then the thought occurred to me that whenever Domotz detects a new device, it could relatively easily go into"promiscuous mode" and start capturing packets for the new device that has joined the network. That would be very helpful. Packet capture would provide a lot of useful data at this point. For example - if Domotz ever wanted to add an optional extra, you could provide an optional service where you analyse the traffic and advise what is going on. Or providethe data so that a mug user like me could use Wireshark or a similar program to attempt to analyse the data captured from the Packet sniffing process would be very useful to try and figure out what is going on. It could be as benign as someone stealing internet, or something more sinister.