Dear Andre, Yes, I can telnet and ssh on loopback. Boy, that debug setting on the telnetd sure dumps a lot of output on the telnet side (but is still silent on the screen where I started it).
- Wayne On Mon, Mar 03, 2003 at 10:48:15AM -0500, Andre Guibert de Bruet wrote: > > On Sun, 2 Mar 2003, Terry Lambert wrote: > > > Andre Guibert de Bruet wrote: > > > On Mon, 3 Mar 2003, Wayne Barnes wrote: > > > > Immediately after rebooting, I get this: > > > > > > > > [EMAIL PROTECTED]:/home/wayne>telnetd -debug > ^^^^^^^ > > > > telnetd: bind: Address already in use > > > > > > > > This doesn't happen on my other (working) system. > > > > Could this be a clue to my problem? > > > > > > Telnetd is telling you that something else is listening on port 23. This > > > is most probably inetd. Do a 'killall inetd' then try that command. > > > > That's not only going to stop inetd from sitting on the port, > > it will probably also make telnet into the box start working, > > if it's related to the TCP wrappers (if he had modified his > > hosts.allow with the advice from a previous poster, he would > > not be having this problem, if that happens, so rather than > > posting his problem over and over again, maybe he should read > > the responses, and at least tell us if they worked?). > > > > Otherwise, another common culprit is ipfw; if he has the > > firewall enabled, the default is to block everything. > > > > Given that he got a connection, and that it was subsequently > > closed, though, rather than not getting a connection at all, > > it's a safe bet that it's the TCP wrappers, not the ipfw, that > > is causing the trouble. > > > > In which case, he should take the advice on the hosts.allow > > file contents that he was given earlier, and it will fix his > > problem... > > Terry, > > Part of the original message said the following: > <quote> > I have installed 5.0 into a new Dell. I have not set up anything > special yet (no firewall, no natd, etc.). > <...> > Is there a new default connecton protection that I must turn off, or > something? [/etc/hosts.allow is the default setting, I see no answer > there.] > </quote> > > If I recall correctly, we don't ship GENERIC with any firewalling options > enabled, so like you said, this is not likely to be a firewalling issue. > > 5.0R's /etc/hosts.allow shipped with something like the following at the > top of the file: > # Start by allowing everything (this prevents the rest of the file > # from working, so remove it when you need protection). > # The rules here work on a "First match wins" basis. > ALL : ALL : allow > > If Wayne was trying to run 'telnetd -debug', would it not make sense for > him to kill inetd first (or at least reconfigure inetd.conf then hup it) > before running the daemon in debug mode at the command line? > > Wayne: Can you successfully login using telnet over the loopback > interface? > > Regards, > > > Andre Guibert de Bruet | Enterprise Software Consultant > > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- -- Wayne M Barnes, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message