From owner-freebsd-net@FreeBSD.ORG Wed May 17 09:41:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D97B816A426; Wed, 17 May 2006 09:41:18 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6B9643D4C; Wed, 17 May 2006 09:41:17 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 54A0D46CD8; Wed, 17 May 2006 05:41:17 -0400 (EDT) Date: Wed, 17 May 2006 10:41:17 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= In-Reply-To: Message-ID: <20060517103906.P49041@fledge.watson.org> References: <20060508.054451.41688849.yamamoto436@oki.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1849780989-1147858877=:49041" Cc: freebsd-net@freebsd.org, Hideki Yamamoto , freebsd-pf@freebsd.org Subject: Re: IPv6 raw socket to send original udp X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 May 2006 09:41:26 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1849780989-1147858877=:49041 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 16 May 2006, JINMEI Tatuya / [ISO-2022-JP] =BF=C0=CC=C0=C3=A3=BA=C8= wrote: > So, if a program needs to specify an arbitrary source IPv6 address for=20 > outgoing packets, it should use other "packet injection" interface such a= s=20 > BPF. One problem with using BPF for packet injection in IPv4 is that it requires= =20 the sender to provide the link layer encapsulation, make the routing decisi= on,=20 and perform any address resolution. Using raw sockets with the full header= =20 option allows the sender to generate a datagram from an arbitrary source ye= t=20 not perform those routing and link layer activities, which require more=20 intimate knowledge of the link type. It might be desirable to add a socket= =20 option to allow the specification of the source address in order to allow= =20 packet replay tools, etc, to work without link layer knowledge. Robert N M Watson --0-1849780989-1147858877=:49041--