I should have more IPv6 hosts, atleast all devices on the local lan
should be getting one, but I'm only showing 10... :(
Can you add the router as well? (From the RA announcements?)
is no need to re-show the first 16 chars again, perhaps just render it
as *:a:b:c:d, or shortform *::23 when their is a vanity IPv6 address.
Actually you could identify tag the SLAAC address as SLAAC, since you would know the MAC address as well, and thus anything else is either manually assigned or may DHCPv6?
So, real-estate is a challenge, but I think it would still be better to show its IPv6 address over the IPv4 one. Since you know its a /64, there
On that topic, an subnet calculator (IPv6/4) would be soo handy. I'm finding I'm always going to vultr to use theirs and having something
local would nice :)
So, real-estate is a challenge, but I think it would still be better to show its IPv6 address over the IPv4 one. Since you know its a /64, there
Added a "Show IPv6 first" toggle on the map - stays IPv4 by default for everyone else, one click flips which family is the bold primary line for you.
Actually you could identify tag the SLAAC address as SLAAC, since you would know the MAC address as well, and thus anything else is either manually assigned or may DHCPv6?
Done, with one deliberate wording choice - I tagged it "EUI-64" rather than "SLAAC vs manual".
Built one, entirely client side, no data leaves the browser. Handles both families, shows network/host range/address count, and for IPv6 tells you how many /64s a bigger block breaks down into.
* When rendering the map, the IPv4 segement shows IPv4 addresses first, and the IPv6 segement shows the IPv6 addresses first.
What also would be better, is a toggle to have the IPv6 segment at the
top of the page (and that toggle to be remembered) - I'd find that very useful too. (Since I am now working in IPv6 first, and IPv4 is an after thought.)
It might be good (if you havent dont it), to do the same with IPv4, ie: a segment address as allocated by a DHCP server or manual, vs an IPv4 address assigned automatically when there is no DHCP server present
(cant remember what segment that is, 172.254.0.0/16?).
Agreed, and it's a better design than what shipped, not just a preference. Each segment will default to showing its own natural address family, and the toggle becomes "show me the other one" in both places at once - so it actually answers your two real questions (what's this IPv4 host's v6 address, what's this v6 host's v4 address) instead of just flipping everything uniformly regardless of which segment you're looking at.
Building that now.
Howdy,
Wow, this is getting better and better.
OK, some cosmetic thoughts:
* Can the IPv6 have an Internet and a Gateway and a LOCAL NETWORK?
* Can all the boxes be the same size? Maybe per IPv4/IPv6. By convention the IPv4 boxes would not be as wide as their IPv6 friends (because of
the smaller real-estate for the address).
* It looks like the IPv6 addresses are sorted by their IPv4 address, can they be sorted by the IPv6 address?
* Some IPv6 addresses are truncated (especially the SLAAC host) by 1 or two chars. The hover to reveal the complete address didnt always appear
to work (and shows "Also:..." when it does). It might be nicer to widen the box to fit those last 1-2 chars. (Instead of having to hover to
reveal it.)
* My lonely 10.1.3.246 appears back under 10.1.3.0/25 :(
* How could I discover (a route hop or two away) IPv6 addresses used by the hosts in other segments (eg: 172.31.20.0/24)?
* Might be useful to have a filter (on the network page and the main
page) to help find a specific host (by name, ip address, mac address, etc).
And as I think about this, I'm a huge fan of mikrotik router's and the penny just dropped that this would be a great container to run on it - since it has visability to all networks/VLANs,etc...
I've not run any containers on it, so not sure if I can bind it to see
the "hosts" network - and I could imagine that the consensus be that is not a good idea anyway, so I'll have to think this through a bit more. (Actually from what I've read so far, the consensus is that you shouldnt really run a container on the router anyway... but there are folks
running pihole, etc..)
A better approach might be to leverage SNMP, if/when you implement that. I'll eaglerly watch which way you go there...
One thing I do want to chase properly rather than guess at blind: 10.1.3.246 showing back under 10.1.3.0/25. Could you send me:
* Your current discovery CIDR settings, exactly as they appear in Settings - has anything changed there since we first sorted this out? (If the /25 isn't in that list anymore, that alone would explain it - the "by network" grouping recomputes fresh from whatever's currently configured, it doesn't remember anything from before.)
OK, might be user error, but my CIDR range is only showing
172.31.20.0/24, and I know I had other LAN segments there (3 of them
while I was playing).
It appears the "CIDR range to scan" is set by the value on the Dashboard "Lan Hosts" "Auto-Discover" input. I was using that to "re-scan" my networks (one at a time). When I put in the value, my nightly schedule range is overritten. :(
Is there a more correct way to rescan a range at a time?
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 16 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 13:26:49 |
| Calls: | 155 |
| Files: | 50,638 |
| D/L today: |
13 files (1,798K bytes) |
| Messages: | 348,381 |