On Sun, 11 Feb 2018 16:46:48 +0100
Florian Westphal wrote:
> Eyal Birger wrote:
>
> Sorry for taking so long to respond.
>
> > On Tue, 6 Feb 2018 14:15:09 +0100
> > Florian Westphal wrote:
> >
> > > Steffen Klassert wrote:
> > > > I gave the patch a quick try, but still I get this:
> >
Eyal Birger wrote:
Sorry for taking so long to respond.
> On Tue, 6 Feb 2018 14:15:09 +0100
> Florian Westphal wrote:
>
> > Steffen Klassert wrote:
> > > I gave the patch a quick try, but still I get this:
> > >
> > > unregister_netdevice: waiting for dummy1 to become free. Usage
> > > count
On Tue, 6 Feb 2018 14:15:09 +0100
Florian Westphal wrote:
> Steffen Klassert wrote:
> > I gave the patch a quick try, but still I get this:
> >
> > unregister_netdevice: waiting for dummy1 to become free. Usage
> > count = 2
>
> Was that with Eyals setup or the bridge one I posted?
>
> If i
On Tue, Feb 06, 2018 at 02:15:09PM +0100, Florian Westphal wrote:
> Steffen Klassert wrote:
> > I gave the patch a quick try, but still I get this:
> >
> > unregister_netdevice: waiting for dummy1 to become free. Usage count = 2
>
> Was that with Eyals setup or the bridge one I posted?
It was w
Steffen Klassert wrote:
> I gave the patch a quick try, but still I get this:
>
> unregister_netdevice: waiting for dummy1 to become free. Usage count = 2
Was that with Eyals setup or the bridge one I posted?
If it was Eyals setup, its possible the patch missed hookup
to whatever tunnel infra i
On Tue, Feb 06, 2018 at 01:56:24PM +0100, Florian Westphal wrote:
> Eyal Birger wrote:
> > Hi,
> >
> > We've encountered a non released device reference upon device
> > unregistration which seems to stem from xfrm policy code.
> >
> > The setup includes:
> > - an underlay device (e.g. eth0) usin
Eyal Birger wrote:
> Hi,
>
> We've encountered a non released device reference upon device
> unregistration which seems to stem from xfrm policy code.
>
> The setup includes:
> - an underlay device (e.g. eth0) using IPv4
> - an xfrm IPv6 over IPv4 tunnel routed via the underlay device
> - an ipi
Hi Steffen,
On Tue, 6 Feb 2018 09:53:38 +0100
Steffen Klassert wrote:
> Cc Wei Wang
>
> On Sun, Feb 04, 2018 at 01:21:18PM +0200, Eyal Birger wrote:
> > Hi,
> >
> > We've encountered a non released device reference upon device
> > unregistration which seems to stem from xfrm policy code.
> >
Steffen Klassert wrote:
> Cc Wei Wang
>
> On Sun, Feb 04, 2018 at 01:21:18PM +0200, Eyal Birger wrote:
> > Hi,
> >
> > We've encountered a non released device reference upon device
> > unregistration which seems to stem from xfrm policy code.
> >
> > The setup includes:
> > - an underlay device
Cc Wei Wang
On Sun, Feb 04, 2018 at 01:21:18PM +0200, Eyal Birger wrote:
> Hi,
>
> We've encountered a non released device reference upon device
> unregistration which seems to stem from xfrm policy code.
>
> The setup includes:
> - an underlay device (e.g. eth0) using IPv4
> - an xfrm IPv6 over
On Sun, 4 Feb 2018 13:21:18 +0200
Eyal Birger wrote:
> Hi,
>
> We've encountered a non released device reference upon device
> unregistration which seems to stem from xfrm policy code.
>
> The setup includes:
> - an underlay device (e.g. eth0) using IPv4
> - an xfrm IPv6 over IPv4 tunnel routed
Hi,
We've encountered a non released device reference upon device
unregistration which seems to stem from xfrm policy code.
The setup includes:
- an underlay device (e.g. eth0) using IPv4
- an xfrm IPv6 over IPv4 tunnel routed via the underlay device
- an ipip6 tunnel over the xfrm IPv6 tunnel
W
12 matches
Mail list logo
