On Sun, Dec 22, 2013 at 1:10 PM, wrote:
> Thank you very much for your problem report.
> It has the internal identification `misc/185092'.
> The individual assigned to look at your
> report is: freebsd-bugs.
>
> You can access the state of your problem report at any time
> via this link:
>
> http
The following reply was made to PR misc/185092; it has been noted by GNATS.
From: Nikolay Denev
To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org,
"freebsd-...@freebsd.org"
Cc:
Subject: Re: misc/185092: panic: rtfree 2 (using RADIX_MPATH in a VNET jail)
Date: Wed, 1 Jan 2
On Wed, Jan 1, 2014 at 1:10 PM, Nikolay Denev wrote:
> On Sun, Dec 22, 2013 at 1:10 PM, wrote:
>
>> Thank you very much for your problem report.
>> It has the internal identification `misc/185092'.
>> The individual assigned to look at your
>> report is: freebsd-bugs.
>>
>> You can access the st
>Number: 185387
>Category: kern
>Synopsis: if_axe usb ethernet interface no ssh, no http with 10.0-RC3
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Number: 185390
>Category: bin
>Synopsis: freebsd-update should work on installed version
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class:
Ok, killing openvpn with -9 leaves the routes around, and particularly
interesting are the following routes :
78.90.222.xx 10.255.255.0 UGHS0 5841 epair0 =>
78.90.222.xx/3210.255.255.0 UGS 00 epair0
Now, if I do :
route delete 78.90.2
The following reply was made to PR misc/185092; it has been noted by GNATS.
From: Nikolay Denev
To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org,
"freebsd-...@freebsd.org"
Cc:
Subject: Re: misc/185092: panic: rtfree 2 (using RADIX_MPATH in a VNET jail)
Date: Wed, 1 Jan 2
>Number: 185393
>Category: bin
>Synopsis: find -lname buffer read overflow bug
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Number: 185395
>Category: kern
>Synopsis: IPv4 Multicast broken in 10.x
>Confidential: no
>Severity: serious
>Priority: high
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter
The following reply was made to PR bin/185393; it has been noted by GNATS.
From: Ben Reser
To: bug-follo...@freebsd.org
Cc:
Subject: Re: bin/185393: find -lname buffer read overflow bug
Date: Wed, 01 Jan 2014 12:03:04 -0800
This is a multi-part message in MIME format.
--080101030
The following reply was made to PR kern/185395; it has been noted by GNATS.
From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?=
To: Peter Jeremy , Gleb Smirnoff
Cc: freebsd-gnats-submit
Subject: Re: kern/185395: IPv4 Multicast broken in 10.x
Date: Wed, 1 Jan 2014 22:03:36 +0100
--047d7b86db46eaf
Synopsis: Frequent reboots due to kernel trap happening in pf_test_rule
State-Changed-From-To: open->closed
State-Changed-By: glebius
State-Changed-When: Wed Jan 1 21:51:17 UTC 2014
State-Changed-Why:
This is duplicate of 182141, and the latter has much more information in it,
so preferred to be
Old Synopsis: Very frequent (at most 3 hours) kernel trap 12
New Synopsis: [pf] crash in pf_test_rule
State-Changed-From-To: open->feedback
State-Changed-By: glebius
State-Changed-When: Wed Jan 1 21:53:02 UTC 2014
State-Changed-Why:
Patch sent to submitter for testing.
Responsible-Changed-From-
>Number: 185406
>Category: misc
>Synopsis: update py-django-simple-captcha from 0.4.0 to 0.4.1
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class:
The following reply was made to PR kern/185395; it has been noted by GNATS.
From: Peter Jeremy
To: Olivier =?iso-8859-1?Q?Cochard-Labb=E9?=
Cc: freebsd-gnats-submit
Subject: Re: kern/185395: IPv4 Multicast broken in 10.x
Date: Thu, 2 Jan 2014 17:47:56 +1100
--s9fJI615cBHmzTOP
Content-Type: t
15 matches
Mail list logo
