On Mon, Jan 5, 2009 at 8:32 PM, Nathan Eisenberg <[email protected]> wrote: > Any thoughts on a next step in troubleshooting? >
As I suggested earlier in this thread: http://doc.pfsense.org/index.php/Policy_on_FreeBSD_issues "Most frequently these issues are driver bugs. We do not have any developers who work on drivers in FreeBSD, and cannot assist with such issues. In these cases, we suggest installing a stock FreeBSD 7.0 release on your hardware, replicating the problem, and reporting it to the appropriate FreeBSD list. This is the only way your problem will be resolved, and even at that will only be resolved in future releases. Alternatively, use different hardware." You may be able to get away with posting questions to freebsd-net using pfSense since it's close to the same as 7.0 release, with no kernel changes related to network drivers. My guess is you would be asked to try 7.1, or RELENG_7, or HEAD to see if the problems persist there. You won't be able to easily do that without running a stock FreeBSD. My guess is this is something specific to this new card that's been addressed with a newer driver, which probably isn't able to be reasonably added to a pfSense install. Hence you may be stuck for the time being. You can try 2.0, which is based on FreeBSD 7.1 and see if that makes any difference. Aside from that, I'm out of suggestions aside from going to the freebsd-net list and hoping the Intel employee who works on the em driver and posts there will offer some suggestions. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
