Date: Fri, 09 Jan 2009 01:08:50 +0000 From: "Bruce M. Simpson" <bms@FreeBSD.org> To: Peter Steele <psteele@maxiscale.com> Cc: freebsd-net@freebsd.org, Adrian Chadd <adrian@freebsd.org>, Peter Grehan <grehan@freebsd.org>, "George V. Neville-Neil" <gnn@FreeBSD.org> Subject: Re: Having problems with limited broadcast Message-ID: <4966A3A2.7030001@FreeBSD.org> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FF9@polaris.maxiscale.com> References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <d763ac660901081411l59120580yb4919a16b451e3ee@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> <49668C71.4090407@FreeBSD.org> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FF9@polaris.maxiscale.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Steele wrote:
>> The folk who point out that link-local addresses could be used, have
>>
> an
>
>> interesting suggestion which might work for you.
>>
>
> It's definitely interesting, but it is very likely that some of our
> customers will want to be able to set their own IP ranges and not be
> limited to 169.254/16. So we need a more generic solution.
Sounds like it's bpf/pcap city for you guys.
A similar bump-in-the-stack to SO_BINDTODEVICE, e.g. let's call it
IP_SENDIF has been on the drawing board, but it needs appropriate
security screening -- the ability to bypass the forwarding tables,
whilst specifying an interface e.g. by index or name, would be desirable
only for certain privileged processes.
BTW: If you guys are already looking at scapy, you may also wish to give
pcs.sourceforge.net a look as an alternative.
It is a Python project which I did some hacking on with George
Neville-Neill who started it. It has BPF/PCAP support out of the box and
has a number of powerful features, including a packet-level expect()
facility, which works in a very similar manner to pexpect (Python expect
for text streams).
I added a scapy-like concatenation syntax ('/' operator) to it as that
makes plugging packet chains together that much easier.
I have the beginnings of an IGMPv3 test suite in my home repo written
using PCS, it uses pcap capture. I imagine a DHCP like protocol could
easily be implemented using PCS too.
cheers
BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4966A3A2.7030001>