On Wed, 2003-02-05 at 11:56, Richard Kuhns wrote: > > The builtin ethernet card in the laptop is an AMD 79c970, if that makes > any difference.
Brian points out that there may be problems with that card... I'm not sure why that would only cause trouble when talking to the FreeBSD box, it's probably worth trying a different card if it's at all feasible. You could also use mii-tool to force the card to half-duplex. I believe that your Linksys "hub" does store and forward switching, but perhaps the card isn't *down* with that. > > > 2) When I use ssh from either RedHat machine, it always does a DNS > > > lookup on the machine name. > > > > Don't know on this one... It seems most likely that ssh is doing some > > additional work. Are you sure the lookup is for the name of the server > > you're connecting to? > > OK, I just tried running ethereal on the FreeBSD and monitored the dialup > line. The RedHat boxes are sending AAAA queries to the nameserver for the > host I'm connecting to, and of course getting a 'no such name' response. > So for some reason it's doing an IPv6 name lookup. Well, that's normal on systems that support IPv6, as Red Hat Linux does. I'm not even sure the resolver cares if the IPv6 stack is available. Perhaps the easiest solution to this problem is simply to run a local caching DNS server, with authority for the names you're using. > > Use telnet to connect to the server's ssh port and see if the machine > > does a DNS lookup when the name is in /etc/hosts. If so, then the > > problem is probably in glibc. If not, then the problem is that ssh is > > doing something that you (and I) don't understand. > > Good idea -- I should have thought of that myself:). I get the same > results using telnet, so apparently something in glibc is always trying to > do an IPv6 name lookup. I just did a little more playing around with > ethereal: with 'hosts: files dns' in nsswitch.conf, there is *always* an > attempt to do an AAAA query, which fails. If I change it to 'hosts: dns > files', there is first an AAAA query which files, and then an A query > which fails. Sounds like a bug to me. Can anyone else verify this? Should be intended behavior. The resolver library is trying to get an A and an AAAA record for the name. When it's set up "files dns", the resolver searched for an IPv6 address in /etc/hosts, and not finding one, it asks DNS. It does find the A record, so it doesn't ask DNS about that one. > > > 3) I've noticed that there are quite a few programs linked with the > > > kerberos libraries. I don't use kerberos now and don't expect to ever > > > use it. Is there such a thing as a RedHat distribution that doesn't > > > include kerberos? > > > > No. Do you think that ~1.5MiB of disk space is worth the effort to > > produce a distribution without it? > > It's not that I'm concerned about the disk space. It's just that I prefer > the 'Keep It Simple' philosophy wherever possible, and kerberos is a > rather complex piece of software that I'm not using yet can't get rid of > -- it's just another potential 'failure point'. I'm not losing any sleep > over it, though. It shouldn't be a failure point if you don't configure it... just an inert library. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
