Fragment questions

Hello, I noticed two questionable things in the fragmentation code: - in ip_fragment, we do not copy the flowid from the original mbuf to the fragmented mbuf. Therefore we may output very desynchronized fragments (first fragment emitted far later the second fragment, etc.) - in the ip_newid macr

Re: Fragment questions

Hello, Yes indeed, it has already been fixed! However, the second point seems to be still here... Regards, Emeric - Mail original - De: "Hans Petter Selasky" À: "Emeric POUPON" , "freebsd-net" Envoyé: Jeudi 19 Mars 2015 13:54:33 Objet: Re: Fragmen

Re: Fragment questions

Hello, Please find attached a proposal using atomic_fetchadd. Best Regards, Emeric - Mail original - De: "Adrian Chadd" À: "Hans Petter Selasky" Cc: "Emeric POUPON" , "freebsd-net" Envoyé: Vendredi 20 Mars 2015 20:04:44 Objet: Re: Fragment qu

Re: Fragment questions

Ok for the function. Please find the review here: https://reviews.freebsd.org/D2141 Regards, Emeric - Mail original - De: "Hans Petter Selasky" À: "Emeric POUPON" , "Adrian Chadd" Cc: "freebsd-net" Envoyé: Mercredi 25 Mars 2015 14:41:46 Objet

Re: Patch to reduce use of global IP ID value(s) to avoid leaking information

> I'm talking about sampling the IP ID value you get in return from a PING > response. A firewall typically has multiple ports. If pinging the > gateway from any of these ports cause an increment of a shared IP ID > value, then anyone that can ping the common firewall will see the IP ID > updat

Multicast routing questions

Hello, I'm testing multicast routing on FreeBSD 9.3 and I have a question: In packet reception, it seems the packet is received locally as many times the packet is rerouted + 1: ip_input -> ip_mforward -> ip_output (as many times there are dst interfaces in the route cache entry) -> ip_mloopbac

Re: Multicast routing questions

necessary. Emeric - Mail original - De: "Emeric POUPON" À: freebsd-net@freebsd.org Envoyé: Mercredi 24 Juin 2015 10:22:45 Objet: Multicast routing questions Hello, I'm testing multicast routing on FreeBSD 9.3 and I have a question: In packet reception, it seems the pack

Re: Multicast routing questions

prevents "infinite" loops. Is that really how it is meant to be done? Emeric - Mail original - De: "Andrey V. Elsukov" À: "Emeric POUPON" , freebsd-net@freebsd.org Envoyé: Jeudi 25 Juin 2015 07:48:44 Objet: Re: Multicast routing questions On 24.06.2015 18

IPsec: question on the sysctl preferred_oldsa

Hello, I have some questions about the sysctl "net.key.preferred_oldsa": https://svnweb.freebsd.org/base/head/sys/netipsec/key.c?view=markup#l971 When I set the net.key.preferred_oldsa to 0 (similar to Linux's behavior, according to what I have read so far): - why does the kernel delete itself t

Re: IPsec: question on the sysctl preferred_oldsa

l - De: "Emeric POUPON" À: "FreeBSD Net" Envoyé: Lundi 17 Août 2015 10:07:45 Objet: IPsec: question on the sysctl preferred_oldsa Hello, I have some questions about the sysctl "net.key.preferred_oldsa": https://svnweb.freebsd.org/base/head/sys/netipse

IPSec and large replay window support

Hello, We plan to support large replay windows in the IPsec stack. Currently, the replay window size is limited due to the size of the field used in the sadb_sa_replay structure. https://www.ietf.org/rfc/rfc2367.txt : struct sadb_sa { uint16_t sadb_sa_len;

Vlan offloaded checksums

Hello, I have a network driver that supports hardware checksums. Thanks to offset parameters, it also supports VLAN checksums. However, it does not handle hardware tagging (not sure the underlying network adapter can actually do it) Unfortunately, the VLAN hardware checksums seem to be done only

Re: IPSec and large replay window support

Hello, Here is what we did for this: https://reviews.freebsd.org/D8468 Regards - Original Message - > From: "Emeric POUPON" > To: "FreeBSD Net" > Cc: j...@freebsd.org, g...@freebsd.org > Sent: Wednesday, 8 June, 2016 14:12:48 > Subject: IPSec and l