Re: RE : Re: Kernel issues due to identical network cards
On Sat, Jan 05, 2008 at 01:11:41PM +0100, David MAGNY wrote:
> --- "Douglas A. Tutty" <dtutty@porchlight.ca> a ?crit
> > On Fri, Jan 04, 2008 at 11:06:31PM +0100, David
> > MAGNY wrote:
> > > Hello,
> > >
> > > I am upgrading a firewall from Sarge to Etch.
> > >
> > > On this machine, I have 3 network cards.
> > >
> > > 2 networks cards are identical. It is PCI network
> > > cards and it is SMC1233A-TX.
> > >
> > > On Sarge, everything worked well.
> > >
> > > The issue is that only one card of both is
> > available.
> >
> > What exactly does this line mean? Do you mean that
> > of the two identical
> > cards, only one is available?
>
> Yes, only one is available
> > so at least you know that the kernel is finding the
> > card.
> >
[snip dmesg that shows all three cards]
> > This suggests that eth0 is the intel card, while
> > eth1 and eth2 are the
> > two ADMtek comets.
>
> Yes you are right. But, I use ifrename (/etc/iftab) in
> order to be sure that a network interface has always
> the same name when I restart the server.
>
> if my /etc/iftab I mention that,
> ethO is one of ADMtek comet
> eth1 is the intel card
> eth2 is the other ADMtek card
>
> and in fact eth2 is not available.
>
>
What if you don't use iftab? If, as a test, you just go ahead and set
up all three cards? Does /sbin/ifconfig then show three cards
configured? If so, then dmesg and the kernel are just fine, the problem
is in ifrename. I've never needed ifrename so I don't know about it.
>
> > What does your /etc/network/interfaces look like?
> #eth0 is connected to Internet
> auto eth0
> iface eth0 inet static
> address X.X.X.X
> netmask X.X.X.X
> network X.X.X.X
> broadcast X.X.X.X
> gateway X.X.X.X
>
> #eth1 is connected to the private network
> auto eth1
> iface eth1 inet static
> address 192.168.0.254
> netmask 255.255.255.0
> network 192.168.0.0
> broadcast 192.168.0.255
>
> #eth2 is connected to the DMZ
> auto eth2
> iface eth2 inet static
> address 192.168.2.254
> netmask 255.255.255.0
> network 192.168.2.0
> broadcast 192.168.2.255
>
Reply to: