> Hello, > > I am currently setting up one of our machines (Dell PowerEdge 350) > as our new firewall box. This machine is equipped with 2 dual NICs: > one Dual NIC Intel PRO/100+ as pci card and one dual on-board NIC > Intel 82559. > > When loading the modules, Bering gives the following output > (no network cables attached on startup): > > e100 - Using /boot/lib/modules/e100.o > Intel(R) PRO/100 Network Driver - version 2.1.24-k1 > Copyright (c) 2002 Intel Corporation > > e100: eth0: Intel(R) PRO/100+ Dual Port Server Adapter > Mem:0xdc0ff000 IRQ:7 Speed:0 Mbps Dx:N/A > > e100: eth1: Intel(R) PRO/100+ Dual Port Server Adapter > Mem:0xdc0fe000 IRQ:5 Speed:0 Mbps Dx:N/A > > PCI: Found IRQ 5 for device 00:0c.0 > PCI: Sharing IRQ 5 with 00:0d.0 > e100: eth2: Intel(R) 82559 Fas Ethernet LAN on Motherboard > Mem:0xfebfe000 IRQ:5 Speed:0 Mbps Dx:N/A > Hardware receive checksums enabled > cpu cycle saver enabled > > PCI: Found IRQ 5 for device 00:0d.0 > PCI: Sharing IRQ 5 with 00:0c.0 > e100: eth3: Intel(R) 82559 Fas Ethernet LAN on Motherboard > Mem:0xfebfd000 IRQ:5 Speed:0 Mbps Dx:N/A > Hardware receive checksums enabled > cpu cycle saver enabled > > After startup I plugged in a network cable and started pinging > a know IP address. At first I thought I had a problem with my > shorewall rules, because I didn't see any traffic (even with > tcpdump), although the TX counter of eth0 was increasing. > So to be sure I stopped shorewall, flushed the tables and set > the policies to ACCEPT. Still no success. But after waiting for > a while (more than one minute) I saw tcpdump reporting some > arp packets and my ping packets. At this time I had already > stopped the ping command! > > I think this is an IRQ sharing problem. I tried the same setup > with another machine and there it is working, but with other > IRQ assingments (Dell PE 1650, 1 Intel PRO/100+ dual NIC, 1 > Intel GB dual NIC). But this machine is not intented to be > our new firewall. > > One thing I don't understand is, that with Bering uClibc 2.0rc1 > (Linux v 2.4.20) I have this problem. But when I start the old > Linux installation which is still on the harddisk (SuSE Linux 7.3, > Kernel 2.4.10, e100 v1.6.22), the NICs and IRQs are assigned in > the same way, but here network traffic just works fine. > > Is this really an IRQ problem or is it driver related? > > The issue with the Dell PE 350 is, that the BIOS does not allow to > assign IRQs to PCI slots. There is only one PCI slot for an > external card available (i.e. the second dual NIC), so I > cannot change the PCI slots of the NICs. > > Any ideas? > > Thanks in advance and best regards, > > Stefan
It could be caused by a specific network module you are using. I have often found that i get different results from the standard kernel net drivers and the Donald Becker net drivers. Try to get the eepro100 (i think it is the module you'll need) from another source. D.Becker's series: http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/2.4.20/net/ Linux Kernel 2.4.20: http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/2.4.20/kernel/ drivers/net/ Good luck! Luis Correia Bering uClibc Team PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 Key Server: http://pgp.mit.edu ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
