[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: OpenBSD 2.4 Network Weirdnesses
John-Paul Pagano wrote:
>
> At 12:06 PM 3/8/99 -0800, Chris Cappuccio wrote:
> >On Mon, 8 Mar 1999, John-Paul Pagano wrote:
> >
> >
> >What kind of ethernet card?
>
> It's an Intel 82557 Fast Lan Controller.
>
> >The domain name/DNS isn't related to the networking ability of the box!
> >(Unless you are using windows ;0)
>
> True enough, which is why I'm totally frustrated by this.
>
> >Send me a copy of your /etc/hosts file
>
> 127.0.0.1 localhost
> 204.x.x.x fatcat fatcat.inven.com
> 204.x.x.x mayhem data data.rangersoftware.com
> 204.x.x.x laocoon laocoon.inven.com
> 10.0.0.1 booyaka-gw booyaka-gw.dmz.inven.com
> 10.0.0.2 laocoon-gw laocoon-gw.dmz.inven.com
> 10.0.0.10 tauhid tauhid.dmz.inven.com
>
> 204.x.x.x is the external network. The 10 network is functioning properly,
> although another problem I've discovered is that if I try to telnet to this
> host on the 10 network, I get:
>
> Trying 10.0.0.2...
> Connected to laocoon-gw.
> Escape character is '^]'.
>
> and it just hangs indefinitely. It seems like the thing is trying to
> resolve either it's own domain name, or the connecting machines. I say
> "its own" because you can see by the telnet output that the machine doesn't
> seem to know its domain name, in spite of the fact that it's clearly listed
> in /etc/hosts. Odd.
>
> --
> John-Paul Pagano
> Unix Systems Administrator
> Voice: (212) 208-0828
> Fax: (212) 825-1040
Hi!
First, I use the 2.4 CDrom distribution, also as a firewall and it is
working great.
(THANK U FOR THE _COOOOL_ STICKERS, Theo!)
the only errors i get from time to time are: 'Mar 9 01:57:56 burn /bsd:
xl0: transmission error: 82'
i use 2x 3c905B cards. what is this?
I encountered similar problems once on a linux system, which was solved
by exchanging the order of
the nameservers in /etc/resolv.conf. (this problem occured only with one
private and one official net!)
It seems also strange to me, that sometimes it ignored the 'order'
statement in /etc/host.conf on linux
or /etc/resolv.conf's lookup statement on openbsd.
the conjunction of nameservice and hosts-file works fine here since i
use 'lookup bind file' on openbsd
and 'order hosts bind' on linux. (note, ist vice-versa!)
The telnet failure is, a name-resolve error on the client. i had exactly
the same lately.
changing the above helped.
--
Best regards, Karl Pitrich.
-------------------------------------------------------------------------
Microsoft is prohibited from distributing this work in any form, in
whole or in part, across any medium. Licenses for distribution are
available to microsoft for $500. Posting without permission constitutes
an agreement to these terms. Please send notices of violation to
toast@enemy.org and postmaster@microsoft.com
-------------------------------------------------------------------------