From owner-freebsd-net  Mon Aug  7  9:48:37 2000
Delivered-To: freebsd-net@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP id EAB1437BC88
	for <net@freebsd.org>; Mon,  7 Aug 2000 09:48:32 -0700 (PDT)
	(envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id BAA21907;
	Tue, 8 Aug 2000 01:48:22 +0900 (JST)
To: Bernie Doehner <bad@wireless.net>
Cc: net@freebsd.org
In-reply-to: bad's message of Mon, 07 Aug 2000 07:11:55 MST.
      <Pine.BSF.3.95.1000807071137.8232C-100000@wireless.net>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: Restoring old IPv4 raw socket behavior under 4.1-RELEASE 
From: itojun@iijlab.net
Date: Tue, 08 Aug 2000 01:48:22 +0900
Message-ID: <21905.965666902@coconut.itojun.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Just upgraded from 4.0-RELEASE to 4.1-RELEASE, and now a custom
>application of ours that used to do:
>
>socket(AF_INET, SOCK_RAW, 4); 
>
>No longer works with:
>Protocol not supported opening socket.
>
>As far as I can tell, this is because SOCK_RAW sockets now default to
>IPv6. Is there a SIMPLE way to restore old ipv4 SOCK_RAW
>socket() behavior, so that I don't need to have any IPv6 routes at all?

	no, the observation is incorrect.  we simply need rip_{output,ctloutput}
	family listed in protosw.

itojun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message