Chuck Swiger wrote:
Typically, that sort of message indicates that the firewall rules are
preventing traffic from going out, or packets are getting stuck in a
queue until it fills up, or maybe even a bug somewhere in the
particular combination of kernel firewall options enabled, high
optimization or CPUTYPE settings, and your particular hardware,
depending on how lucky you are. :-)
Does the problem go away if you use a trivial "permit all" PF ruleset?
Does the problem go away if you use a trivial IPFW "permit all"
instead of PF?
Does the problem go away if you use a stock 5.4 release kernel?
The 3Com 3c905B-TX is an OK NIC, apparently the later C revision or
the 918/920's are pretty decent, but anyway--
...does the problem go away if you switch to another (known good) NIC?
System was ok with 5.3-RELEASE & custom kernel with ipfw. PF logs all
block rules and nothing gets to pflog on those dhclient errors. I try
those tips you gave, thanks. Stuck in a queue sounds most likely to be
the case.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
