*BSD News Article 95992


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!news.bri.connect.com.au!corolla.OntheNet.com.au!not-for-mail
From: Tony Griffiths <tonyg@OntheNet.com.au>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: DEC 21140 doesn't connect to HUP
Date: Fri, 23 May 1997 18:43:43 +1000
Organization: On the Net (ISP on the Gold Coast, Australia)
Lines: 39
Message-ID: <338558BF.5E0@OntheNet.com.au>
References: <3382C782.41C67EA6@iaehv.nl>
Reply-To: tonyg@OntheNet.com.au
NNTP-Posting-Host: swanee.nt.com.au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0 (WinNT; I)
To: Geert-Jan Plattel <plattel@iaehv.nl>
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:41487

Geert-Jan Plattel wrote:
> 
> Dear everybody,
> 
> I'm trying to install a DEC 21140 100TX card in my computer.
> When probing the device the 100 Mbps led goes off, and the
> connect-to-hup-LED is lit. But the HUP doesn't think so. The hup works
> properly with NT systems...

See my previous post/email re "-link ?" ifconfig switch.

> 
> I think other people have had this problem before.
> - A driver problem?
> 
> - Does my ifconfig have an error? Here a look at my sysconfig:

Yes!

> 
>   network_interfaces="ed0 lo0 de0"
>   ifconfig_ed0="inet 100.0.0.202  netmask 255.255.0.0"
>   ifconfig_lo0="inet 127.0.0.1"
>   ifconfig_de0="inet 100.0.1.0    netmask 255.255.0.0"

You have the same 'network' on both the ed0 _AND_ the de0 interfaces. 
basically your netmask of 255.255.0.0 specifies a host address range of-

	100.0.0.0 -> 100.0.255.255  [64k addresses]

thus you have addresses in the same subnet on two different interfaces. 
I don't think that arp is going to work correctly here!

I suspect that you really want to sub-network the larger 100.0/16 block
into smaller blocks (eg. a 100.0.0/24 subnet and a 100.0.1/24 subnet). 
If this is so, the netmasks should be 255.255.255.0 which will allow 254
hosts [256 - 2] on each LAN segment.

Tony