*BSD News Article 43895


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!sun.lclark.edu!news.reed.edu!usenet.ee.pdx.edu!cs.uoregon.edu!reuter.cse.ogi.edu!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!news.sprintlink.net!matlock.mindspring.com!rsanders
From: rsanders@interbev.mindspring.com (Robert Sanders)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: FreeBSD 2.0-950412-SNAP and 3c509 problems
Date: 8 May 1995 17:49:52 GMT
Organization: MindSpring Enterprises, Inc.
Lines: 19
Message-ID: <3ollk0$1p9a@nntp4.mindspring.com>
References: <3ok7ck$874@nntp4.mindspring.com>
NNTP-Posting-Host: interbev2.mindspring.com

In article <3ok7ck$874@nntp4.mindspring.com>,
Robert Sanders <rsanders@interbev.mindspring.com> wrote:

>    ifconfig ep0 168.121.253.90 netmask 0xffffff00

Thanks to the people who responded.  That should have been:

    ifconfig ep0 168.121.253.90 netmask 0xffffff00 link2

Actually, I can't get it to *not* work now that I've configured it once
with the "link2" flag; I'll have to see what happens if I remove link2
from /etc/sysconfig.  Strange.

I and another new user are a bit worried about the "3c509 is buggy" caveat on
the release notes.  How buggy is it?  Is there ongoing work to debug it, or
should we just use a different adapter?

  -- Robert