https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #8 from Richard Scheffenegger ---
Rescue Retransmission for SACK is not in releng/13.0, thus D29315 is unlikely
to be the problem here.
There was another known panic (but with a KASSERT giving it away), fixed with
D29083, but
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #9 from Richard Scheffenegger ---
The two cores look vastly different - and the 2nd one would be interesting to
me to see what is going on in detail. There is no trace of TCP stack
involvement
in the original (BETA3) core dump.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #10 from shamaz.ma...@gmail.com ---
I think, the main search vector is why there are no panics when
net.link.ether.ipfw sysctl is set to 0 and there are panics when it is set to
1.
I pasted my ipfw rules earlier, so you can see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment #
On 22 Mar 2021, at 22:45, Alan Somers wrote:
> On Mon, Mar 22, 2021 at 7:31 PM Kevin Bowling
> wrote:
>
>> Hi,
>>
>> I was talking with gnn and kevans on IRC about the tcp testsuite
>> (https://github.com/freebsd-net/tcp-testsuite).
>>
>> Currently we maintain this in ports, although the way t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #12 from Aleks ---
(In reply to Alexander V. Chernikov from comment #9)
I've sent you what you asked for (in email).
--
You are receiving this mail because:
You are on the CC list for the bug.
_
> On 23. Mar 2021, at 02:31, Kevin Bowling wrote:
>
> Hi,
>
> I was talking with gnn and kevans on IRC about the tcp testsuite
> (https://github.com/freebsd-net/tcp-testsuite).
>
> Currently we maintain this in ports, although the way the port is set
> up doesn't make a lot of sense because
> On 23. Mar 2021, at 03:45, Alan Somers wrote:
>
> On Mon, Mar 22, 2021 at 7:31 PM Kevin Bowling
> wrote:
> Hi,
>
> I was talking with gnn and kevans on IRC about the tcp testsuite
> (https://github.com/freebsd-net/tcp-testsuite).
>
> Currently we maintain this in ports, although the way the
> On 23. Mar 2021, at 12:26, George Neville-Neil wrote:
>
>
>
> On 22 Mar 2021, at 22:45, Alan Somers wrote:
>
>> On Mon, Mar 22, 2021 at 7:31 PM Kevin Bowling
>> wrote:
>>
>>> Hi,
>>>
>>> I was talking with gnn and kevans on IRC about the tcp testsuite
>>> (https://github.com/freebsd-net/t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #12 from Richard Scheffenegger ---
Can you share the 2nd core dump and kernel?
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_
>> Yeah, it's not a problem to use binaries from ports in /usr/tests. As
>> long as the tests can compile they can live in the base system. Is
>> there a strong incentive to import them?
>
> The tests are just scripts, which can be executed by packetdrill, which is
> available in the ports tr
Kevin Bowling wrote this message on Mon, Mar 22, 2021 at 18:31 -0700:
> I was talking with gnn and kevans on IRC about the tcp testsuite
> (https://github.com/freebsd-net/tcp-testsuite).
>
> Currently we maintain this in ports, although the way the port is set
> up doesn't make a lot of sense beca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
Alexander V. Chernikov changed:
What|Removed |Added
Status|New |In Progress
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #13 from shamaz.ma...@gmail.com ---
Can you reproduce by it yourself by adding net.link.ether.ipfw = 0 to
/etc/sysctl.conf
and writing firewall rules like these:
#!/bin/sh
IPFW="/sbin/ipfw -q"
IFACE="wg0"
PUB_IFACE="re1"
SKIP_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #14 from shamaz.ma...@gmail.com ---
Disregard my last message. Tryed layer2 filtering on my second machine. All
works fine. It causes trouble only at the first one.
--
You are receiving this mail because:
You are the assignee f
15 matches
Mail list logo
