Re: ssh within home LAN issues

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Dazed_75
Date:  
To: Main PLUG discussion list
Subject: Re: ssh within home LAN issues
Thanks Alex. I am not sure how this helps since I don't believe I can
put IPCop on the Linksys Router and Wireless AP that is my DHCP server
(and a DHCP client to my Linksys Cable Modem) especially since some of
the boxes I may want to ssh between are wired and some wireless.

>From what I can see this solution might work if I put a dedicated

linux box BETWEEN the cable modem and router/AP with 2 Ethernet
interfaces and IPCop but frankly that seems a bit excessive. I may
well be wrong about this as networking is not exactly a strong suit
for me and I only spent a short time on the IPCop web site, but please
tell how me if so. Learning is good. :)

On 4/19/06, Alex Dean <> wrote:
>
> 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
> ---------------------------------------------------
> PLUG-discuss mailing list -
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



--

Nothing is really work unless you would rather be doing something else.
- James M. Barrie
---------------------------------------------------
PLUG-discuss mailing list -
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss