I've got an interesting problem, that seems to exist in all the
2.2.x kernels I've used. We have a redhat 6.0 box, used as a squid
proxy server (2.2.STABLE4). The ethernet card has the
Digital DS21140 Tulip chipset. A dmesg is appended below.
The box is currently running 2.2.14, but this particular problem
has exisited under all the 2.2.x kernels. 2.0.x does not have the
issue. The problem is that the we lose aliased interfaces and
the default route, after manipulating the default route several
times a minute on a continual basis. Our networking config looks
something like this (ip addresses changed to protect the innocent) :
eth0 Link encap:Ethernet HWaddr 00:80:C8:43:04:5E
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:813370259 errors:0 dropped:1389 overruns:0 frame:0
TX packets:910910756 errors:182 dropped:0 overruns:0 carrier:182
collisions:0 txqueuelen:100
Interrupt:5 Base address:0xd000
eth0:1 Link encap:Ethernet HWaddr 00:80:C8:43:04:5E
inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:5 Base address:0xd000
eth0:2 Link encap:Ethernet HWaddr 00:80:C8:43:04:5E
inet addr:192.168.3.6 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:5 Base address:0xd000
eth0:3 Link encap:Ethernet HWaddr 00:80:C8:43:04:5E
inet addr:192.168.4.6 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:5 Base address:0xd000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:109948030 errors:0 dropped:0 overruns:0 frame:0
TX packets:109948030 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Each class C is advertised to a different upstream provider. We then
snmp poll the various interfaces on our router, and based on the
utilization of each link, we change our default route. This means that
we go out with a different source ip, and thus inbound traffic comes back
via the appropriate link. We find it an effective way of balancing a number
of upstream pipes. After several days of doing this, the box loses it's
default route, and all the aliased interfaces go away. Nothing found in
the logs. eth0 remains, and so does the network route for eth0. A simple
ifconfig and addition of the appropriate network routes and default route
puts the box back to normal for the next few days. As I said above, we
have boxes running 2.0.36, and they don't have this problem. Would appreciate
some advice.
Linux version 2.2.14 (root@jibbajabba) (gcc version egcs-2.91.66 19990314/Linux
(egcs-1.1.2 release)) #1 Mon Feb 28 16:07:32 WST 2000
Detected 400917823 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 399.77 BogoMIPS
Memory: 257884k/262080k available (948k kernel code, 412k reserved, 2788k data, 48k
init)
Dentry hash table entries: 32768 (order 6, 256k)
Buffer cache hash table entries: 262144 (order 8, 1024k)
Page cache hash table entries: 65536 (order 6, 256k)
CPU: Intel Pentium II (Deschutes) stepping 02
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xf0720
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 262144 bhash 65536)
Starting kswapd v 1.5
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
PIIX4: IDE controller on PCI bus 00 dev 21
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:pio, hdd:pio
keyboard: Too many NACKs -- noisy kbd cable?
keyboard: Too many NACKs -- noisy kbd cable?
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
scsi: ***** BusLogic SCSI Driver Version 2.1.15 of 17 August 1998 *****
scsi: Copyright 1995-1998 by Leonard N. Zubkoff <[EMAIL PROTECTED]>
scsi0: Configuring BusLogic Model BT-958 PCI Wide Ultra SCSI Host Adapter
scsi0: Firmware Version: 5.07B, I/O Address: 0xB800, IRQ Channel: 12/Level
scsi0: PCI Bus: 0, Device: 10, Address: 0xE2800000, Host Adapter SCSI ID: 7
scsi0: Parity Checking: Enabled, Extended Translation: Enabled
scsi0: Synchronous Negotiation: Fast, Wide Negotiation: Enabled
scsi0: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
scsi0: Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211
scsi0: Driver Queue Depth: 211, Host Adapter Queue Depth: 192
scsi0: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
scsi0: Error Recovery Strategy: Default, SCSI Bus Reset: Enabled
scsi0: SCSI Bus Termination: Both Enabled, SCAM: Disabled
scsi0: *** BusLogic BT-958 Initialized Successfully ***
scsi1: Configuring BusLogic Model BT-958 PCI Wide Ultra SCSI Host Adapter
scsi1: Firmware Version: 5.07B, I/O Address: 0xB400, IRQ Channel: 10/Level
scsi1: PCI Bus: 0, Device: 11, Address: 0xE2000000, Host Adapter SCSI ID: 7
scsi1: Parity Checking: Enabled, Extended Translation: Enabled
scsi1: Synchronous Negotiation: Fast, Wide Negotiation: Enabled
scsi1: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
scsi1: Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211
scsi1: Driver Queue Depth: 211, Host Adapter Queue Depth: 192
scsi1: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
scsi1: Error Recovery Strategy: Default, SCSI Bus Reset: Enabled
scsi1: SCSI Bus Termination: Both Enabled, SCAM: Disabled
scsi1: *** BusLogic BT-958 Initialized Successfully ***
scsi0 : BusLogic BT-958
scsi1 : BusLogic BT-958
scsi : 2 hosts.
Vendor: QUANTUM Model: VIKING II 9.1WSE Rev: 5520
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: QUANTUM Model: VIKING II 9.1WLS Rev: 5520
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi1, channel 0, id 0, lun 0
scsi0: Target 0: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset 15
scsi1: Target 0: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset 15
scsi : detected 2 SCSI disks total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 17836668 [8709 MB] [8.7 GB]
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 17836668 [8709 MB] [8.7 GB]
tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED]
eth0: Digital DS21140 Tulip rev 34 at 0xd000, 00:80:C8:43:04:5E, IRQ 5.
eth0: EEPROM default media type Autosense.
eth0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
eth0: MII transceiver #0 config 1000 status 782d advertising 01e1.
Partition check:
sda: sda1 sda2 sda3 sda4
sdb: sdb1
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 48k freed
scsi0: Tagged Queuing now active for Target 0
Adding Swap: 130748k swap-space (priority -1)
scsi1: Tagged Queuing now active for Target 0
Regards,
D
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
