LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   How do i configure guarddog so i can use SSH remotely and ping my box? (https://www.linuxquestions.org/questions/slackware-14/how-do-i-configure-guarddog-so-i-can-use-ssh-remotely-and-ping-my-box-465327/)

asilentmurmur 07-18-2006 06:54 PM
How do i configure guarddog so i can use SSH remotely and ping my box?
 
Hey everyone

Here is the deal. I am currently running Slack 10.2 with Guarddog as my firewall.I Have SSH set up on my system. I want to be able to connect via SSH remotely to my computer. When I tried to ping my home computer remotely, the ping request timed out on me!Also I was not able to SSH from remote to my Linux box. I suspect this is an issue with the firewall configuration. How do I go about configuring guarddog so that I can ping my linux box AND SSH to it from a remote location?

uselpa 07-19-2006 04:42 AM
How is your home PC connected to the internet? Is there an router which has a build-in firewall?

asilentmurmur 07-19-2006 05:19 AM
well my computer is connected to the internet via DSL. My desktop runs a cat5 cable to the router/modem that my ISP provided me with. I do not know if the actual router/modem has a built in firewall. I did port-forward port 22 and configure it for SSH in my router using the router configuration page.SSH works when i disable guarddog. But when guarddog is reenabled, no computer is able to ping nor SSH into my computer.

stitchman 07-19-2006 08:14 AM
I can't help you with guarddog, but i want to recommend that if your router supports it, forward a diffrent port for ssh. What i mean is, make it so when you remotely ssh in, you are aiming at a port other than 22, such as 422, or 8022, or any non-standard ssh port. Have the router then forward that traffic to port 22 on your computer. I say this because there are a lot of script kiddies out there with brute force password guessers, you will see all their attempts in /var/log/messages.

Also, since you are using a software firewall along with your hardware firewall (router) i assume you are the paranoid type (a good thing) so you will want to edit /etc/ssh/sshd_config and add something like this:
Code:
AllowGroups users
AllowUsers <your username>
DenyGroups root bin daemon apache (etc...)
DenyUsers root bin daemon apache (etc...)
These two precautions should make it harder for someone to randomly find your computer (with nmap looking for port 22 open on a set of IP addresses) and if they do guess your "secret" port for ssh they wont be able to try to login as root with a password guesser.

I hope i helped a bit, though i know nothing about guarddog.

uselpa 07-19-2006 10:58 AM
For Guardog, it works as follows:
- go to the "Protocol" tab
- in "Defined Network Zones" choose "Local"
- in the "Zone Properties" Part expand "Interactive Session"
- check the checkbox that is at the intersection of line "SSH - Remote Login Protocol" and column "Internet" (the checkmark must correspond to the one that is shown next to the label "protocol is permitted")
- finally, Apply these rules

What you did this way is that you said that the Local zone (i.e. your machine) serves SSH to clients in zone Internet.

asilentmurmur 08-03-2006 12:57 AM
Quote:
Originally Posted by stitchman
I can't help you with guarddog, but i want to recommend that if your router supports it, forward a diffrent port for ssh. What i mean is, make it so when you remotely ssh in, you are aiming at a port other than 22, such as 422, or 8022, or any non-standard ssh port. Have the router then forward that traffic to port 22 on your computer. I say this because there are a lot of script kiddies out there with brute force password guessers, you will see all their attempts in /var/log/messages.

Also, since you are using a software firewall along with your hardware firewall (router) i assume you are the paranoid type (a good thing) so you will want to edit /etc/ssh/sshd_config and add something like this:
Code:
AllowGroups users
AllowUsers <your username>
DenyGroups root bin daemon apache (etc...)
DenyUsers root bin daemon apache (etc...)
These two precautions should make it harder for someone to randomly find your computer (with nmap looking for port 22 open on a set of IP addresses) and if they do guess your "secret" port for ssh they wont be able to try to login as root with a password guesser.

I hope i helped a bit, though i know nothing about guarddog.

You said:
Quote:
can't help you with guarddog, but i want to recommend that if your router supports it, forward a diffrent port for ssh. What i mean is, make it so when you remotely ssh in, you are aiming at a port other than 22, such as 422, or 8022, or any non-standard ssh port. Have the router then forward that traffic to port 22 on your computer. I say this because there are a lot of script kiddies out there with brute force password guessers, you will see all their attempts in /var/log/messages.
How do i do that? my router has the standard SSH port forwarded for SSH and when i connect with an SSH client to this computer, i am using the standard port. i tried connecting with another port but it was to no avail. Could you explain to me step by step what i should do there? i am pretty much a n00b at life lol


All times are GMT -5. The time now is 08:00 PM.