[Bug 250366] [tcp] The ioctl of socket fd should return -1 after listen to avoid misusing.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250366 Kubilay Kocak changed: What|Removed |Added URL||https://reviews.freebsd.org

Confirmation On Submission of Contact Form

___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Pinning Threads

Hello All I was curious about what you think of this solution to not having enough cores. I have an 8 core server with a solarflare nic. The Nic is a two port card so it will have 8 queues per port. Next I have netisr set to start 8 threads as well. Now to get the better performance out of pf and

'dropped due to full socket buffers' by SNMP

Hi All Can somebody help me to get UDP 'dropped due to full socket buffers' by SNMP? Is it possible? Now I'm getting it with `netstat -n -p udp -f inet -s` but SNMP will be more useful for remote monitoring. Thanks! -- CU, Victor Gamov ___ freebsd

[Bug 250499] [tcp] Should we reject the packet with timestamp if no timestamp in SYN and SYN_ACK?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250499 Michael Tuexen changed: What|Removed |Added Flags|mfc-stable12?, |mfc-stable12+,

[Bug 250499] [tcp] Should we reject the packet with timestamp if no timestamp in SYN and SYN_ACK?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250499 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: tuexen Date: Mon Nov 30 10:58:07 UTC 2020 New revision: 368183 URL: https://svnweb.freebsd.org/changeset/base/368183 Log: MFC r367530: RFC 7323 spe

[Bug 250366] [tcp] The ioctl of socket fd should return -1 after listen to avoid misusing.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250366 Michael Tuexen changed: What|Removed |Added Status|In Progress |Closed Flags|mfc-sta

[Bug 250499] [tcp] Should we reject the packet with timestamp if no timestamp in SYN and SYN_ACK?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250499 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: tuexen Date: Mon Nov 30 09:45:45 UTC 2020 New revision: 368181 URL: https://svnweb.freebsd.org/changeset/base/368181 Log: MFC r367530: RFC 7323 speci

Re: ipfw nat bug

30.11.2020 16:10, Eugene Grosbein wrote: > Hi! > > It seems I'm facing a bug in NAT44 ipfw nat/libalias implementation. > > Suppose we have a LAN 192.168.0.0/24 and two WAN channels with public IP > addresses > and internal server 192.168.0.100 that serves connection to the port 5060, > both T

[Bug 250366] [tcp] The ioctl of socket fd should return -1 after listen to avoid misusing.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250366 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: tuexen Date: Mon Nov 30 09:21:02 UTC 2020 New revision: 368179 URL: https://svnweb.freebsd.org/changeset/base/368179 Log: MFC r367464: The ioctl() ca

ipfw nat bug

Hi! It seems I'm facing a bug in NAT44 ipfw nat/libalias implementation. Suppose we have a LAN 192.168.0.0/24 and two WAN channels with public IP addresses and internal server 192.168.0.100 that serves connection to the port 5060, both TCP and UDP, so we configure redirects: nat 1 config if vl

80% Sconto Black Friday su Email Marketing + garanzia risultati fino al 15%

Lanciamo sottocosto le vostre campagne email promozionali a imprese e privati in conformità, profilati e geolocalizzati, certificate ISO9001 e ISO27001 e garanzia rimborso 100% Potete scegliere fra 10.000.000 di email imprese, 20.000.000 di Consumer o estero. Includiamo creazione del messaggio