Yes to both... From the Netgear's perspective, the LAG looks good.
It's up and both interfaces are full-duplex.

On Sat Mar  3 14:21:36 2012, Dan Shechter <dans...@gmail.com> wrote:

Do you see the LAG up on the netgear?

Do you see the links on the netgear as FD?

Best regards,
Dan



On Sat, Mar 3, 2012 at 8:25 PM, Peter Erickson <redlam...@gmail.com> wrote:

I have a soekris net6501 running obsd 5.0 and am having problems
creating a trunk interface between it and a Netgear GSM7228PS managed
switch. The switch is configured such that ports 23 and 24 are in a LAG
group and all traffic from vlan id's 2 and 3 should leave the lag
tagged. After creating the trunk and vlans on the net6501, I'm finding
that all traffic traveling through the switch is not properly tagged
even though traffic from the net6501 is. If I remove the lag on the
switch and create the vlans on a single interface, everything works as
expected. Based on that, I thought it was a netgear issue and contacted
them. After hours of trouble shooting with no luck, I just happened to
take the same 5.0 image and run it on a soekris net5501. This worked
without any problems when using a trunk so I'm pretty confident that the
switch is configured properly, but am confused about why the trunk
interface will work on a net5501 and not a net6501. The only thing I can
thing of at this point is the net6501 is using the em driver with 4x
Intel 82574IT Gigabit Ethernet ports and the net5501 is using the vr
driver with 4 VIA VT6105M 10/100 Mbit Ethernet ports, but not sure why
it would matter. Any help in identifying the problem would be
appreciated.

This is how I created the interfaces... the only difference between how
I configured the net6501 and the net5501 was that the net5501 uses the
vr driver as opposed to the em.

# ifconfig trunk0 trunkproto lacp trunkport em2 trunkport em3 up
# ifconfig vlan2 inet 172.16.2.253 netmask 255.255.255.0 \
       vlan 2 vlandev trunk0
# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:00:24:ce:69:c4
       priority: 0
       groups: egress
       media: Ethernet autoselect (1000baseT full-duplex)
       status: active
       inet 172.16.3.254 netmask 0xffffff00 broadcast 172.16.3.255
       inet6 fe80::200:24ff:fece:69c4%em0 prefixlen 64 scopeid 0x1
em1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:00:24:ce:69:c5
       priority: 0
       media: Ethernet autoselect (none)
       status: no carrier
em2: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
mtu 1500
       lladdr 00:00:24:ce:69:c6
       priority: 0
       trunk: trunkdev trunk0
       media: Ethernet autoselect (1000baseT full-duplex)
       status: active
       inet6 fe80::200:24ff:fece:69c4%em2 prefixlen 64 scopeid 0x3
em3: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
mtu 1500
       lladdr 00:00:24:ce:69:c6
       priority: 0
       trunk: trunkdev trunk0
       media: Ethernet autoselect (1000baseT full-duplex)
       status: active
       inet6 fe80::200:24ff:fece:69c4%em3 prefixlen 64 scopeid 0x4
trunk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:00:24:ce:69:c6
       priority: 0
       trunk: trunkproto lacp
       trunk id: [(8000,00:00:24:ce:69:c6,4044,0000,0000),
                (8000,c4:3d:c7:92:59:41,01A3,0000,0000)]
               trunkport em3 active,collecting,distributing
               trunkport em2 active,collecting,distributing
       groups: trunk
       media: Ethernet autoselect
       status: active
       inet6 fe80::200:24ff:fece:69c6%trunk0 prefixlen 64 scopeid 0x8
vlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:00:24:ce:69:c6
       priority: 0
       vlan: 2 priority: 0 parent interface: trunk0
       groups: vlan
       status: active
       inet6 fe80::200:24ff:fece:69c6%vlan2 prefixlen 64 scopeid 0x9
       inet 172.16.2.253 netmask 0xffffff00 broadcast 172.16.2.255






--
Peter Erickson
redlam...@gmail.com

Reply via email to