Re: "CU didn't stop" error message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2 Jun 2003 10:31:39 -0500, Brian Lawrence wrote
> I appreciate your offer. Would the driver be suitable for a 
> production firewall server?

It is still labelled as experimental because the code has been changing a lot 
between releases. Now that the code is beginning to stabilise, I'll stop 
calling it experimental in one of the next few releases. But using it in a 
firewall setup is another thing. There are still code paths that are rarely 
executed, e.g. the multicast setup, which happens to be where your "CU didn't 
stop" messages come from (in eexpress.c). I'm not sure.

-- 
Regards,
Rask Ingemann Lambertsen

-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux