Alexander Bluhm wrote Monday, August 08, 2011 10:50 AM
> On Sun, Aug 07, 2011 at 04:02:32AM +0200, Florian Fuessl wrote:
> > Alexander Bluhm wrote Sat., Aug. 06, 2011
> > > On Sat, Aug 06, 2011 at 12:47:27AM +0200, Alexander Bluhm wrote:
> > > > To trigger the bug, you need two adresses in the sam
On Sun, Aug 07, 2011 at 04:02:32AM +0200, Florian Fuessl wrote:
> Alexander Bluhm wrote Sat., Aug. 06, 2011
> > On Sat, Aug 06, 2011 at 12:47:27AM +0200, Alexander Bluhm wrote:
> > > To trigger the bug, you need two adresses in the same network on
> > > the carp and on the parent interface. One o
Alexander Bluhm wrote Sat., Aug. 06, 2011
> On Sat, Aug 06, 2011 at 12:47:27AM +0200, Alexander Bluhm wrote:
> > To trigger the bug, you need two adresses in the same network on
> > the carp and on the parent interface. One of them has the route,
> > the other cannot do ndp.
>
> The bridge has t
Todd T. Fries wrote Fri, Aug. 05, 2011 6:06 PM
>
> Are you using global IPv6 addresses for your test or link-local
> addresses for your test?
I'm using global IPv6 addresses.
i.e.
host side ping6:
...@melon:~$ ping6 2a00:1230::feed:cafe
PING 2a00:1230::feed:cafe(2a00:1230::feed:cafe) 56 data byt
On Sat, Aug 06, 2011 at 12:47:27AM +0200, Alexander Bluhm wrote:
> To trigger the bug, you need two adresses in the same network on
> the carp and on the parent interface. One of them has the route,
> the other cannot do ndp.
The bridge has the same problem there, bridge and carp can be fixed
in
On Fri, Aug 05, 2011 at 11:50:41PM +0200, Alexander Bluhm wrote:
> On Fri, Aug 05, 2011 at 02:00:21PM +0200, Florian Fuessl wrote:
> > Feature or bug?
>
> Sounds like a bug, but I cannot reproduce it.
To trigger the bug, you need two adresses in the same network on
the carp and on the parent inte
On Fri, Aug 05, 2011 at 02:00:21PM +0200, Florian Fuessl wrote:
> Feature or bug?
Sounds like a bug, but I cannot reproduce it.
> Latest snapshot /bsd kernel (03. Aug. 11) does not react to neighbor
> discovery requests for inet6 address on carp master interface, here.
With this kernel
kern.
Are you using global IPv6 addresses for your test or link-local addresses
for your test?
I have found that you sometimes need to ping6 the link-local address
on a carp interface from a workstation before it will respond to ndp.
For reference, this scenario happens if you run rtadvd against a carp
Feature or bug?
Latest snapshot /bsd kernel (03. Aug. 11) does not react to neighbor
discovery requests for inet6 address on carp master interface, here.
-Florian
