From: kstailey@yahoo.com (Kenneth Stailey)
Subject: [TUHS] Re: SIMH compilation problems
Date: Wed, 3 Sep 2003 18:46:24 -0700 (PDT) [thread overview]
Message-ID: <20030904014624.45815.qmail@web10002.mail.yahoo.com> (raw)
In-Reply-To: <slrnblcaec.qgd.mirian@trantor.cosmic.com>
--- list-tuhs at cosmic.com wrote:
> On Wed, 3 Sep 2003 14:39:28 +0200 (CEST), Rico Pajarola <rp at servium.ch>
> wrote:
> >
> >on FreeBSD you can't send packets directly over bpf (at least not
> >the same way you can on Net-/OpenBSD).
>
> FreeBSD certainly does let you send packets over bpf. If you open the
> device (e.g. /dev/bpf0) for both reading and writing, you can write()
> a buffer to the device, and the contents of that buffer will be sent
> verbatim from that device. I do this all the time for protocol
> testing.
It's actually the pcap library not the bpf driver that can't write in FreeBSD
but can in NetBSD.
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libpcap/pcap-bpf.c
versus:
http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/libpcap/pcap-bpf.c
http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libpcap/Attic/pcap-bpf.c
> I'm not running NetBSD or OpenBSD currently, so perhaps they support a
> richer interface than FreeBSD does, but the essentials are indeed
> there.
>
> --Mirian
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
prev parent reply other threads:[~2003-09-04 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030903020020.5179B1F98@minnie.tuhs.org>
2003-09-03 12:39 ` Rico Pajarola
2003-09-03 17:50 ` list-tuhs
2003-09-04 1:46 ` Kenneth Stailey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030904014624.45815.qmail@web10002.mail.yahoo.com \
--to=kstailey@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).