IIRC, all ethernet cards have a register for the address, so
filtering that this packet is for this host is done in hardware.
Some cards have two address registers. I don't think there are any
that have 37 registers, so the NIC is in promiscuous mode and address
filtering is done is software. You may be finding the limits of the
software filtering. If this hypothesis is correct, reducing the
number of IP aliases or getting a faster CPU should help.
I read somewhere that a way to sometimes find packet sniffers on you
network is that they are slow to respond to pings because of the
address filtering load in promiscuous mode.
HTH,
Jeffrey
Quoting Christian Klippel
hi jeffrey,
Am Freitag, 8. Juni 2001 17:29 schrieb Jeffrey Taylor:
Does route -n hang? If not, you may have flaky DNS and route is waiting for it.
Jeffrey
will try next time. but i ping the adresses via their ip-numbers instead of their names. just in this moment it is so, that for example 195.80.222.121 is set up as eth0:35 inside the network (from another machine) i can ping it, but not from outside (from my home) but, for example, 195.80.222.171 (eth0:36) can be pinged from booth ......
web:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 195.80.222.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 195.80.222.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 195.80.222.254 0.0.0.0 UG 0 0 0 eth0
is what route shows actually.
part of ifconfig output :
........ eth0:35 Link encap:Ethernet HWaddr 00:E0:18:1E:81:48 inet addr:195.80.222.121 Bcast:195.80.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth0:36 Link encap:Ethernet HWaddr 00:E0:18:1E:81:48 inet addr:195.80.222.171 Bcast:195.80.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ........
this really makes me crazy .....
greets,
chris
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck