One of my servers has a lot of IP aliases on eth0 so I thought it would be easier to use iproute2 instead of ifconfig. I duly commented out modules=("ifconfig") in /etc/conf.d/net (since the comments indicate iproute2 is the default in that case). Upon reboot, the startup scripts showed the IP aliases being added and each said [ok] but they did not appear to be added at all. Did I do something wrong or is iproute2 not the right tool for the job? I switched back to ifconfig and the startup scripts work fine.

Also, each IP took a few seconds to add (this machine has 260 IPs!) - as you can imagine it took about 15 minutes to add all the IPs before the rest of the boot process could continue. Is there any way to speed this up? Maybe forego the "arping" check for every single IP added?

Final problem: I tried to force full-duplex on eth0 by using ethtool in the preup() function in /etc/conf.d/net. But now Im seeing errors like this on my console:

eth0: Transmit error, Tx status register 82.
Probably a duplex mismatch.  See Documentation/networking/vortex.txt
  Flags; bus-master 1, dirty 4225325(13) current 4225325(13)
  Transmit list 00000000 vs. f7c2da20.
  0: @f7c2d200  length 8000059a status 0001059a
  1: @f7c2d2a0  length 80000042 status 00010042
  2: @f7c2d340  length 800005ea status 000105ea
  3: @f7c2d3e0  length 800005ea status 000105ea
  4: @f7c2d480  length 800005ea status 000105ea
  5: @f7c2d520  length 80000245 status 00010245
  6: @f7c2d5c0  length 800005ea status 000105ea
  7: @f7c2d660  length 800005ea status 000105ea
  8: @f7c2d700  length 800005ea status 000105ea
  9: @f7c2d7a0  length 800005ea status 000105ea
  10: @f7c2d840  length 800005ea status 000105ea
  11: @f7c2d8e0  length 800005ea status 000105ea
  12: @f7c2d980  length 8000042a status 8001042a
  13: @f7c2da20  length 800005e2 status 000105e2
  14: @f7c2dac0  length 800005e2 status 000105e2
  15: @f7c2db60  length 8000059a status 0001059a


The switch this is plugged in to (HP ProCurve) indicates that the port is set to 100Mbit-FDx with flow control switched on, so why the errors? The NICs on this server are 3c980-C.



--
A
--
[EMAIL PROTECTED] mailing list

Reply via email to