Research
Skip Research Menus
Research MenuSecurity Enhanced Linux What's New Frequently Asked Questions Background Documents License Download Participating Mail List Archives Remaining Work Contributors Related Work Press Releases Information Assurance Research NIARL In-house Research Areas Mathematical Sciences Program Sabbaticals Computer & Information Sciences Research Technology Transfer Advanced Computing Advanced Mathematics Communications & Networking Information Processing Microelectronics Other Technologies Technology Fact Sheets Publications Related Links |
SELinux Mailing ListRE: ftp long time connection
From: Walker, Jason <Jason.Walker_at_csoconline.com>
Date: Wed, 20 Feb 2002 09:00:42 -0600
What they're talking about is the reverse DNS lookup, where the SERVER does a reverse lookup on the address of the CLIENT to see who's trying to connect, for logging and authentication purposes. If the Server doesn't know the name associated with the Client IP address, it will take some extra time before the server gives up and simply logs the client IP address instead of hostname. Make sure that the client system is listed in DNS, that the server is using the appropriate DNS server, or that the server has a HOSTS file listing the client. From the server, try doing an nslookup against the client IP address and see if it correctly returns the client name.
Jason Walker
-----Original Message-----
Flood Randy Capt AFCA/TCAA(randy.flood@scott.af.mil)@Tue, Feb 19, 2002 at
01:55:17PM -0600:
True, DNS errors will do that, as others here have pointed out. The original query, however, also mentioned that accessing the host directly by its IP was attempted with the same results. So while there may be some DNS-related delays as well, it cannot be a complete explanation. I also doubt SE Linux is the cause here either since it's a fairly generic kind of problem. I'd try attempting other protocols such as SSH, telnet (if enabled), SMTP and probably SCP too. To both hostname and IP address. See if it is affecting all protocols or just one or two, also try telnetting to the machine on port 21 and see exactly what point at which it slows to a crawl or breaks. Chances are the cause (and shortly thereafter, the solution) will leap out during this process.
Regards,
-- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.Received on Wed 20 Feb 2002 - 10:06:27 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |