<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 7, 2016 at 2:37 PM, DJ-Pfulio <span dir="ltr"><<a href="mailto:DJPfulio@jdpfu.com" target="_blank">DJPfulio@jdpfu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 06/07/2016 02:23 PM, Solomon Peachy wrote:<br>
>> > and $25 for an Intel PRO/1000 with ZERO driver hassles - they get my<br>
>> > extra $5 every time. Not all PRO/1000s are the same either. There were<br>
>> > some made in Mexico which would lock up if some specially crafted SIP<br>
>> > traffic was seen<br>
> It's not the location of manufacture, but rather due to there genuinely<br>
> being many major (and even more minor) variations of the Intel ethernet<br>
> ASICs over the years. Notably, the server-targeted PRO/1000 family was<br>
> quite different (and more expensive) than the client-targeted PRO/1000s.<br>
> The former supported more PHYs and fancier offload support which took a<br>
> few revisions to get right..<br>
<br>
</span>True. It was a design issue, NOT a manufacturing problem. Mexico just<br>
happened to be the locate of that specific run.<br>
<br>
And the outages begin again today. Had one earlier today. Comcast<br>
didn´t claim to know about it, so looks like something from the street<br>
to my house.<br>
<span class=""><br>
$ ping 8.8.8.8<br>
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.<br>
<br>
</span><span class="">--- 8.8.8.8 ping statistics ---<br>
</span>10 packets transmitted, 0 received, 100% packet loss, time 9071ms<br>
<div class="HOEnZb"><div class="h5"><br>
<br></div></div></blockquote><div><br></div><div>FWIW I had an "outage" recently with Comcast. I found that my IPv4 connectivity was broken and I could not get a DHCP response. My IPv6 connectivity did work however. I found that I was able to get IPv4 working again by changing my MAC address. It appeared that my MAC got placed in a block list. I believe this to be the case because I accidentally enabled DHCP Server on my Comcast facing port (whoops), which I've stopped now.</div><div><br></div><div>Probably unrelated to your issues but I figure its worth sharing for anyone that may experience a similar issue.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
_______________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">[<a href="mailto:stillwaxin@gmail.com" target="_blank">stillwaxin@gmail.com</a> ~]$ cat .signature<br>cat: .signature: No such file or directory<br>[<a href="mailto:stillwaxin@gmail.com" target="_blank">stillwaxin@gmail.com</a> ~]$<br></div>
</div></div>