Date: Tue, 21 Nov 1995 21:25:09 -0700 From: "Mark G.M. O'Lear" <Mark.Olear@Colorado.EDU> To: questions@freebsd.org Subject: Re: 951104-SNAP - Can't telnet in (Solved!) Message-ID: <199511220425.VAA16943@jack.colorado.edu> In-Reply-To: Your message of "Thu, 16 Nov 1995 23:03:03 EST."
next in thread | raw e-mail | index | archive | help
I have been having (and still am having) a very similar problem.
Unfortunately your solution only partially fixes the problem for me.
The situation:
Host A: FreeBSD 2.1.0-951026-SNAP with krb and des.
Host B: FreeBSD 2.1.0-951104-SNAP with krb and des.
Before any changes:
I could not connect Host A to/from Host B with telnet, ftp, finger
or rlogin no matter what scenario I tried. rup and ping worked.
I could connect from either Host A or B to any other non-FreeBSD
host using either scenerio. I could connect from any other
non-FreeBSD host to either Host A or B using either scenerio. Any
connection from/to localhost on either Host A or B would work as well.
After switching to 2.1.0-RELEASE ftpd, inetd, telnet and telnetd
on both machines (using both kerberos and non-kerberos versions
of telnet and telnetd on both Host A and B):
Scenerio 1:
subnet 1 PPP subnet 1 Ether subnet 1 Ether or FDDI ?
(Host A) <--> (PPP-server) <--> (Nameless router) <-->
subnet 2 Ether subnet 2
(Named router) <--> (Host B)
I could not connect Host A to/from Host B with telnet, ftp, finger
or rlogin from different subnets with a nameless router (no DNS
host name entry) between them. rup and ping worked fine. Connecting
Host A and B from/to any other non-FreeBSD machine still works.
Scenerio 2:
subnet 2 PPP subnet 2
(Host A) <--> (Host B)
I could connect Host A and B if they were both on the same
subnet and there was no nameless router between them. I know
this is an over simplification of the situation.
I can also use ftp and http from Host A and B to
ftp/www.freebsd.org. I checked with traceroute and there are no
nameless routers between me and ftp/www.freebsd.org.
It seems to me that there may be more than one problem
going on here. Unfortunately this is not the best test
case possible, but I am limited to my home computer and
work computer because they are the only FreeBSD boxes I
have access to.
Also if it is inetd, it seems to only have problems with some clients
and internally managed ports. Telnetting to daytime port and rup both
worked before and after. The following happen now in scenerio 1 when
using inetd built-ins:
1) chargen gives me 492 chars and hangs (TCP only, UDP keeps going)
2) echo doesn't echo at all (TCP only, UDP works)
3) discard won't discard after 16384 bytes (TCP only,
UDP keeps discarding or I never know about it).
4) daytime and time work (both TCP and UDP)
One more note, ftp only hangs after I type in my username.
telnet hangs before username.
Thanks for any suggestions,
Mark
Mark.Olear@Colorado.EDU
> From: Kenneth Merry <ken@ulc199.residence.gatech.edu>
> Subject: Re: 951104-SNAP - Can't telnet in (Solved!)
> To: jaykuri@interaccess.com (Jay Kuri)
> Date: Thu, 16 Nov 1995 23:03:03 -0500 (EST)
> Cc: maral@webnet.com.au, questions@FreeBSD.ORG
> In-Reply-To: <Pine.BSI.3.91.951116212200.9519A-100000@flowbee.interaccess.com> from "Jay Kuri" at Nov 16, 95 09:26:19 pm
>
> >
> > > > > generic info: 2.1.0-951104-SNAP, SMC Elite 16C Ultra, DES and Kerberos
> > > > > distributions installed.
> > > > > I don't think this is kerberos related, since it shows up with
> > > > > finger, talk, etc.
> > > > > Does anyone have any ideas on this?
> > > > This is just a hunch, but try adding a domain name to /etc/sysconfig
> > > Hmm..what'll that do? I'm not running NIS, so setting the NIS
> > > domain name won't help..and my hostname is already fully qualified in
> > > /etc/sysconfig and in /etc/hosts. (i.e. hostname.subdomain.domain.edu)
> >
> > When I first installed the SNAP, I was getting problems with the
> > telnets as well. I got a strange message about a function not having the
> > right parameters, or something (unfortunately I don't remember it) I
> > recompiled telnet and telnetd and they worked fine from then on. This
> > may be unrelated as I was installing over an old distribution, but just
> > thought I'd mention it just in case it's not.
> >
> > Also, I too am using the 951104-SNAP, a SMC-elite 16C and DES and Kerberos.
>
>
> Well, I figured out how to solve the problem...(but not exactly
> what caused it) I recompiled inetd, and things work just fine! I don't
> see what difference that could make, since it doesn't seem to use any
> libraries other than libc...go figure.
> Thanks for the idea, I'm up and running now...:)
>
>
> Ken
> --
> Kenneth Merry
> ken@ulc199.residence.gatech.edu
> Disclaimer: I don't speak for GTRI, GT, or Elvis.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511220425.VAA16943>