From owner-freebsd-hackers Thu Sep 20 17: 5: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta6-rme.xtra.co.nz (mta6-rme.xtra.co.nz [203.96.92.19]) by hub.freebsd.org (Postfix) with ESMTP id 973A937B409 for ; Thu, 20 Sep 2001 17:05:06 -0700 (PDT) Received: from development.wgtn.csg.co.nz ([210.86.1.68]) by mta6-rme.xtra.co.nz with SMTP id <20010921000505.BVXP2560251.mta6-rme.xtra.co.nz@development.wgtn.csg.co.nz>; Fri, 21 Sep 2001 12:05:05 +1200 Content-Type: text/plain; charset="iso-8859-1" From: David Preece Reply-To: davep@afterswish.com To: davidc@acns.ab.ca, sridharv@ufl.edu, bright@mu.org Subject: Raw sockets: Stevens shall provide. Date: Fri, 21 Sep 2001 12:05:20 +1200 X-Mailer: KMail [version 1.2] Cc: hackers@freebsd.org MIME-Version: 1.0 Message-Id: <01092112052007.36513@development.wgtn.csg.co.nz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks for your help, as suggested the combination of IP_HDRINCL and reading Stevens seems to have me back on the right path. Part of the confusion was the Linux implementation of IP_HDRINCL appears to need the hardware addresses writing as well, consequently there are lots of examples of this being done in order to forge arp replies etc - not what I needed. Or rather, it was actually. Anyway, the code is now refusing to send packets entirely, which is actually good because it implies a checksum is broken somewhere and that's a bug, not a misunderstanding about the API. Thanks again, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message