Let me know if you use it and if it's useful to you =)
Re: My latest project - "TipOff"
By: MeaTLoTioN to All on Thu Jul 02 2026 11:52 pm
Howdy,
Let me know if you use it and if it's useful to you =)
Just had a play today - nice tool, well done.
Be keen to see where you take this - I think there could be a few great things added.
* I see from the mac address you can identify the vendor - be good to identify all VMs (from their mac)
* Might be good to be able to group stuff, ie: seperate the appliance
from the homelab, etc...
* Could be helpful to have some lan topology if you can get it. ie: I
dont use a /24 on the same wire - some devices I route to, so it could
be useful to find out which devices are acting as a router
* Wondering how you could do IP6?
* I see from the mac address you can identify the vendor - be good to identify all VMs (from their mac)
* Might be good to be able to group stuff, ie: seperate the appliance
from the homelab, etc...
* Could be helpful to have some lan topology if you can get it. ie: I
dont use a /24 on the same wire - some devices I route to, so it could
be useful to find out which devices are acting as a router
* Wondering how you could do IP6?
Do a `docker compose pull && docker compose up -d` and you'll have all of these =)
* Could be helpful to have some lan topology if you can get it. ie: I dont use a /24 on the same wire - some devices I route to, so it could be useful to find out which devices are acting as a routerDo a `docker compose pull && docker compose up -d` and you'll have all of these =)
MAC Address identify is a little better, can identify which hosts are VM's if the MAC address matches a known template.
The network topology is not 100% fot me. To give you an example, at
home, I use 10.1.3.0/25 for my homelab. Tipoff is running on 10.1.3.54.
Thus everything on 10.1.3.0/25 you'll get a MAC address and know its "local", if you havent figured that out from quizzing 10.1.3.54 network routing table.
10.1.3.192/28 is running inside an emulator off of 10.1.3.111 and you
may be able to work that out via the same way traceroute does. Those addresses wont have a MAC address (from 10.1.3.54) - but they are
grouped under 10.1.3.0/24 (even though I choose "network" from the
network map).
Simularly 10.1.3.240/29 is another network via my core router 10.1.3.1.
Interestingly, my wifi is 172.31.20.0/24 and on it I have my home assistant VM, it shows as "infrastructure" at the top of the network diagram, next to 172.31.20.1 - what makes it "infrastructure" and not a "device"?
It would be ideal if 10.1.3.1,172.31.20.1,10.1.3.246 were discovered as the same router.
MAC Address identify is a little better, can identify which hosts are V if the MAC address matches a known template.
How do I define a mac mask, so that all my proxmox and esx machines are discovered as a VM?
I've had a look at the issues you raised:
| Sysop: | smooth0401 |
|---|---|
| Location: | New Providence, NJ |
| Users: | 4 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 495332:18:39 |
| Calls: | 385 |
| Files: | 788 |
| D/L today: |
69 files (11,435K bytes) |
| Messages: | 59,931 |