[atlas] beta status page vs. ipv6 only network
- Previous message (by thread): [atlas] beta status page vs. ipv6 only network
- Next message (by thread): [atlas] beta status page vs. ipv6 only network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Fri Jan 12 11:02:02 CET 2018
On 2018-01-11 18:39, Bjoern Buerger wrote: > Hi, > > One of our probes has a warning "IPv4 Doesn't Work Properly" > on the beta Status Page, along with a "IPv4 doesn't work" > Tag on the main page. > > While this is technically correct, the cause is simple and > nothing is broken. We just removed IPv4 from that specific > network segment (because it's not needed anymore). > > Is it possible to somehow tag the probe as "single stack > on purpose" in the configuration page? > > Thanks in advance, > Bjørn Hello, This is an interesting corner case (for now :-) ) I'd think it's relatively difficult to automatically (i.e. system) tag probes as "intentionally single stack", as we don't really know if that's a misconfiguration (e.g. DHCP server is down) or intentional. We could probably system-tag your probe and others like it as no-ipv4. I'd also recommend user-tagging the probe as "IPv6-only" to make this explicit. Regards, Robert
- Previous message (by thread): [atlas] beta status page vs. ipv6 only network
- Next message (by thread): [atlas] beta status page vs. ipv6 only network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]