`<div dir="ltr"><div><div>well, we figured it out..<br><br></div>it was pretty silly actually.. It looks like for this machine, at this location, and without the network/routing/route disabled, it was picking up a *second* default route.. so some of the packets (seemingly acks and other TCP activity -- somewhat important!) were ending up at this other router which belongs to a peer organization and we're not making it all the way to the remote side under certain circumstances. Once that second default route was removed, everything was fixed. It never affected ping, and my existing ssh was working fine. I have no idea why this suddenly started causing a problem!<br><br></div>I'm glad it turned out to be something simple.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 18, 2014 at 1:21 PM, Dan McDonald <span dir="ltr"><<a href="mailto:danmcd@omniti.com" target="_blank">danmcd@omniti.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Dec 18, 2014, at 11:26 AM, Doug Hughes <<a href="mailto:doug@will.to">doug@will.to</a>> wrote:<br>
><br>
><br>
> Here's the simplest test... I start up ttcp -r on the server, it binds to port 5001, listening. I run snoop.. Then I try to connect to 5001 from another machine. I see the packets in snoop, but the accept call on the omniOS machine never returns. Something seems wonky in network land. Has anybody seen this? THe machine has been up for weeks without any problems.<br>
><br>
> OmniOS v11 r151012<br>
> Copyright 2014 OmniTI Computer Consulting, Inc. All rights reserved.<br>
> Use is subject to license terms.<br>
><br>
> Regular/plain Intel chipset:<br>
> e1000g0:<br>
> root@xyr-r:/root# dladm show-link e1000g0<br>
> LINK CLASS MTU STATE BRIDGE OVER<br>
> e1000g0 phys 1500 up -- --<br>
> root@xyr-r:/root# dladm show-phys e1000g0<br>
> LINK MEDIA STATE SPEED DUPLEX DEVICE<br>
> e1000g0 Ethernet up 1000 full e1000g0<br>
><br>
> e1000 prtdiag excerpt:<br>
> name='device-name' type=string items=1<br>
> value='82574L Gigabit Network Connection'<br>
<br>
</span>I can't recall if this chipset has problems or not. I want to say it might, BUT I'm not sure, so I won't point fingers.<br>
<span class=""><br>
> name='subsystem-name' type=string items=1<br>
> value='unknown subsystem'<br>
> Device Minor Nodes:<br>
> dev=(112,1)<br>
> dev_path=/pci@0,0/pci8086,1d14@1c,2/pci122e,10d3@0:e1000g0<br>
> Ideas?<br>
<br>
</span>If you've the disk space, please utter "savecore -L" while your machine is in this state. It might be nice to have the system state while things are failing.<br>
<br>
Do you see any complaints from e1000g in /var/adm/messages?<br>
<br>
It's like the NIC or the driver stopped receiving packets.<br>
<br>
One thing you could do is unplumb and replumb the interface. That may make the kernel reset the driver.<br>
<br>
ifconfig e1000g0 unplumb<br>
ifconfig e1000g0 plumb <addr/prefix> up<br>
<br>
If that doesn't work, you may also need to modunload the driver before replumbing.<br>
<br>
ifconfig e1000g0 unplumb<br>
modinfo | grep e1000g<br>
modunload -i <number from modinfo line><br>
ifconfig e1000g0 plumb ....<br>
<br>
If modunload complains, you will need to unplumb the v6 interface ("ifconfig e1000g0 inet6 unplumb") or maybe disable some other services temporarily.<br>
<span class="HOEnZb"><font color="#888888"><br>
Dan<br>
<br>
</font></span></blockquote></div></div>
`