Hi,

        It turned out that the problem is in netinet/in_proto.c.
        (It might have been fixed in -stable long ago, but not
        in 4.2 release. :-)

        yushun.


--- /usr/src/sys/netinet/in_proto.c     Thu Feb  1 14:56:45 2001
+++ /usr/src/sys/netinet/in_proto.c.ORIG        Thu Feb  1 14:38:25 2001
@@ -72,7 +72,6 @@
 #ifdef IPSEC
 #include <netinet6/ipsec.h>
 #include <netinet6/ah.h>
-#include <netinet6/ipcomp.h>
 #ifdef IPSEC_ESP
 #include <netinet6/esp.h>
 #endif
@@ -149,12 +148,6 @@
   ah4_input,   0,              0,              0,
   0,
   0,           0,              0,              0,
-  &nousrreqs
-},
-{ SOCK_RAW,    &inetdomain,    IPPROTO_IPCOMP, PR_ATOMIC|PR_ADDR,
-  ipcomp4_input,0,              0,              0,
-  0,
-  0,            0,              0,              0,
   &nousrreqs
 },
 #ifdef IPSEC_ESP


____________________________________________________________________________
Yu-Shun Wang <[EMAIL PROTECTED]>               Information Sciences Institute
                                           University of Southern California

On Thu, 1 Feb 2001, Jun-ichiro itojun Hagino wrote:

>
> >     No, but the problem is that there was no increase (actually, no
> >     record at all) under ipsec: IPComp. The number on the sending
> >     side seemed right. The increase matched the ones I saw from
> >     tcpdump. It looked like the IPComp packets either weren't
> >     logged or were dropped for some reason.
>
>       send the following items.
>       - full tcpdump output
>       - netstat -sn before, and after the test (on both ends)
>       - full SA configuration on both sides (previous email may have included
>         it)
>       - ifconfig -a output, on both ends
>       - netstat -rn output, on both ends
>       - simple network diagram (like intermediate routers) between both ends
>
> itojun
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the message
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Reply via email to