Re: Stretch net install on EeePC - unable to resolve mirror host address
On Fri, Feb 23, 2018 at 02:22:01PM +0100, Erwan David wrote:
> On Fri, Feb 23, 2018 at 01:12:41PM CET, Reco <recoverym4n@gmail.com> said:
> > Hi.
> >
> > On Fri, Feb 23, 2018 at 12:22:26PM +0100, Roger Price wrote:
> > > On Thu, 22 Feb 2018, Reco wrote:
> > >
> > > > > On the EeePC Ctl-Alt-F3 /dev/tty3:
> > > > > ~ # ip address
> > > > > 3: enp0s4: <BROADCAST,MULTICAST,UP,LOWER_UP> ...
> > > > > ...
> > > > > inet 10.218.0.100 scope global enp0s4
> > > > > inet6 fe80::22cf:30ff:fe10:43fd/64 scope link
> > > > >
> > > > > The "fe" at the beginning of the IPv6 address says that this is not capable
> > > > > of working with the public IPv6 network.
> > > >
> > > > There's one crucial detail that's missing here. I agree that fe80
> > > > designates link-local IPv6 (they don't put "scope link" there for
> > > > nothing), but what about routing?
> > > > I.e. I'm curious about the output of "ip -6 ro l".
> > >
> > > rprice@kananga:~$ ip -6 ro l
> > > fe80::/64 dev wlan0 proto kernel metric 256 pref medium
> >
> > Now *that* actually means it should be impossible for this host to
> > connect to 2001:41d0:202:100:213:32:5:7.
>
> No. In SLAAC the router often sends its linklocal address as
> gateway.
And this particular routing table does not have it.
What it does have is the usual link-local /64 route, which cannot be
used to send packets to 2001::/96.
But, looking at all this once more, I see a discrepancy - "ip a" shows
Unpredictable Network Name, yet "ip ro" shows conventional "wlan0".
Reco
Reply to: