Gerhard Sittig
This is usually referenced from the remote host back to you when you relay mail there. Is there smtp traffic in company with these events? You might want to log them for investigation.
It happens when I open a ssh connection to the web server. Then, the server tries to connect back to my workstations port 113. But I guess it's not wise just to open external connects to port 113 of all workstations I do ssh from? Also, another thing: ssh worked not until I permitted connects from the servers ssh port to my workstations. First, I just permitted traffic from my workstations' ssh port to the server (as does the SuSE firewall script), but then it won't connect. Is this normal behaviour? Thanks, Jochen -- *** Linux BBS: Die deutsche Website fuer Linux-News und -Infos *** http://www.linuxbbs.org/
Jochen Lillich wrote:
Gerhard Sittig
writes: This is usually referenced from the remote host back to you when you relay mail there. Is there smtp traffic in company with these events? You might want to log them for investigation.
It happens when I open a ssh connection to the web server. Then, the server tries to connect back to my workstations port 113.
Looks like an ident request.
But I guess it's not wise just to open external connects to port 113 of all workstations I do ssh from?
No, don´t open 113 at all.
Also, another thing: ssh worked not until I permitted connects from the servers ssh port to my workstations. First, I just permitted traffic from my workstations' ssh port to the server (as does the SuSE firewall script), but then it won't connect. Is this normal behaviour?
SSH connection from workstation to server: ------------------------------------------ Random Port on workstation side -> Port 22 on server side SSh connection from server to workstation: ------------------------------------------ Random Port on Server side -> Port 22 on workstation side hope that helps Uwe -- " I Drink and Smoke because I believe a Gentleman should have a Hobby." -Oscar Wilde WWW: http://www.connect-gmbh.de GC 98: wTSba5eLafarbaa86ftMSXPYwdbyibvbqa22$vtTF3f5Ged 5GiaWez2ccbJSecNdFjwof6kndsNiycSbXHbhaaacdeBY
"Uwe A. P. Würdinger" wrote:
Jochen Lillich wrote:
Gerhard Sittig
writes: This is usually referenced from the remote host back to you when you relay mail there. Is there smtp traffic in company with these events? You might want to log them for investigation.
It happens when I open a ssh connection to the web server. Then, the server tries to connect back to my workstations port 113.
Looks like an ident request.
But I guess it's not wise just to open external connects to port 113 of all workstations I do ssh from?
No, don´t open 113 at all.
i have to allow incoming connections on 113 to be able to access a proxy server. is that a major problem?
Also, another thing: ssh worked not until I permitted connects from the servers ssh port to my workstations. First, I just permitted traffic from my workstations' ssh port to the server (as does the SuSE firewall script), but then it won't connect. Is this normal behaviour?
SSH connection from workstation to server: ------------------------------------------ Random Port on workstation side -> Port 22 on server side
SSh connection from server to workstation: ------------------------------------------ Random Port on Server side -> Port 22 on workstation side
hope that helps
Uwe
thanks in advance, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
On Mon, Oct 18, 1999 at 10:37:38PM +0000, Chris Reeves wrote:
No, don´t open 113 at all.
i have to allow incoming connections on 113 to be able to access a proxy server. is that a major problem?
It's not a bug and not a feature. But you can turn off this service, 'cause it's neccessary. Regards, Daniele -- "Assassins do it from behind." *fortune -o output* finger pgp_gelitten@mupfel.infra.de | pgp -fka -> Daniele.Frijia@infra.de <- -> http://realcosmo.hat.gelitten.org <-
participants (4)
-
Chris Reeves
-
Daniele Frijia
-
Jochen Lillich
-
Uwe A. P. W�rdinger