ssh within home LAN issues

[Alex Dean]

On Apr 18, 2006, at 5:25 PM, Alan Dayley wrote:

> Dazed_75 said:
>>
> --[clip]--
>> Hence 3 questions for now:
>> 1 - How best to not have to use IPs for the ssh functions?
>
> I am interested in the answer to this one.  I solved it by going to  
> fixed
> IP addresses for my home computers.

That's what I did as well.  Static DHCP made this a lot easier.  The  
client machines still get their IPs via DHCP, but the DHCP server  
always gives the same IP to a given MAC address.  (Allowing you to  
see all your client machines and their IPs in a single place.)

IPCop has a nice local DNS (they call it 'edit hosts') setup, so you  
can give descriptive names to machines.  I used to have all the IPs  
memorized for my local machines, but since setting up IPCop I've  
really liked being able to access them by name instead.

alex

ps : If you have OSX machines on your network...
The domain name '.local' (ie : machine1.local, machine2.local) might  
give you problems.  I chose this initially for my local network, and  
I was unable to find any of my Linux boxes from my Powerbook.  I  
eventually figured out that Apple has a separate name-resolution  
system (Bonjour, multi-cast DNS) which uses '.local' by default.   
When I tried to access debian.local, OSX didn't even try to use  
normal DNS.  It just said the machine could not be found.  Changing  
my local addresses to use '.localdomain' worked around the conflict.   
You can also tell OSX to search DNS for '.local' addresses with the  
instructions here : http://docs.info.apple.com/article.html? 
artnum=107800