By the way, this is on a pfSense/Netgate device and I still have at least 2 support incidents available. I'd happily burn at least one of them to have someone remotely check this.
I'll be back on site within 2 hours from this post, I'll check the web by then for the proper procedure to open a case. -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia (from mobile device), integral.be/om > Le 26 mai 2016 à 13:03, Olivier Mascia <[email protected]> a écrit : > > LAN Interface (lan, igb0) > Status up > MAC Address 00:08:a2:09:58:96 > IPv4 Address 10.32.0.1 > Subnet mask IPv4 255.255.0.0 > IPv6 Link Local fe80::1:1%igb0 (???) > IPv6 Address 2a02:578:4d07::1 > Subnet mask IPv6 64 > MTU 1500 > Media 1000baseT <full-duplex> > > I do not understand where this fe80:1:1 comes from, it clearly isn't derived > from the MAC. > > Indeed workstations on the LAN capture fe80::1:1 for their default gateway > and even pinging that IP from a workstation doesn't work: > > ping6 fe80::1:1 > PING6(56=40+8+8 bytes) fe80::aa20:66ff:fe21:7c8e%en2 --> fe80::1:1 > ping6: sendmsg: No route to host > ping6: wrote fe80::1:1 16 chars, ret=-1 > ping6: sendmsg: No route to host > ping6: wrote fe80::1:1 16 chars, ret=-1 > > Not surprised. > The question is where could this fe80::1:1 come from? > So I could get rid of it and get there a proper link-local address? > > Reboot does not help. > Downloaded config file, there is no fe80::1:1 anywhere in there. > > -- > Meilleures salutations, Met vriendelijke groeten, Best Regards, > Olivier Mascia, integral.be/om > > > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
