Figuring out a headless server's zeroconf addr

[Tim]

On Mon, 2014-07-21 at 10:55 -0400, Robert Moskowitz wrote:
> I have a headless system that I cannot connect to.  So I was thinking
> to put a direct connection to it and my notebook.  Both ethernets
> would use the zeroconf (169.254.0.0/16) addresses.  I could then use
> fping
>  
> fping -g 169.254.0.0/16
>  
> And SHOULD be able to get its address, and then SSH into the box.

I was under the impression that zeroconf did some rudimentary name
resolution, and you ought to be able to connect to hostname.local
(replacing "hostname" with the actual hostname).

It'd be a bit dopey if a zero-configuration scheme required you to
configure things...

> Any other thoughts?  I can't get to the box to recable it and reboot
> it (as that is the only way I can figure out for it to readdress eth0)
> until this evening.

Only that:  Are you on the same network?  169.254 connections can't be
expected to be reachable outside of their own net.


-- 
tim at localhost ~]$ uname -rsvp

Linux 3.14.8-200.fc20.i686 #1 SMP Mon Jun 16 22:36:56 UTC 2014 i686

All mail to my mailbox is automatically deleted, there is no point trying
to privately email me, I will only read messages posted to the public lists.

George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.