Date: Wed, 29 Oct 1997 16:14:22 -0600 From: Jonathan Lemon <jlemon@americantv.com> To: Sunthiti Patchararungruang <stt@pluto.cpe.ku.ac.th> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel modification Message-ID: <19971029161422.12013@right.PCS> In-Reply-To: <Pine.BSF.3.96.971029220052.15259A-101000@pluto.cpe.ku.ac.th>; from Sunthiti Patchararungruang on Oct 10, 1997 at 10:19:26PM %2B0700 References: <Pine.BSF.3.96.971029220052.15259A-101000@pluto.cpe.ku.ac.th>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 10, 1997 at 10:19:26PM +0700, Sunthiti Patchararungruang wrote: > First of all. I would like to appologize that this mail is > off-topic of yours but I don't know where to post it to. For this type of thing, hackers@freebsd.org would probably be the most appropriate place. > program on FreeBSD2.2.2. It need to copy a data link frame from an > interface to another one. The data frame must not be changed even in > ethernet address field. I use BPF. I have found that the system always > change my ethernet source address to the address of the output interface. AFAIK, this is correct. I believe that the Ethernet specification requires that the source MAC address in the ethernet frame correspond to the hardware address of the transmitting device. I can't see why you would want to re-transmit with the original MAC address; this would cause arp lookups to fail, among other things. Even bridges put their own MAC address in the frame. > However, I have corrected the problem. I modified the kernel, already > attach all files with this mail, to add two things. They are: In the future, it would probably be better to submit something as a diff against a specified FreeBSD revision, instead of sending the files in their entirety. -- Jonathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971029161422.12013>