Firewalla assigning duplicate .lan addresses?
I've got two test devices on my LAN, test.a2.lan and test.a2p.lan. For a2:
$ host test.a2.lan
test.a2.lan has address 192.168.1.90
test.a2.lan has address 192.168.1.105
test.a2.lan has IPv6 address 2401:7000:dc48:7304:xxxx:xxxx:xxxx:1ef9
test.a2.lan has IPv6 address 2401:7000:dc48:7304:xxxx:xxxx:xxxx:f908
test.a2.lan has IPv6 address 2401:7000:dc48:7304:xxxx:xxxx:xxxx:177c
test.a2.lan has IPv6 address 2401:7000:dc48:7304:xxxx:xxxx:xxxx:42d3
For a2p:
$ host test.a2p.lan
test.a2p.lan has address 192.168.1.105
test.a2p.lan has IPv6 address 2401:7000:dc48:7304:xxxx:xxxx:xxxx:177c
test.a2p.lan has IPv6 address 2401:7000:dc48:7304:xxxx:xxxx:xxxx:f908
As far as I can tell, the Firewalla is assigning the a2p addresses to the a2 as well, with every other device on the LAN seeing the a2p addresses as part of the a2 addresses. The Firewalla app shows the correct single (IPv4) address for the a2 (.90) and a2p (.105), but anything using DHCP is seeing the a2p's address assigned to the a2.
Has anyone else seen something like this? It's such an unusual thing that before I start doing a lot of re-plumbing I wanted to check if this is a known issue.
-
They're both physical instances, two embedded devices with slightly different hardware revs, definitely different MAC addresses.
I thought about masking the IPv6 addresses but they're just test devices on an internal network so couldn't see any real threat from revealing them, but I'll mask a few of the octets just in case.
-
Oh, and I've edited the post to mask most of the interface ID, since I assumed it was coming from a DHCPv6 server and doesn't seem to correspond to the MAC address I figured out would be OK to leave it in. However the posts are now marked as "Pending approval", possibly because of the long strings of X's I used to mask the address.
Please sign in to leave a comment.
Comments
4 comments