Re: [PATCH net-next 0/2] bonding: use correct ether type for alb

2014-03-14 Thread David Miller
From: Veaceslav Falico Date: Thu, 13 Mar 2014 12:41:56 +0100 > There have been reports that, while using the ETH_P_LOOP ether type > (0x0060), the ether type is treated as its packet length. > > To avoid that and to not break already existing apps - add new ether type > ETH_P_LOOPBACK that

Re: [PATCH net-next 0/2] bonding: use correct ether type for alb

2014-03-14 Thread David Miller
From: Veaceslav Falico vfal...@redhat.com Date: Thu, 13 Mar 2014 12:41:56 +0100 There have been reports that, while using the ETH_P_LOOP ether type (0x0060), the ether type is treated as its packet length. To avoid that and to not break already existing apps - add new ether type

[PATCH net-next 0/2] bonding: use correct ether type for alb

2014-03-13 Thread Veaceslav Falico
Hi, There have been reports that, while using the ETH_P_LOOP ether type (0x0060), the ether type is treated as its packet length. To avoid that and to not break already existing apps - add new ether type ETH_P_LOOPBACK that contains the correct id - 0x9000. CC: Jay Vosburgh CC: Andy

[PATCH net-next 0/2] bonding: use correct ether type for alb

2014-03-13 Thread Veaceslav Falico
Hi, There have been reports that, while using the ETH_P_LOOP ether type (0x0060), the ether type is treated as its packet length. To avoid that and to not break already existing apps - add new ether type ETH_P_LOOPBACK that contains the correct id - 0x9000. CC: Jay Vosburgh fu...@us.ibm.com