From: Eric Dumazet
Date: Wed, 30 Dec 2015 11:55:25 -0500
> On Wed, 2015-12-30 at 10:11 -0500, Dave Jones wrote:
>> On Wed, Dec 30, 2015 at 10:38:56AM +0100, Daniel Borkmann wrote:
>>
>> > Given that this drop doesn't strictly need to be caused by filter code,
>> > it
On Wed, 2015-12-30 at 10:11 -0500, Dave Jones wrote:
> On Wed, Dec 30, 2015 at 10:38:56AM +0100, Daniel Borkmann wrote:
>
> > Given that this drop doesn't strictly need to be caused by filter code,
> > it would be nice if you could pin the location down where the packet gets
> > dropped
On 12/30/2015 12:50 PM, David Miller wrote:
> From: Eric Dumazet
> Date: Wed, 30 Dec 2015 11:55:25 -0500
>
>> On Wed, 2015-12-30 at 10:11 -0500, Dave Jones wrote:
>>> On Wed, Dec 30, 2015 at 10:38:56AM +0100, Daniel Borkmann wrote:
>>>
>>> > Given that this drop doesn't
On Wed, 2015-12-30 at 12:50 -0500, David Miller wrote:
> From: Eric Dumazet
> Date: Wed, 30 Dec 2015 11:55:25 -0500
>
> > On Wed, 2015-12-30 at 10:11 -0500, Dave Jones wrote:
> >> On Wed, Dec 30, 2015 at 10:38:56AM +0100, Daniel Borkmann wrote:
> >>
> >> > Given that
On 12/29/2015 11:16 PM, Alexei Starovoitov wrote:
> On Tue, Dec 29, 2015 at 10:44:31PM -0500, Doug Ledford wrote:
>> On 12/29/2015 10:43 PM, Alexei Starovoitov wrote:
>>> On Mon, Dec 28, 2015 at 08:26:44PM -0500, Doug Ledford wrote:
On 12/28/2015 05:20 PM, Daniel Borkmann wrote:
> On
On 12/30/2015 05:16 AM, Alexei Starovoitov wrote:
On Tue, Dec 29, 2015 at 10:44:31PM -0500, Doug Ledford wrote:
On 12/29/2015 10:43 PM, Alexei Starovoitov wrote:
On Mon, Dec 28, 2015 at 08:26:44PM -0500, Doug Ledford wrote:
On 12/28/2015 05:20 PM, Daniel Borkmann wrote:
On 12/28/2015 10:53
On Wed, Dec 30, 2015 at 10:38:56AM +0100, Daniel Borkmann wrote:
> Given that this drop doesn't strictly need to be caused by filter code,
> it would be nice if you could pin the location down where the packet gets
> dropped exactly. Perhaps dropwatch or perf with '-e skb:kfree_skb -a -g
>
On 12/29/2015 10:43 PM, Alexei Starovoitov wrote:
> On Mon, Dec 28, 2015 at 08:26:44PM -0500, Doug Ledford wrote:
>> On 12/28/2015 05:20 PM, Daniel Borkmann wrote:
>>> On 12/28/2015 10:53 PM, Doug Ledford wrote:
The 4.4-rc7 kernel is failing for me. In my case, all of my vlan
interfaces
On Mon, Dec 28, 2015 at 08:26:44PM -0500, Doug Ledford wrote:
> On 12/28/2015 05:20 PM, Daniel Borkmann wrote:
> > On 12/28/2015 10:53 PM, Doug Ledford wrote:
> >> The 4.4-rc7 kernel is failing for me. In my case, all of my vlan
> >> interfaces are failing to obtain a dhcp address using dhclient.
On Tue, Dec 29, 2015 at 10:44:31PM -0500, Doug Ledford wrote:
> On 12/29/2015 10:43 PM, Alexei Starovoitov wrote:
> > On Mon, Dec 28, 2015 at 08:26:44PM -0500, Doug Ledford wrote:
> >> On 12/28/2015 05:20 PM, Daniel Borkmann wrote:
> >>> On 12/28/2015 10:53 PM, Doug Ledford wrote:
> The
On 12/28/2015 10:53 PM, Doug Ledford wrote:
The 4.4-rc7 kernel is failing for me. In my case, all of my vlan
interfaces are failing to obtain a dhcp address using dhclient. I've
tried a hand built 4.4-rc7, and the Fedora rawhide 4.4-rc7 kernel, both
failed. I've tried NetworkManager and the
On 12/28/2015 05:20 PM, Daniel Borkmann wrote:
> On 12/28/2015 10:53 PM, Doug Ledford wrote:
>> The 4.4-rc7 kernel is failing for me. In my case, all of my vlan
>> interfaces are failing to obtain a dhcp address using dhclient. I've
>> tried a hand built 4.4-rc7, and the Fedora rawhide 4.4-rc7
Hi Dave,
The 4.4-rc7 kernel is failing for me. In my case, all of my vlan
interfaces are failing to obtain a dhcp address using dhclient. I've
tried a hand built 4.4-rc7, and the Fedora rawhide 4.4-rc7 kernel, both
failed. I've tried NetworkManager and the old SysV network service,
both fail.
13 matches
Mail list logo