Hi All,
Eugene has reported about the following assertion in the ARP code:
http://www.grosbein.net/freebsd/crash/arp-kassert.txt
After some investigation I found that L2 cache has reference leak, that
can lead to integer overflow and this assertion.
The one of the ways to reproduce this o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217749
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: cem
Date: Mon Mar 13 18:05:32 UTC 2017
New revision: 315207
URL: https://svnweb.freebsd.org/changeset/base/315207
Log:
alias_proxy.c: Fix accidental er
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217749
Conrad Meyer changed:
What|Removed |Added
Status|New |Closed
CC|
Just to add a bit more information, the problem appears solely with the
outbound nat via the tun interface. It doesnt matter the rdr is on a
regular nic or not, it still does not work when the nat statement is for
traffic on a tun interface.
So it appears its not possible to nat connections initiat
On Mon, Mar 13, 2017 at 10:13 AM, John Jasen wrote:
> On 03/13/2017 01:03 PM, Navdeep Parhar wrote:
>
>> On Sun, Mar 12, 2017 at 5:35 PM, John Jasen wrote:
>>> UDP traffic. dmesg reports 16 txq, 8 rxq -- which is the default for
>>> Chelsio.
>>>
>> I don't recall offhand, but UDP might be using 2
The issue does not seem to be specific to Chelsio cards. The same tests
with Mellanix cards using the mlx4 drivers exhibit similar behaviors and
results.
On 03/12/2017 06:13 PM, John Jasen wrote:
> I think I am able to confirm Mr. Caraballo's findings.
>
>
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217746
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: np
Date: Mon Mar 13 17:16:29 UTC 2017
New revision: 315201
URL: https://svnweb.freebsd.org/changeset/base/315201
Log:
cxgbe(4): Fix an always-true ass
On 03/13/2017 01:03 PM, Navdeep Parhar wrote:
> On Sun, Mar 12, 2017 at 5:35 PM, John Jasen wrote:
>> UDP traffic. dmesg reports 16 txq, 8 rxq -- which is the default for
>> Chelsio.
>>
> I don't recall offhand, but UDP might be using 2-tuple hashing by
> default and that might affect the distrib
On Sun, Mar 12, 2017 at 5:35 PM, John Jasen wrote:
>
> UDP traffic. dmesg reports 16 txq, 8 rxq -- which is the default for
> Chelsio.
>
I don't recall offhand, but UDP might be using 2-tuple hashing by
default and that might affect the distribution of flows across queues.
Are there senders gener
On 2017-03-13 11:01, Andrey V. Elsukov wrote:
On 12.03.2017 00:23, Hooman Fazaeli wrote:
Hi,
As you know the ipsec/setkey provide limited syntax to define security
policies: only a single subnet/host, protocol number and optional port
may be used to specify traffic's source and destination.
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217721
Eugene Lozovoy changed:
What|Removed |Added
Attachment #180740|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217721
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
I am not sure if I have run into a bug or a limitation. Basically a rdr
on one interface and then a nat on the outbound. It works fine when the
interfaces are two physical network cards like an em and igb. But if
both are tun interfaces, the nat doesnt work
2 servers and one router (all 3 freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217749
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217748
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217746
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
K
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217721
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
K
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217712
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213015
--- Comment #10 from commit-h...@freebsd.org ---
A commit references this bug:
Author: ae
Date: Mon Mar 13 09:04:10 UTC 2017
New revision: 315192
URL: https://svnweb.freebsd.org/changeset/base/315192
Log:
Ignore ifnet renaming in the bpf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637
--- Comment #7 from Alexandre martins ---
The server run FreeBSD 10.3. The client (originally) was a Android smartphone.
In the capture, I use a Ubuntu 16.10 up-to-date.
I cut the capture to avoid to have a big file, but in reality, the fi
Hi,
I had submitted a PR for a panic caused by Open vSwitch a while back:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213015
It looks to be due to traffic being sent while a tap interface is
being renamed, during which if_bpf in the ifnet is set to null. The
following patch does stop the p
On 12.03.2017 00:23, Hooman Fazaeli wrote:
> Hi,
>
> As you know the ipsec/setkey provide limited syntax to define security
> policies: only a single subnet/host, protocol number and optional port
> may be used to specify traffic's source and destination.
>
> I was thinking about the idea of usin
22 matches
Mail list logo
