Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
Daniel Eischen deisc...@freebsd.org wrote: My rc.conf is something like this: # # For now, force ath0 to use the same MAC address as xl0. # This works around a bug where lagg is unable to set the # MAC address of the underlying wlan0 interface. # ifconfig_ath0=ether 01:02:03:04:05:06 wlans_ath0=wlan0 ifconfig_wlan0=ssid SSID_FOO_NAME WPA I hope the above isn't literally what you're using for your MAC address. The first octet in particular, because it has LSB set to 1, will be treated as a multicast address, and many routers and switches will not believe it when it's given as an ARP reply, or as a source address for traffic. I'm hoping it's just an example you substituted so as not to reveal your actual MAC. When making up MAC addresses, keep the LSB of the first octet at zero (required) and set the next bit to 1 (optional, but a good practice). So first octet should be 02, 06, 8a, 9e, etc... any even number, preferably multiple of four, plus two. ifconfig_xl0=up closed_interfaces=lagg0 ifconfig_lagg0=laggproto failover laggport xl0 laggport wlan0 ifconfig_lagg0_alias0=inet 10.0.0.4 netmask 0xff00 I use aliasX to add the address and netmask. -- DE -- David DeSimone == Network Admin == f...@verio.net I don't like spinach, and I'm glad I don't, because if I liked it I'd eat it, and I just hate it. -- Clarence Darrow This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. Verio Inc. makes no warranty that this email is error or virus free. Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Tue, 18 Sep 2012, David DeSimone wrote: Daniel Eischen deisc...@freebsd.org wrote: My rc.conf is something like this: # # For now, force ath0 to use the same MAC address as xl0. # This works around a bug where lagg is unable to set the # MAC address of the underlying wlan0 interface. # ifconfig_ath0=ether 01:02:03:04:05:06 wlans_ath0=wlan0 ifconfig_wlan0=ssid SSID_FOO_NAME WPA I hope the above isn't literally what you're using for your MAC address. No, of course not :-) I thought it was obvious I elided my actual MAC address. -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On 11/09/2012 22:03, Giulio Ferro wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. For what is worth its working fine for me on 8.3-RELEASE using failover. ifconfig_igb0=up ifconfig_igb1=up cloned_interfaces=lagg0 lagg0.53 lagg0.52 lagg0.66 ifconfig_lagg0=laggproto failover laggport igb0 laggport igb1 85.233.xxx.xxx/23 ifconfig_lagg0_53=inet 192.168.xxx.226/24 ifconfig_lagg0_52=inet 192.168.xxx.254/24 ifconfig_lagg0_66=inet 192.168.xxx.250/24 ipv4_addrs_lagg0_52=192.168.xxx.254/24 192.168.0.70/24 lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=401bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO ether 00:25:90:39:64:76 inet 85.233.xx.xx netmask 0xfe00 broadcast 85.233.xx.255 media: Ethernet autoselect status: active laggproto failover laggport: igb1 flags=0 laggport: igb0 flags=5MASTER,ACTIVE Vince ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On 09/11/2012 11:34 PM, Freddie Cash wrote: On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org mailto:au...@zirakzigil.org wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0=laggproto ... ifconfig_lagg0_alias0=inet 192... I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. Nope, doesn't work. It always hangs at boot and cannot be killed (freebsd 9 RELEASE) I still think the problem is with lagg and / or igb. Someone should look into it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro au...@zirakzigil.org wrote: On 09/11/2012 11:34 PM, Freddie Cash wrote: On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org mailto:au...@zirakzigil.org wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0=laggproto ... ifconfig_lagg0_alias0=inet 192... I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. Nope, doesn't work. It always hangs at boot and cannot be killed (freebsd 9 RELEASE) I still think the problem is with lagg and / or igb. Someone should look into it. 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. -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash fjwc...@gmail.com wrote: On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro au...@zirakzigil.org wrote: On 09/11/2012 11:34 PM, Freddie Cash wrote: On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org mailto:au...@zirakzigil.org wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0=laggproto ... ifconfig_lagg0_alias0=inet 192... I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. Nope, doesn't work. It always hangs at boot and cannot be killed (freebsd 9 RELEASE) I still think the problem is with lagg and / or igb. Someone should look into it. 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. Jack -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
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. I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to test this with as well. -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Wed, Sep 12, 2012 at 1:51 PM, Freddie Cash fjwc...@gmail.com 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. I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to test this with as well. I wouldn't use 9.0, go with 9.1 RC or whatever has the latest igb code, if you see the issue there I can see about getting some time to look into it here. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
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. I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to test this with as well. I wouldn't use 9.0, go with 9.1 RC or whatever has the latest igb code, if you see the issue there I can see about getting some time to look into it here. Jack We're running igb + lagg on two interfaces here at Yahoo without issues like this. We're using LACP exclusively with Cisco switches. If you're seeing failover issues, I wonder if its the switch you're using as opposed to the host and ethernet card? Just a shot in the dark here. Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. This installation is a zfs root, but I don't think this has anything to do with this. Yes, I think that the maintainer of igb and/or lagg driver should absolutely look into this... On 09/07/2012 12:01 PM, Simon Dick wrote: We've had similar problems with lagg at work, each lagg is made up of one igb and one em port, sometimes for no apparent reason they seem to stop passing through traffic. The easiest way we've found to get it working again is ifconfig down and up on one of the physical interfaces. This is on 8.1 On 3 September 2012 19:25, Giulio Ferro au...@zirakzigil.org wrote: No idea anybody why this bug happens? Patches? On 08/29/2012 10:22 PM, Giulio Ferro wrote: On 08/28/2012 11:12 AM, Damien Fleuriot wrote: Hi Giulio, Just to clear things up: igb0: 192.168.9.60/24 lagg0: 192.168.12.21/24 Yes. Actually I notice now that the lagg0 address is different from what I wrote below in my rc.conf (192.168.12.7). I've just made many test with different configuration, but no matter, it just doesn't work... What's the IP of the host you're trying ssh connections from ? I'm just trying to connect to and from management interface igb0 (192.168.9.60). From external pc I do : ssh myuser@192.168.9.60 From that server I do : ssh myuser@pcaddress Just to be more precise, the consequences are: 1) daemon sshd on the server gets stuck and becomes unkillable 2) the first connection may work, but then the program ssh on the server becomes unresponsive and unkillable If I don't create a lagg0 interface and just connect (say) igb1 to the data switch, I've no problem and everything works. Just to answer others' question, I connect igb1, igb2 and igb3 to the same data switch in ports configured for aggregation. I connect igb0 to another management switch (of course not configured for aggregation) Also, just in case, did you enable any firewall ? (PF, ipfw) As I already said, no. Nothing is working/active on this server, just sshd. Thank you. On 27 August 2012 21:22, Giulio Ferro au...@zirakzigil.org wrote: Hi, thanks for the answer Here is what you asked for: # ifconfig igb0 igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4401bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO ether ... inet 192.168.9.60 netmask 0xff00 broadcast 192.168.9.255 inet6 prefixlen 64 scopeid 0x1 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active # netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.9.1UGS 00 igb0 127.0.0.1 link#12UH 00lo0 192.168.9.0/24 link#1 U 0 14 igb0 192.168.9.60 link#1 UHS 00lo0 192.168.12.0/24link#13U 0 109 lagg0 192.168.12.21 link#13UHS 00lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRS lo0 ::1 link#12 UH lo0 :::0.0.0.0/96 ::1 UGRS lo0 fe80::/10 ::1 UGRS lo0 fe80::%igb0/64link#1U igb0 fe80::ea39:35ff:feb6:a0d4%igb0link#1 UHS lo0 fe80::%igb1/64link#2U igb1 fe80::ea39:35ff:feb6:a0d5%igb1link#2 UHS lo0 fe80::%igb2/64link#3U igb2 fe80::ea39:35ff:feb6:a0d6%igb2link#3 UHS lo0 fe80::%igb3/64link#4U igb3 fe80::ea39:35ff:feb6:a0d7%igb3link#4 UHS lo0 fe80::%lo0/64 link#12 U lo0 fe80::1%lo0 link#12 UHS lo0 fe80::%lagg0/64 link#13 U lagg0 fe80::ea39:35ff:feb6:a0d5%lagg0 link#13 UHS lo0 ff01::%igb0/32fe80::ea39:35ff:feb6:a0d4%igb0 U igb0 ff01::%igb1/32fe80::ea39:35ff:feb6:a0d5%igb1 U igb1 ff01::%igb2/32
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0=laggproto ... ifconfig_lagg0_alias0=inet 192... I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Tue, 11 Sep 2012, Giulio Ferro wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0=inet ... ifconfig_igb1=up ifconfig_igb2=up ifconfig_igb3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 My rc.conf is something like this: # # For now, force ath0 to use the same MAC address as xl0. # This works around a bug where lagg is unable to set the # MAC address of the underlying wlan0 interface. # ifconfig_ath0=ether 01:02:03:04:05:06 wlans_ath0=wlan0 ifconfig_wlan0=ssid SSID_FOO_NAME WPA ifconfig_xl0=up closed_interfaces=lagg0 ifconfig_lagg0=laggproto failover laggport xl0 laggport wlan0 ifconfig_lagg0_alias0=inet 10.0.0.4 netmask 0xff00 I use aliasX to add the address and netmask. -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)
On Tue, 11 Sep 2012, Freddie Cash wrote: On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org wrote: cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24 sshd_enable=YES --- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0=laggproto ... ifconfig_lagg0_alias0=inet 192... I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. This was my experience too, though it's been quite a while since I tried it combined onto the same ifconfig line. -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
