On Sat, Nov 28, 2015 at 03:57:13PM +0100, Reyk Floeter wrote:
> [...]
> But it is documented, right in the beginning of the iked(8) manpage:
> [...]
I didn't intend my message as an insult of your work, if it was
taken as such, please accept my sincere apology.
> [...]
> So what should I do, disa
On 2015/11/28 15:57, Reyk Floeter wrote:
> On Sat, Nov 28, 2015 at 03:19:20PM +0100, Gregor Best wrote:
> > Hi bugs@,
> >
> > it turns out it was just a concidence that I've only noticed the
> > broken IPv6 setup after the upgrade. The real cause of the problem
> > was a half-set up iked which ins
On Sat, Nov 28, 2015 at 03:19:20PM +0100, Gregor Best wrote:
> Hi bugs@,
>
> it turns out it was just a concidence that I've only noticed the
> broken IPv6 setup after the upgrade. The real cause of the problem
> was a half-set up iked which installed
>
> flow esp out from ::/0 to ::/0 type
Hi bugs@,
it turns out it was just a concidence that I've only noticed the
broken IPv6 setup after the upgrade. The real cause of the problem
was a half-set up iked which installed
flow esp out from ::/0 to ::/0 type deny
as a default IPSEC flow. This persisted after a reboot because I h
Hello Gregor,
On 26/11/15(Thu) 22:10, Gregor Best wrote:
> Hi bugs@,
>
> I just upgraded my mailserver to today's snapshot and noticed a
> weird "situation" with IPv6 link local traffic: I get a "No route
> to host" for all operations such as ping6:
I cannot reproduce that with the next snapshot
Hi bugs@,
I just upgraded my mailserver to today's snapshot and noticed a
weird "situation" with IPv6 link local traffic: I get a "No route
to host" for all operations such as ping6:
$ ping6 fe80::1%lo0
PING6 fe80::1%lo0 (fe80::1%lo0): 24 data bytes
ping6: sendmsg: No rout
