Of course FreeBSD supports more than one NIC :

gw# ifconfig -a
ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
        ether 52:54:4c:1b:90:1b 
ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 212.198.30.16 netmask 0xffffff00 broadcast 212.198.30.255
        ether 00:40:05:61:20:3e 
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000 
gw# 

To use more than one NIC, you've two things to do :
1/ enable the NIC in your kernel, that is most likely recompiling your
kernel, as it is explained on :
<http://www.freebsd.org/handbook/kernelconfig-building.html>
2/ enable both NICs in the /etc/rc.conf file where wou will write
something like :
network_interfaces="ed0 ed1 lo0"
ifconfig_ed0="inet 192.168.1.3  netmask 255.255.255.0"
ifconfig_ed1="DHCP"
(my second board uses DHCP, but you may set a fixed IP address)

        TfH

PS : you should also read
<http://www.freebsd.org/handbook/advanced-networking.html>

"Brian D. Moffet" wrote:
> 
> Of course some one knows this, but does FreeBSD support 2 NICS?
> I have a 3com 3c905 and a 3com 3c509 in my box, but no matter how I adjust the
> configuration file, I cannot get the 509 to be recognized.  I could put
> the Ne2000 clone in there instead, but the 509 is a better card.
> 
> Also, does the sio driver support PCI sio boards?  The 3com / US Robotics
> 56K faxmodem is an sio card with a modem on the other side, so that the
> computer should be able to talk to it as a 16550.  Though the IO address may
> be a bit strange (in the 0x4000 or 0xa000 range).  I guess this boils down
> to 2 questions, IO space as well as PCI interrupts.
> 
> And as soon as I find out more information, I plan on modifying pciconf
> to be able to parse more of the PCI BIOS information instead of just
> the vendor and card IDs, unless someone has already done so.  Where should
> I send the changes?
> 
> Thanks
> Brian Moffet
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to