On Tue, Jan 27, 2009 at 12:39:26PM -0500, Mike Tancsa wrote: ... > > but if I create some vlan interfaces off lagg0 > > lagg0.100: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > options=3<RXCSUM,TXCSUM> > ether 00:30:48:90:4c:fe > inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 > media: Ethernet autoselect > status: active > vlan: 100 parent interface: lagg0 > lagg0.102: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > options=3<RXCSUM,TXCSUM> > ether 00:30:48:90:4c:fe > inet 192.168.102.1 netmask 0xffffff00 broadcast 192.168.102.255 > media: Ethernet autoselect > status: active > vlan: 102 parent interface: lagg0 > > and do the same pulling of the cable, it does not work. BUT, if I do an > arp -nda on a machine that is part of vlan102 which is doing the pinging > (so an arp-who has gets sent out and a reply answered), it works. The > other option is if I send a packet out on the vlan's broadcast address from > the server
Can you verify that em2, em3 and all the lagg* interfaces have the same mac address. Andrew _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[email protected]"
