On Thu, May 08, 2014 at 08:50:48PM +0200, Michael Tuexen wrote:
> Dear all,
>
> while testing checksum offloading of UDP packets over IP with IP options, I
> figured
> out that my card
>
> dev.re.1.%desc: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet
> dev.re.1.%driver: re
> dev.re.1
On Thu, May 08, 2014 at 08:40:22PM +0200, Michael Tuexen wrote:
> On 07 May 2014, at 10:37, Yonghyeon PYUN wrote:
>
> > On Wed, May 07, 2014 at 10:07:09AM +0200, Michael Tuexen wrote:
> >> On 07 May 2014, at 09:56, Yonghyeon PYUN wrote:
> >>
> >>> On Sat, May 03, 2014 at 11:52:47AM +0200, Micha
Eygene,
On Thu, May 08, 2014 at 12:10:48PM +0400, Eygene Ryabinkin wrote:
E> - I'll do a patch for carp(4) that will allow it to use configurable
E>OUI from a sysctl knob (first 5 bytes of OUI);
Please no sysctl knobs. This should be configurable via ifconfig(8)
per vhid.
P.S. Sorry for
Dear all,
while testing checksum offloading of UDP packets over IP with IP options, I
figured
out that my card
dev.re.1.%desc: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet
dev.re.1.%driver: re
dev.re.1.%location: slot=0 function=0 handle=\_SB_.PCI0.PE1F.LAN2
dev.re.1.%pnpinfo: vendo
On 07 May 2014, at 10:37, Yonghyeon PYUN wrote:
> On Wed, May 07, 2014 at 10:07:09AM +0200, Michael Tuexen wrote:
>> On 07 May 2014, at 09:56, Yonghyeon PYUN wrote:
>>
>>> On Sat, May 03, 2014 at 11:52:47AM +0200, Michael Tuexen wrote:
On 02 May 2014, at 16:02, Bjoern A. Zeeb wrote:
Thu, May 08, 2014 at 05:32:28PM +0400, Eygene Ryabinkin wrote:
> Thu, May 08, 2014 at 12:08:28PM +, Bjoern A. Zeeb wrote:
> > People need to talk. The fact that your server guys use a
> > non-unique Ethernet address for CARP without talking to their local
> > authority who’s in charge of the
Thu, May 08, 2014 at 12:08:28PM +, Bjoern A. Zeeb wrote:
> On 08 May 2014, at 09:50 , Eygene Ryabinkin wrote:
>
> > No, we're conflicting with VRRP on the MAC address space.
> >
> > And, as I understand, CARP in 10 hadn't changed protocol in any way,
> > it just refurbished now CARP instance
On 08 May 2014, at 09:50 , Eygene Ryabinkin wrote:
> No, we're conflicting with VRRP on the MAC address space.
>
> And, as I understand, CARP in 10 hadn't changed protocol in any way,
> it just refurbished now CARP instances are configured and attached to
> the interfaces. Could be wrong here,
Thu, May 08, 2014 at 10:28:19AM +, Bjoern A. Zeeb wrote:
> On 08 May 2014, at 09:50 , Eygene Ryabinkin wrote:
>
> >> Apart from that I thought the different version number was sufficient
> >
> > The thing is that both VRRP and CARP packets use MAC address (on
> > Ethernet at least) that equa
On 08 May 2014, at 09:50 , Eygene Ryabinkin wrote:
>> Apart from that I thought the different version number was sufficient
>
> The thing is that both VRRP and CARP packets use MAC address (on
> Ethernet at least) that equals to 00:00:5e:00:01:$VRID. So in case
> that $VRID is the same and VRRP
Bjoern, good day.
Thu, May 08, 2014 at 09:37:37AM +, Bjoern A. Zeeb wrote:
> On 08 May 2014, at 08:10 , Eygene Ryabinkin wrote:
> > As current CARP implementation somewhat hijacks OUI MAC space for VRRP
> > (00:00:5e:00:01:$VRID) and this sometimes create problems, because
> > routing people
On 08 May 2014, at 08:10 , Eygene Ryabinkin wrote:
> As current CARP implementation somewhat hijacks OUI MAC space for VRRP
> (00:00:5e:00:01:$VRID) and this sometimes create problems, because
> routing people tend to be different from the ones that run CARP
> clusters, so their VRID/VHID can cla
Good day.
As current CARP implementation somewhat hijacks OUI MAC space for VRRP
(00:00:5e:00:01:$VRID) and this sometimes create problems, because
routing people tend to be different from the ones that run CARP
clusters, so their VRID/VHID can clash inside single L2 domain, and
this often leads t
13 matches
Mail list logo
