Another systemd-resolved problem in 17.04

[Karl Auer]

On Thu, 2017-06-22 at 11:18 -0400, Tom H wrote:
> On Thu, Jun 22, 2017 at 10:06 AM, Karl Auer <kauer at biplane.com.au>
> wrote:
> > 
> > On Thu, 2017-06-22 at 09:13 -0400, Tom H wrote:
> > > 
> > > > 
> > > > 
> > > > So are you saying that the nameserver that's responding with
> > > > REFUSE
> > > > is 'out there' on the internet somewhere?
> > > It depends whether the "fe80..." address is you own (as I've
> > > assumed
> > > up to now) or not.
> > Link local addresses are by definition local to the link.
> Sure. But the fe80 of wlp4s0 is different from the one that resolved
> is using...

I don't understand your point. The responding link local address is, by
definition, reachable on the local link. It is not "somewhere out
there". It is possible that a link local address might leak and be used
as a destination address on a link other than it's own, but it is not
possible that a packet would reach such an address, or that it would
respond. The link local address that responded with a REFUSED status is
on his network, one way or another.

All that said, I realise there are more things between heaven and earth
than are dreamed of in my philosophy :-)

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: A52E F6B9 708B 51C4 85E6 1634 0571 ADF9 3C1C 6A3A
Old fingerprint: E00D 64ED 9C6A 8605 21E0 0ED0 EE64 2BEE CBCB C38B