On Fri, Mar 10, 2017 at 04:14:44PM +0100, Paul de Weerd wrote:
> Hi Rafael, others,
>
> It looks like your commit to ip_mroute.[ch] from January 11th broke
> multicast forwarding. I found another thread that may suffer from the
> same problem: http://marc.info/?l=openbsd-bugs&m=148605155027668&w=
I've looked at this. So far no real clue.
The maddening thing is that the code that triggers single suffix in
the non directory case is the same in freebsd's bmake and ours,
so obviously it doesn't trigger when there's an extra directory, as
the paths don't match.
I'll have to check if there's som
I can confirm Rafael's diff fixes the issues I was having with
multicast.
Thank you very much, Rafael!
Paul
On Mon, Mar 13, 2017 at 06:03:56PM +0100, Rafael Zalamena wrote:
| On Fri, Mar 10, 2017 at 04:14:44PM +0100, Paul de Weerd wrote:
| > Hi Rafael, others,
| >
| > It looks like your commit
On Mon, Mar 13, 2017 at 06:03:56PM +0100, Rafael Zalamena wrote:
> On Fri, Mar 10, 2017 at 04:14:44PM +0100, Paul de Weerd wrote:
> > Hi Rafael, others,
> >
> > It looks like your commit to ip_mroute.[ch] from January 11th broke
> > multicast forwarding. I found another thread that may suffer fro
Hi,
ospf6d does not like beeing reloaded and exits.
Below an example on -current running in VMM. I first noticed it
on an OpenBSD 6.0 amd64 router on real hardware.
Remi
r1# ifconfig -A
lo0: flags=8049 mtu 32768
index 3 priority 0 llprio 3
groups: lo
inet6 ::1 prefixle
Remi Locherer writes:
> Hi,
Hi,
> ospf6d does not like beeing reloaded and exits.
>
> Below an example on -current running in VMM. I first noticed it
> on an OpenBSD 6.0 amd64 router on real hardware.
The issue has already been reported, it's not really new. The code that
handles interfaces a
