https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193953
Kubilay Kocak changed:
What|Removed |Added
CC||ko...@freebsd.org,
tue...@freebsd.org wrote:
>> On 4. Apr 2021, at 22:28, Rick Macklem wrote:
>>
>> Oops, yes the packet capture is on freefall (forgot to mention that;-).
>> You should be able to:
>> % fetch https://people.freebsd.org/~rmacklem/linuxtofreenfs.pcap
>>
>> Some useful packet #s are:
>> 1949 - partitio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238324
Dutchman01 changed:
What|Removed |Added
CC||dutchma...@quicknet.nl
--- Comment #1
> On 4. Apr 2021, at 22:28, Rick Macklem wrote:
>
> Oops, yes the packet capture is on freefall (forgot to mention that;-).
> You should be able to:
> % fetch https://people.freebsd.org/~rmacklem/linuxtofreenfs.pcap
>
> Some useful packet #s are:
> 1949 - partitioning starts
> 2005 - partition h
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
Rodney W. Grimes wrote:
>And I'll follow the lead to top post, as I have been quietly following
>this thread, trying to only add when I think I have relevant input, and
>I think I do on a small point...
>
>Rick,
>Your "unplugging" a cable to simulate network partitioning,
>in my experience
Oops, yes the packet capture is on freefall (forgot to mention that;-).
You should be able to:
% fetch https://people.freebsd.org/~rmacklem/linuxtofreenfs.pcap
Some useful packet #s are:
1949 - partitioning starts
2005 - partition healed
2060 - last RST
2067 - SYN -> gets going again
This was tak
And I'll follow the lead to top post, as I have been quietly following
this thread, trying to only add when I think I have relevant input, and
I think I do on a small point...
Rick,
Your "unplugging" a cable to simulate network partitioning,
in my experience this is a bad way to do that, a
> On 4. Apr 2021, at 17:27, Rick Macklem wrote:
>
> Well, I'm going to cheat and top post, since this is elated info. and
> not really part of the discussion...
>
> I've been testing network partitioning between a Linux client (5.2 kernel)
> and a FreeBSD-current NFS server. I have not gotten a
Well, I'm going to cheat and top post, since this is elated info. and
not really part of the discussion...
I've been testing network partitioning between a Linux client (5.2 kernel)
and a FreeBSD-current NFS server. I have not gotten a solid hang, but
I have had the Linux client doing "battle" wit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
Alexander V. Chernikov changed:
What|Removed |Added
Status|In Progress |Closed
Resolution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #23 from Aleks ---
(In reply to Alexander V. Chernikov from comment #22)
For me - yes. Thank you very much!
--
You are receiving this mail because:
You are on the CC list for the bug.
__
For what it‘s worth, suse found two bugs in the linux nfconntrack (stateful
firewall), and pfifo-fast scheduler, which could conspire to make tcp sessions
hang forever.
One is a missed updaten when the cöient is not using the noresvport moint
option, which makes tje firewall think rsts are ille
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243703
--- Comment #3 from Alexander V. Chernikov ---
I'm going to proceed with case closure on April 11 unless any feedback is
received.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189088
Alexander V. Chernikov changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #22 from Alexander V. Chernikov ---
All relevant patches are in 13-R.
Does it fix an issue for you?
--
You are receiving this mail because:
You are on the CC list for the bug.
___
fr
16 matches
Mail list logo
