Subject: Re: multiple network interfaces
To: None <firstname.lastname@example.org, email@example.com>
From: Douglas Egan <firstname.lastname@example.org>
Date: 03/22/2001 11:47:49
Sorry for my late reply, I appreciate your quick answer.
I needed to get something running quickly so I dropped back to one card, and
haven't tried this again. Next week I will have some more time to troubleshoot
I would agree that it should be a no-brainer, and I was expecting just what
you described, that I should be able to ping each interface from its own subnet.
With PNP ISA cards, (which I am using for one interface 3c509) I booted DOS
and configured the card for PNP. I was going to try to hardcode the address
and irq in the kernel conf file to see if that makes any difference.
>Can you provide the output of the following commands?
>dmesg | grep '^e.0:'
>Two interfaces should be a no brainer. Both interfaces should be
>pingable from other machines on their local subnet, etc.
>Unless you have an interrupt conflict between the boards or something.
>----- Original Message -----
>From: "Douglas Egan" <email@example.com>
>Sent: Wednesday, March 14, 2001 1:21 PM
>Subject: multiple network interfaces
>> I am trying to get 2 NIC cards running simultaneously on my V1.5 NetBSD.
>> card will run individually on either network, but when I try to get them
>> simultaneously I don't have any luck.
>> I have packet forwarding enabled in the kernel config file and sysctl says
>> net.inet.ip.forwarding is 1.
>> Initially I don't want a firewall functionality or router functionality,
>> want to access the machines resources (SAMBA and NFS) from two private
>> Only the first interface enabled ever responds to pings, even if I
>> disable it and make sure the second one is on.
>> At the very least I would think that each interface would respond to a
>> from its own network.
>> Do I have to configure firewall functionality in order to get both
>> to work? I will ultimately get there, but for now just want minimal dual
>> ex0 3Com905-PCI 192.168.193.133
>> ep0 3Com509-ISA 172.31.1.2
>> Any help appreciated.
>> Doug Egan