Re: [pfSense] Strange fe80::1:1 link-local address on LAN interface

[Chris Buechler]

On Thu, May 26, 2016 at 6:03 AM, Olivier Mascia  wrote:
> LAN Interface (lan, igb0)
> Status  up
> MAC Address 00:08:a2:09:58:96
> IPv4 Address10.32.0.1
> Subnet mask IPv4255.255.0.0
> IPv6 Link Local fe80::1:1%igb0  (???)
> IPv6 Address2a02:578:4d07::1
> Subnet mask IPv664
> MTU 1500
> Media   1000baseT 
>
> I do not understand where this fe80:1:1 comes from, it clearly isn't derived 
> from the MAC.
>

That's your link-local gateway IP, it exists on every interface that
obtains its IP via PD. It's common to use that as a gateway IP in that
case. It also provides an easy IP to use to hit the GUI.


> 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

You need an interface scope when pinging link local. For instance on a
Linux host whose connected NIC is wlan0, this is pinging the gateway
IP on a PD-configured interface.

$ ping6 fe80::1:1%wlan0
PING fe80::1:1%wlan0(fe80::1:1) 56 data bytes
64 bytes from fe80::1:1: icmp_seq=1 ttl=64 time=3.01 ms
64 bytes from fe80::1:1: icmp_seq=2 ttl=64 time=3.20 ms
64 bytes from fe80::1:1: icmp_seq=3 ttl=64 time=3.49 ms
^C
--- fe80::1:1%wlan0 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 3.010/3.235/3.493/0.209 ms
$ ip -6 neighbor
fe80::1:1 dev wlan0 lladdr 00:08:a2:09:3b:b4 router REACHABLE

Or on a Mac where en0 is the interface.

$ ping6 fe80::1:1%en0
PING6(56=40+8+8 bytes) fe80::426c:8fff:fe2c:d08%en0 --> fe80::1:1%en0
16 bytes from fe80::1:1%en0, icmp_seq=0 hlim=64 time=0.225 ms
16 bytes from fe80::1:1%en0, icmp_seq=1 hlim=64 time=0.252 ms
^C
--- fe80::1:1%en0 ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.225/0.238/0.252/0.014 ms

$ ndp -an
NeighborLinklayer Address  Netif ExpireSt Flgs Prbs

fe80::1:1%en0   0:8:a2:9:3b:b4   en0 7sR  R


> So I could get rid of it and get there a proper link-local address?
>

There's nothing improper about it, it's fine as-is.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Strange fe80::1:1 link-local address on LAN interface

[Walter Parker]

In IPv6, Link Local fe80::1:1  is like what IPv4 does when there isn't a
DHCP server (it auto assigns an address from 169.254.0.0/16 ). The IPv6 RFC
documents two ways to generate these link local address. The second method
generates addresses that are not dependent on the MAC address. Unlike the
IPv4 standard, the IPv6 standard requires that this address always exists,
even when a "real" (read globally routable)  IPv6 address exists.



Walter

On Thu, May 26, 2016 at 5:39 AM, Olivier Mascia  wrote:

> 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  a écrit :
> >
> > LAN Interface (lan, igb0)
> > Statusup
> > MAC Address00:08:a2:09:58:96
> > IPv4 Address10.32.0.1
> > Subnet mask IPv4255.255.0.0
> > IPv6 Link Localfe80::1:1%igb0  (???)
> > IPv6 Address2a02:578:4d07::1
> > Subnet mask IPv664
> > MTU1500
> > Media1000baseT 
> >
> > 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
>



-- 
The greatest dangers to liberty lurk in insidious encroachment by men of
zeal, well-meaning but without understanding.   -- Justice Louis D. Brandeis
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Strange fe80::1:1 link-local address on LAN interface

[Olivier Mascia]

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  a écrit :
> 
> LAN Interface (lan, igb0)
> Statusup
> MAC Address00:08:a2:09:58:96
> IPv4 Address10.32.0.1
> Subnet mask IPv4255.255.0.0
> IPv6 Link Localfe80::1:1%igb0  (???)
> IPv6 Address2a02:578:4d07::1
> Subnet mask IPv664
> MTU1500
> Media1000baseT 
> 
> 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

[pfSense] Strange fe80::1:1 link-local address on LAN interface

[Olivier Mascia]

LAN Interface (lan, igb0)
Status  up
MAC Address 00:08:a2:09:58:96
IPv4 Address10.32.0.1
Subnet mask IPv4255.255.0.0
IPv6 Link Local fe80::1:1%igb0  (???)
IPv6 Address2a02:578:4d07::1
Subnet mask IPv664
MTU 1500
Media   1000baseT 

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