On 09/12/2012 10:51 PM, Freddie Cash wrote:
On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel <jfvo...@gmail.com> wrote:
On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash <fjwc...@gmail.com> wrote:
Thanks for checking. I've used lagg(4) with igb, just not on 9.x.
You're right, it seems to be pointing to the igb(4) driver in 9.x
compared to < 9.0.
How do you determine that since it doesn't happen without lagg? I've no
reports of igb hanging otherwise and its being used extensively.
Well, I did say "seems to". :)
igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0
and 9-STABLE on those three boxes.
igb+lagg doesn't work for him on 9.0. Although, I don't recall if
non-LACP options were tried earlier in this thread, or if it's just
the LACP mode that's failing. If one mode works (say failover) and
LACP mode doesn't, that "seems to" point to lagg.
Sorry, forgot to mention it. I tried both failover and lacp: neither
worked. The switch is a Dell powerconnect 6248 with ports configured for
aggragation.
I first tried on a 9.1 prerelease, then on a 9.0 release to have
everything clean. In both ssh, both as server and as client, become
unresponsive and unkillable.
The problem might also lie within ssh/d, but I somehow doubt it.
I haven't tried other network services.
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
