Hey All,

I installed suse 9.2 and basically I hope to set it up ssh so I can access files when I travel and also for ssh tunneling.

I set it up on the linuxbox, start the ssh daemon and used putty in windows xp to connect to my linuxbox. I have internal network connected to a cable connection with a router and port forwarding. When I use the internal lan address 192.168.0.5 I can connect to my linux machine run commands and do all sorts of things... When I connect using my external IP it is much slower, I haven't tested file transfer, but sometimes I type something and I'll get a pause and then after a couple seconds the rest of the text will show up.

Is this normal or is something wrong? I'm almost positive I have Port Forwarding configured correctly. Does the machine have to be fairly fast to allow ssh? Right now its only experimental so I am using a 400mhz P2 with about 128mb of ram, could this be the issue?


Thanks for any and all suggestions in advance.

//Mark

It isn't the speed unless you are running an IDS. I forwared much more traffic on a much smaller box before. Your box is probably too small to run a proactive IDS though.


I'm not sure I understand your question. Are you saying when you connect to the linux box from your home internal lan it is fast. When you are on the road connecting to the external interface it is slow?


m

iamnotherbert-

I'm sorry, what does IDS stand for?

Let me clarify about how I am connecting. You are correct in your statements... I have two pcs on a internal lan connected with a netgear router, one running suse the other winxp. When I connect using the internal addressing scheme(192.168.0.xxx) of my lan it is as fast as could be, pretty much real time. However, when I go to www.whatismyip.com and use that IP from my windows xp box, to connect to my linux box it is slow..... Does that clarify?

//Mark

You are on the winxp machine say it's 192.168.1.2 connecting to the linux machine at 192.168.1.1. <--this works

You are on the winxp machine 192.168.1.2 connecting to x.x.x.x (public ip address of the netgear) then getting forwarded back to the linux box. <--- this is slow

If i'm correct then the problem is most likely the netgear box. You should configure it not to allow this because of ip spoofing attacks.

IDS = intrusion detection system. Like snort. These systems inspect packets and log to the filesystem network activity. They use alot more of the CPU.

Hope this helps.

m

If I disallow port forwarding due to ip spoofing attacks how am I able to get to the ssh server from the external IP?