TCP socket handling errors

2024-04-03 Thread Sad Clouds
Hello, I have a client/server networking application that exhibits TCP socket handling errors. This only happens on FreeBSD, while NetBSD, Linux, Solaris, etc. all seem to work correctly. I was hoping to get some advice on what could be the root cause. I have two processes - client and server,

[Bug 278130] [netgraph][patch] ng_bridge hooks should auto assign number for [up]link

2024-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278130 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are

[Bug 278100] ena (Elastic Network Adapter) driver memory leak on detach

2024-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278100 Arthur Kiyanovski changed: What|Removed |Added CC||akiy...@amazon.com ---

Re: TCP socket handling errors

2024-04-03 Thread Michael Tuexen
> On 3. Apr 2024, at 15:44, Sad Clouds wrote: > > I found a bug that is still open from May 2010 and describes the same > behaviour that I see with my application: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=146845 > > If this hasn't been fixed over the last 14 years, then I guess I

Re: TCP socket handling errors

2024-04-03 Thread Sad Clouds
I found a bug that is still open from May 2010 and describes the same behaviour that I see with my application: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=146845 If this hasn't been fixed over the last 14 years, then I guess I will add some code to simply ignore ECONNRESET on close(2) for

[Bug 278130] [netgraph][patch] ng_bridge hooks should auto assign number for [up]link

2024-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278130 --- Comment #2 from David Marker --- Added review D44615 as requested. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 277849] [bge] panic when attaching if_bge on Supermicro H13SSL-N

2024-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277849 --- Comment #3 from Martin Matuska --- I can confirm that this workaround avoids the panic makes the network card operate: --- a/sys/net/if_media.c +++ b/sys/net/if_media.c @@ -272,19 +272,19 @@ ifmedia_ioctl(struct ifnet *ifp, struct

[Bug 277849] [bge] panic when attaching if_bge on Supermicro H13SSL-N

2024-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277849 --- Comment #4 from Martin Matuska --- Created attachment 249689 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249689=edit Workarounbd patch -- You are receiving this mail because: You are the assignee for the bug.

Re: TCP socket handling errors

2024-04-03 Thread Sad Clouds
On Wed, 3 Apr 2024 17:28:52 +0200 Michael Tuexen wrote: > > On 3. Apr 2024, at 15:44, Sad Clouds wrote: > > > > I found a bug that is still open from May 2010 and describes the same > > behaviour that I see with my application: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=146845

[Bug 278130] [netgraph][patch] ng_bridge hooks should auto assign number for [up]link

2024-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278130 Gleb Smirnoff changed: What|Removed |Added Assignee|n...@freebsd.org |gleb...@freebsd.org