<p dir="ltr">I agree. Script up a tool that checks for connection to the gateway. If it fails, stop network, unload module, load module, start network and retest conn to gateway. If that works, it proves absolutely nothing except the connection will restart.</p>
<div class="gmail_quote">On Sep 13, 2015 5:25 PM, "Michael Trausch" <<a href="mailto:mike@trausch.us">mike@trausch.us</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Check your available modules and use a chip which can be driven. Realtek chips are relatively safe as they use the same ones for a long long time.<br>
<br>
A diagnostic for you: does removal and reinsertion of module work? That'd be able to eliminate many aspects (but not all) of software causes. I don't believe it's possible to do a power cycle from software on the PCI-e bus, or if suggest that as an interim solution. If you bounce the chip as soon as malfunction is detected most tcp sessions will survive it.<br>
<br>
Sent from my iPhone<br>
<br>
> On Sep 13, 2015, at 5:02 PM, Neal Rhodes <<a href="mailto:neal@mnopltd.com">neal@mnopltd.com</a>> wrote:<br>
><br>
> Any recommendations for an inexpensive no-drama PCI x1 card that works out of the box with Centos 6?<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>