https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217721
--- Comment #4 from Eugene Lozovoy ---
(In reply to Pyun YongHyeon from comment #3)
>Wouldn't you're able to send packets again if you wait some more
>time(i.e. link establishment time + time taken to empty queued
>packets)?
No, I waited ~
On Wed, Mar 15, 2017 at 7:33 PM, Kristof Provost wrote:
> On 15 Mar 2017, at 22:10, Mike Tancsa wrote:
>
>> On 3/15/2017 4:28 AM, Kristof Provost wrote:
>>
>>> I don’t see any obvious reason why that would happen.
>>>
>>> Can you reduce this to a minimal test setup and include rc.conf,
>>> pf.con
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217721
--- Comment #3 from Pyun YongHyeon ---
(In reply to Eugene Lozovoy from comment #2)
Wouldn't you're able to send packets again if you wait some more
time(i.e. link establishment time + time taken to empty queued
packets)?
I guess your patc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409
Luiz Otavio O Souza,+55 (14) 99772-1255 changed:
What|Removed |Added
Status|New |In Progre
On 15 Mar 2017, at 22:10, Mike Tancsa wrote:
On 3/15/2017 4:28 AM, Kristof Provost wrote:
I don’t see any obvious reason why that would happen.
Can you reduce this to a minimal test setup and include rc.conf,
pf.conf, …
with a bug report in bugzilla?
is it possible that its how OpenVPN sets
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209581
--- Comment #6 from Kaho Toshikazu ---
(In reply to ingenium from comment #5)
＞ Are you suggesting simply deleting that line from 10.3 and it may allow
＞ vlan tags to not be stripped?
Yes. I don't know that the code setting the vlan filter
On 3/9/2017 1:31 PM, Bryan Drewery wrote:
> This came up at shutdown in r314708. I don't yet know if I will have a
> core to diagnose.
>
>> panic: Assertion err == 0 failed at /usr/src/sys/net/iflib.c:2241
>> cpuid = 0
>> KDB: stack backtrace:
>> db_trace_self_wrapper() at db_trace_self_wrapper+0x
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209581
--- Comment #5 from ingen...@gmail.com ---
(In reply to Kaho Toshikazu from comment #4)
I'm not sure that I follow? Are you suggesting simply deleting that line from
10.3 and it may allow vlan tags to not be stripped?
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637
--- Comment #12 from Michael Tuexen ---
I did some testing and can explain some of the aspects of the traces,
especially the ones on the FreeBSD side.
The client establishes the TCP connection and send the first fragment of the
HTTP reques
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217782
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: mizhka
Date: Wed Mar 15 18:57:19 UTC 2017
New revision: 315324
URL: https://svnweb.freebsd.org/changeset/base/315324
Log:
[bhnd] fix mask for PMU contr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #9 from Aiko Barz ---
(In reply to Aiko Barz from comment #8)
The Lifecycle method does not work at the moment. But I installed the firmware
version 16.5.20 from 05/12/2016. That firmware was offered as a Redhat shell
script pa
On 3/15/2017 4:28 AM, Kristof Provost wrote:
> I don’t see any obvious reason why that would happen.
>
> Can you reduce this to a minimal test setup and include rc.conf, pf.conf, …
> with a bug report in bugzilla?
is it possible that its how OpenVPN sets up the tun interface ?
Otherwise nat via p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #8 from Aiko Barz ---
(In reply to Andrey V. Elsukov from comment #7)
We did not have those issues with 10.1. But I keep your advise in mind.
I currently try to upgrade all those firmware-packages. Unfortunately the Dell
Lifec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
Andrey V. Elsukov changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #6 from Aiko Barz ---
Hardware: Dell PowerEdge R320
* Intel Xeon E5-2430 v2 (2,5GHz, 6C, 15MB Cache, 7,2GT/s QPI, 80W, Turbo)
* PowerEdge R320 Mainboard, TPM
* Intel Ethernet I350 DP 1Gbit/s Serveradapter, Low Profile
* Intel X5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217784
Kevin Lo changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217784
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kevlo
Date: Wed Mar 15 09:31:58 UTC 2017
New revision: 315294
URL: https://svnweb.freebsd.org/changeset/base/315294
Log:
Fix unreachable code in wi_pci
I don’t see any obvious reason why that would happen.
Can you reduce this to a minimal test setup and include rc.conf, pf.conf, …
with a bug report in bugzilla?
Thanks,
Kristof
On 14 Mar 2017, at 2:56, Mike Tancsa wrote:
> Just to add a bit more information, the problem appears solely with the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257
--- Comment #28 from Luiz Otavio O Souza,+55 (14) 99772-1255
---
Any issues or regressions ?
If not, can I close this PR ?
--
You are receiving this mail because:
You are the assignee for the bug.
___
Looks like my scripts did not come through.
Here is a link to them
https://paste.ee/p/lB3iE
Best,
Reshad
On 14 March 2017 23:55:23 GMT+05:30, Reshad Patuck
wrote:
>Hi,
>
>I am trying to use vnet and pf to host multiple (100s of) jails on a
>server with a jailed pf router, which will be spun
20 matches
Mail list logo
