Date: Wed, 17 May 2006 10:41:17 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp> Cc: freebsd-net@freebsd.org, Hideki Yamamoto <yamamoto436@oki.com>, freebsd-pf@freebsd.org Subject: Re: IPv6 raw socket to send original udp Message-ID: <20060517103906.P49041@fledge.watson.org> In-Reply-To: <y7v64k6qiab.wl%jinmei@isl.rdc.toshiba.co.jp> References: <20060508.054451.41688849.yamamoto436@oki.com> <y7v64k6qiab.wl%jinmei@isl.rdc.toshiba.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060517103906.P49041>