I'm stunned today to open my app and have the Eero crap app displaying IPV6 addresses in bridge configuration which isn't using IPV6 and never has.   I've never had this problem in many years using the app.  As usual, Eero regressing features regularly.

Ok, I've noticed this too after recent EERO updates.  My network is in bridge mode and I have a pfSense firewall providing DHCP services.  I can assure you ipV6 is disabled and the DHCP server only is serving ipV4 addresses.  All of my client devices on the EERo used to have ipv4 addresses and after one of the most recent upgrades, everything only shows a ipv6 address.  This is not a bug in my firewall, dhcp server, this is plain and simple a bug in eero.   if the eero can discern the chip supplier, Mac address, and ipv6 address (which it's likely getting link-local since ipv6 is explicitly turned off on my network and devices.  In fact, some of my devices like say my garage door openers don't even support ipv6, ( I called them) so there is no way.   Eero needs to fix this bug. 

-russ

Further to the topic, all 80 plus of my devices were happily displaying ipv4 devices, eero upgraded and now they don't. I'm quite sure I didn't go re-configure or touch 80+ devices and the firewall in my network has been online without an upgrade for well over 100 days and this problem showed up in the last 30-45 days.. 

VersionKernel PTIUptime

VersionKernel PTIUptime

I too see IPV6 addresses where I should see IPV4 addresses. I believe what eero is displaying are the ‘link-local’ addresses and, in my LAN, are irrelevant. Link-local addresses are generated by the devices and not your DHCP server. eero should not be reporting these addresses as they are not used in a network that is not configured for IPV6. A link-local address has a prefix of FE80: If that is what you are seeing, "In the Internet Protocol Version 6 (IPv6), the address block fe80::/10 has been reserved for link-local unicast addressing" eero needs to be fixed to display the IPV4 address when IPV6 is not enabled. 

IPv6 has site-local address that are derived from MAC addresses and will be unique.

IPv6 also doesnt have any problem of private/public IPs as with IPv4.

Finally, even for IPv4, your local (possibly private) IPs, accessible from inside the LAN will always be unique. They have to be, so that the router can send packets to the correct computer/device.

MyCCPay Log In

I’m also very annoyed about the “upgrade” that removed IPv4 addresses. My network has to be in Bridged mode because my DSL modem doesn’t support non-bridged mode.

I can also convert that hardwired devices don’t show in the eero app. There is, however, a workaround: just reboot the device and it will show up. 

I'd like to add my name to the list of customers irritated by this issue. To say that eero can't access router info to know IPv4 addresses sounds like a cop-out. Since eero is handling the traffic, it has access to IPv4 addresses (we know this since the software used to work properly even in bridge mode).  There are many customers for whom the LAN management MUST be done on the router.  In this configuration the router handles the LAN while the eero does what it does best: handling the wifi traffic.  We'd still like to have access to the wifi routing info!  

I'll add that the loss of correct IPv4 reporting seems to coincide with all network settings becoming greyed out when in bridge mode.  This is an unnecessary dumbing down of the app (which was already frustrating due to lack of direct access to settings).  The inability to manage wifi settings anytime the eeros are disconnected from the WAN (even is bridge mode) is unnecessary and incredibly annoying.  The eeros should work as long as there is a LAN DHCP server up and running (even if it is 3rd party router).

I agree. This is a bug and the explanation doesn't suffice. If eero really needs to collect buckets of user data only available in unbridged mode, then price the product according to configuration - but don't short-change the folks who opt out of bridge mode for whatever reason.  I will not be nudged into submission.

same issue guys, bridge mode, use firewall to offer v4 address only, app is showing node with ipv6 addresses making it hard to see which device is connected to which AP

I am not in bridge mode, I do not have IPv6 enabled and I have several devices now displaying the IPv6 address instead of the IPv4 address. I previously used bridge mode, but recently replaced an eero Pro with an eero Pro 6 set up as the gateway behind my dsl modem, the dsl modem is operating in bridge mode. I would also like to mention that when my eero was in bridge mode the IPv4 addresses were displayed in the app 

I am not in bridge mode. (Automatic)
I do not have IPV6 enabled.

I am seeing wifi devices with only IPv6 addresses.  However, my Firewalla is seeing them with IPv4 addresses, so I have a workaround.

But I'd still like the iOS Eero app to be giving me correct information