src/sys/netinet/ip_output.c, branch release/3.3.0_cvs FreeBSD source tree This commit was manufactured by cvs2svn to create tag 1999-09-16T08:26:13+00:00 cvs2svn cvs2svn@FreeBSD.org 1999-09-16T08:26:13+00:00 5be28542797ac26e17de490f50e0830003596d38 'RELENG_3_3_0_RELEASE'. This commit was manufactured to restore the state of the 3.3-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs. 
'RELENG_3_3_0_RELEASE'.

This commit was manufactured to restore the state of the 3.3-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.
$Id$ -> $FreeBSD$ 1999-08-29T16:33:42+00:00 Peter Wemm peter@FreeBSD.org 1999-08-29T16:33:42+00:00 c4f617ca01b475bdf034553dfe123deeb1589899 






MFC: free the dummynet header in ip_dummynet, not in the called
1999-05-04T16:24:00+00:00

Luigi Rizzo
luigi@FreeBSD.org

1999-05-04T16:24:00+00:00

41bfb6539404f7d94977ed16b629cd9e880d52da

routine.





routine.







MFC: fix "arp: host is not local" problem with dummynet
1999-03-16T18:03:28+00:00

Luigi Rizzo
luigi@FreeBSD.org

1999-03-16T18:03:28+00:00

ba9ad9cc2abf3b1656f35106ecc4aac01dd7cd5a












MFC: prevent panic when pkts > MTU and with DF set get out of a pipe.
1999-02-19T18:56:58+00:00

Luigi Rizzo
luigi@FreeBSD.org

1999-02-19T18:56:58+00:00

10fdb1db5303420edefe2275cb8ab33e1f15bd07

Actually, after fixing this for the third time (in HEAD, RELENG_3
and RELENG_2_2) i notice that there are a few more places in
ip_output() potentially with a similar problem:

the head of the mbuf chain is changed, yet the original pointer m0
(which is used in case the pkt exceeds the MTU and has DF set) is
not updated. This could lead to panics or more likely to mbuf leaks
depending on what happens to the original mbuf pointed by m0.
Something worth fixing soon...





Actually, after fixing this for the third time (in HEAD, RELENG_3
and RELENG_2_2) i notice that there are a few more places in
ip_output() potentially with a similar problem:

the head of the mbuf chain is changed, yet the original pointer m0
(which is used in case the pkt exceeds the MTU and has DF set) is
not updated. This could lead to panics or more likely to mbuf leaks
depending on what happens to the original mbuf pointed by m0.
Something worth fixing soon...







Restore 1.82->1.83 change deleted by mistake< per Bruce suggestion
1998-12-21T21:36:40+00:00

Luigi Rizzo
luigi@FreeBSD.org

1998-12-21T21:36:40+00:00

f0f6d6434dae6f048d18395b2067ce09fc8b804b












Last bits (i think) of dummynet for -current.
1998-12-14T18:09:13+00:00

Luigi Rizzo
luigi@FreeBSD.org

1998-12-14T18:09:13+00:00

b715f178c6489ac99e3c10fb85bb6b42146648b6












add #include <sys/kernel.h> where it's needed by MALLOC_DEFINE()
1998-11-10T09:16:29+00:00

Peter Wemm
peter@FreeBSD.org

1998-11-10T09:16:29+00:00

1c5bb3eaa14c4be2cc54700ffe7e9dce193f3219












Properly fragment multicast packets.
1998-09-02T15:11:14+00:00

Garrett Wollman
wollman@FreeBSD.org

1998-09-02T15:11:14+00:00

db028362a0feb54e958d9f0aeb6e75aa62ae7e6e

PR: 7802
Submitted by:	Steve McCanne <mccanne@cs.berkeley.edu>





PR: 7802
Submitted by:	Steve McCanne <mccanne@cs.berkeley.edu>







Yow!  Completely change the way socket options are handled, eliminating
1998-08-23T03:07:17+00:00

Garrett Wollman
wollman@FreeBSD.org

1998-08-23T03:07:17+00:00

cfe8b629f1f13b06fa1aec801248b7e431e48aba

another specialized mbuf type in the process.  Also clean up some
of the cruft surrounding IPFW, multicast routing, RSVP, and other
ill-explored corners.





another specialized mbuf type in the process.  Also clean up some
of the cruft surrounding IPFW, multicast routing, RSVP, and other
ill-explored corners.