Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!sgigate.sgi.com!uhog.mit.edu!news.mathworks.com!newsfeed.internetmci.com!news1.erols.com!newsmaster@erols.com From: Ken Bigelow <kbigelow@www.play-hookey.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Switching Ethernet Cards Date: Wed, 19 Jun 1996 22:46:15 -0700 Organization: Erols Internet Services Lines: 44 Message-ID: <31C8E5A7.6AEC@www.play-hookey.com> References: <roy-1906961616510001@206.53.164.230> NNTP-Posting-Host: kenjb05.play-hookey.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.02 (Win16; I) To: Roy Lovejoy <roy@adeptsolutions.com> Roy Lovejoy wrote: > > Hiya: > > I hope someone can help/point me in direction. > > I've been running fine with FreeBSD for a while now, but due to relocating > the machine, I needed to swap Ethernet cards (from TwistedPair to Thin). > > Previously, I had a 3Com card that was working perfectly, I yanked that > (power off of course), and replaced it with a Novell2000 clone. > > The boot sequence spews forth and says that it recognizes ed1, and dumps > the ethernet address & everything, but when it comes time to kick off the > network stuff it says "Network unreachable". > > I tested the card with the SW that comes with it under DOS, and everything > is OK. And FreeBSD seems to like it at inquiry time. > > Is there something SW/Driver/UNIXish that I have to switch inorder to use > the other card? > > PLEASE don't tell me that I have to re-install with the new card in place! > > Please email & post any helpful advice. > Was your old card identified as ed1? If so, use the -c option at the boot: prompt and verify that both the port and the IRQ for this card are correctly set. With no device name change, that should get you up and running. If your 3com card had a different device name and the new one has to remain as ed1 (would ed0 do just as well?), you'll have to edit the Netconfig section of your /etc/sysconfig file. In this section, you'll find a few lines designating your inet configuration. The first of these lines is network_interfaces="------" and the rest are individual specs for the devices named. You'll need to correct the device names in this group to reflect your new hardware. When you reboot, the corrected /etc/sysconfig file should solve your problem. Ken