Re: ssh again
On Tuesday, June 14, 2016 at 5:00:09 PM UTC-5, Dan Purgert wrote:
> Lisi Reisz wrote:
> > On Tuesday 14 June 2016 18:08:45 Brian wrote:
> >> With avahi-daemon installed on both machines
> >>
> >> ssh hostname.local
> >>
> >> should just work. No messing with config files or anything like that.
> >>
> >> /etc/hosts is fine if you are more comfortable with it but an IP address
> >> changing can make it a pain on the local LAN.
> >
> > Works a dream!! Thank you, Brian. That was a remarkably easy lesson! I
> > might set a hosts file up as I was shown by emetib. It doesn't hurt
> > to know both, and I might some time want to ssh into a machine that
> > hasn't got avahi-daemon installed.
> >
> > But I can see that changing IPs around could be a pain - I have several
> > machines that have two network cards for one reason or another, and I
> > have assigned different IPs to different cards in the router.
>
> This is a little more "involved" than /etc/hosts or ahavi-daemon, but
> you might consider isc-dhcp-server and bind9 on a box you designate as
> "your server" (I have it on a spare desktop sitting in the corner).
>
> That way,
>
> - you don't have to mess with /etc/hosts as things change (e.g. got a
> new computer)
> - you don't have to worry about "oh, that one doesn't have
> ahavi-daemon"
> - you can use hostnames with networked device, including those things
> that may not have hostfiles or a decent bonjour client (phones,
> tablets, TVs, etc.)
> - Other stuff I'm forgetting :)
> - When you replace your router (or get a forced 'upgrade' from your
> ISP), you don't have to deal with "fixing things" beyond the router
> itself.
>
> --
> |_|O|_| Registered Linux user #585947
> |_|_|O| Github: https://github.com/dpurgert
> |O|O|O|
dan has a good point about having your own nameserver. yet with only three computers in your home network it's not necessarily needed.
wait i did that before.
they are easy to set up and if you do have a POS sitting around getting dusty then it's something to play with. you could do an ntp-server on it also for your private network.
or just use a little used machine that is already on the network, or the most powerful one, it's up to you.
both are easy to set up and you don't need to open up ports on your firewall since they are getting response packets. and it helps with the knowledge curve when you start to play with the dhcp and/or static addresses. maybe plug a wireless card into a pci slot and make your own wireless network.
take care
em
Reply to: