On Sun, Sep 18, 2011 at 09:50:39PM -0700, Paul Allen Newell wrote:
> The phrase "enough of a pain to set up" is a red flag to me to make sure
> I am putting my effort into what I really need versus what might be nice
> (aka "gravy"). I appreciate the editorial !!!
Please see my post. It's much easier than you think.
> That being said, I'll google sshd_deamon to make sure I am understand
> what it would provided me
Actually, look at 'sshd_config'. (Actually, just *run* it.)
I do have one suggestion--after sshd_config has completed, *if* you're
tuneling ssh from the WAN side, edit the file /etc/sshd_config (EITHER
under /etc/ssh on the Linux box, or /etc on the CygWin environment) to make
the following changes:
1. Change "Port 22" to something different (e.g., "Port 2234"). Make
sure to change your firewall to reflect that change.
2. Add a line to the end of the file of the form:
AllowUsers mylogin
where "mylogin" is the name of your account you'll be using to get
into 'ssh'. This will prevent any other login from authenticating;
again, it restricts the scriptkiddies' playground.
> I did try getting the info from the router and it was there
> (192.168.2.100) but I couldn't ping it. I can ping myself at the address
> on XP/Cygwin.
Hmm...if you're on the same subnet, you should be able to ping it. Take a
look at the output of 'ipconfig /all' on the XP box--make sure the Default
Gateway, IP address, netmask, and DNS servers all look right.
It also sounds like you're using your router as your DHCP server, and the
implication is that it isn't your Fedora box. Go into the router and make
sure the DHCP range is something sensible (e.g., it may be set to something
like 192.168.2.1-192.168.2.254. That would be bad.)
Restrict it to something like 192.168.2.100-192.168.2.199. Then you can use
the rest of the subnet range for static assignments. It's always a good
idea to assign addresses according to a usage scheme; one I often use would
be, for your selected subnet:
192.168.2.1-192.168.2.9 : Network devices. (Router, switches, etc.)
192.168.2.10-192.168.2.99: Server, printers
192.168.2.100-192.168.2.199: DHCP range
192.168.2.200-192.168.2.254: Experimental, VPN assignments
For VPN schemes that assign IP addresses, on Class 'C' subnets I often
assign working down from 254, giving me known addresses for guest machines,
experimental hardware, etc. working up from 200.
Cheers,
--
Dave Ihnat
dihnat@xxxxxxxxxx
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
