i’ve got a IPcop firewall at home with two SUSE boxes and one win box. from my win machine at work i can remotely ssh to the IPcop firewall through putty, no prob. just had to create a firewall rule. i’ve setup ultravnc to view my win box desktop remotely, no prob. i just had to setup a port forward firewall rule on the IPcop.
im now trying to log into one of my suse boxes through ssh. i created another firewall rule: port forward source port 12345 to the suse box’s ip, port 22. i get a connection time out. is there anything i need to setup on the suse box?
Yes, I meant using YaST to start ssh (now and on every boot) as Barry_Nichols points out.
But when you are able to use ssh from another system to this system that must be OK.
And @Barry_Nichols: no he need not to forward port 22 of the router to port 22 of his system, because he forwarded another (less obvious to the outside world) port (represented by 12345 in his first post) to port 22 on his system.
And at last yes, I support Akoellha advice to doublecheck and switch the SuSEfirewall2 off.
Hm, I thought port-translation (including NAT: from Internet to port 12345 on router, translate to port 22 on particular-system) is one of the things I have heard more often from. It keeps your internal ports standard. Can’t see problems with this principle. You can then even translate 12345 to 22 on system1 and 12346 to 22 on system2.
Can anyone tell us if this is not only a possible, but also often done, or am I talking nuts?
Maybe the description was confuding due to the fact, that I run openSUSE_Factory in VirtualBox on openSUSE 11.1 without mentioning it.
So it goes like this:
SSH via Port 22 from WWW => openSUSE 11.1 => Redirect of SuSEfirewall2 running on host openSUSE 11.1 from 22 (host) to 12345 (host) => Redirect from local port 12345 on host with VirtualBox (NAT) to => port 22 openSUSE_Factory (guest)
I also have another SSHD running on the host machine, which is on a non-standard port and “masked” by port-knocking.
(Yes, one of the ideas is to use the VM as a honeypot, “just for fun”.)
When I understand correctly what you explain, my understanding is that you are using the same mechanism (port forwarding with translation) but in your case the other way around. Not translating Internet to 12345 on the router into 22 on system1, but translating 22 on system into 12345 on virtualsystem. Which not only shows that it functions (but you have of course be aware of what port is what on what system), but also that it has more applications.
im trying to understand all this but im still learning. ok, just to get everything clear, the one suse box is my desktop (suse11) and the other suse box is my file server (also susse11). im having trouble logging into my file server from my office at work. so here’s what i’ve done so far: from my desktop, terminal>ssh file-server-ip -p 22. typed in the command
service sshd status
checking for service sshd running
just after my last post yesterday, i logged into my desktop from my file-server and vice versa. this morning, logged into my file-server from my desktop and issued the command:
and the firewall was stopped. i tried again to log into the file-server through the port but no luck. my winbox and desktop (SUSE) receive addresses assigned by ipcop and ive created static addresses for them. but with the file-server i had to statically assign the ip address because it did not respond to the DHCP server. would that have anything to do with it?
The -p 22 is not needed there as it is the standard ssh port. When you can log in that proofs that the sshd is running, no need to see if the daemon runs.
I am not sure I can quite follow this, but you need a static IP adress in any case, else you do not know where to forward to.
Can I say in short:
. inside your LAN you can SSH from desktop to file-server and vv.
. you have configured a fowarding rule on your router that should forward traffic from the internet to your router port 12345 to file-server port 22.
. when you use some Redmond box on the internet to SSH to 12345 on the router this fails (even with SuSEFirewall2 on file-server switched off).
Is that correct?
I see two possible culprits here:
your router, maybe it does not function as you think it does. I do not know the brand, maybe other can help you;
the Redmond stuff you use. You seem quite confident it can function as a SSH client. As I know nothing of Redmond systems, I am afraid I can not comment on tthis.
windows… microsoft is based in Redmond, Washington.
> thanks for the response. i’ve bridged my DSL router through to my IPcop
> firewall. all port forward and external access is configured on ipcop.
> what do you mean by Redmond stuff?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Sorry, it is one of those ways to give a name to what a lot of people dare not speak out loud. lol!
It is as email@example.com explained. I did not want to make my story more difficult to you and appologize.