Bug 20473

Summary: socket(AF_INET, SOCK_RAW, 4) no longer works
Product: Base System Reporter: bad <bad>
Component: kernAssignee: itojun
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.1-RELEASE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description bad 2000-08-08 00:30:01 UTC
We use the /dev/tun* devices for transmitting and receiving
protocol ipencap (4) (ip4 inside ip4),
and within our application we open the IPENCAP socket  with
socket(AF_INET, SOCK_RAW, 4). 

This works with 4.0-RELEASE and before. (cvs versions 1.53 and prior
of /sys/netinet/in_proto.c).

Is this no longer correct?

Fix: Workaround - comment out lines in in_proto.c that break our program.
How-To-Repeat: 
	Do a socket(AF_INET, SOCK_RAW, 4); under 4.1-RELEASE
and we get a "Protocol not supported".
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-08 10:42:41 UTC
Responsible Changed
From-To: freebsd-bugs->itojun

Over to one of the KAME folks.
Comment 2 itojun 2000-08-08 16:12:21 UTC
	does it fix the issue?

itojun


Index: in_proto.c
===================================================================
RCS file: /cvsroot/kame/kame/freebsd4/sys/netinet/in_proto.c,v
retrieving revision 1.4
retrieving revision 1.5
diff -c -1 -r1.4 -r1.5
*** in_proto.c	2000/08/05 11:46:54	1.4
--- in_proto.c	2000/08/08 15:11:51	1.5
***************
*** 165,167 ****
    encap_init,		0,		0,		0,
!   &nousrreqs
  },
--- 165,167 ----
    encap_init,		0,		0,		0,
!   &rip_usrreqs
  },
***************
*** 172,174 ****
    0,		0,		0,		0,
!   &nousrreqs
  },
--- 172,174 ----
    0,		0,		0,		0,
!   &rip_usrreqs
  },


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Comment 3 itojun freebsd_committer freebsd_triage 2001-09-06 08:39:41 UTC
State Changed
From-To: open->closed

should have been fixed in sys/netinet/in_proto.c 1.56