Gerry, good day.
Sun, Dec 28, 2008 at 07:59:57PM -0600, Gerry Weaver wrote:
> I am working on a driver to collect some network statistics using
> pfil. I have set up a bridge and set net.link.bridge.pfil_member=1 via
> sysctl. I have added hooks for incoming and outgoing packets. I also
> put a th
Because that is clearly related to freebsd-net.
Have you lost your mind??
On Sun, 2008-12-28 at 17:14 -0800, Michael Sierchio wrote:
> Hi freebsd-net,
>
> I set up a Facebook profile where I can post my pictures, videos and events
> and I want to add you as a friend so you can see it. First, yo
Hi freebsd-net,
I set up a Facebook profile where I can post my pictures, videos and events and
I want to add you as a friend so you can see it. First, you need to join
Facebook! Once you join, you can also create your own profile.
Thanks,
Michael
To sign up for Facebook, follow the link below
Hello All,
I am working on a driver to collect some network statistics using pfil. I have
set up
a bridge and set net.link.bridge.pfil_member=1 via sysctl. I have added hooks
for
incoming and outgoing packets. I also put a third adapter into the system for
dev/managment purposes. My hooks are
On Sun, 28 Dec 2008, Bjoern A. Zeeb wrote:
Hi,
On Sun, 28 Dec 2008, Kip Macy wrote:
Hi,
What do you think wrt to adding the (possibly optional) int *error and
returning the errno rather than a (void *)-1? If you'd be ok, I'd can
prepare the patch. I'd rather break the API now than in a few
On Sun, 28 Dec 2008, Kip Macy wrote:
Hi,
What do you think wrt to adding the (possibly optional) int *error and
returning the errno rather than a (void *)-1? If you'd be ok, I'd can
prepare the patch. I'd rather break the API now than in a few months.
I would greatly prefer having a dedicate
> What do you think wrt to adding the (possibly optional) int *error and
> returning the errno rather than a (void *)-1? If you'd be ok, I'd can
> prepare the patch. I'd rather break the API now than in a few months.
I would greatly prefer having a dedicated new function that calls in
to it. Ther
Hi,
Cc:ing freebsd-net as I came across the (void *)-1 "hack" 1.5 weeks
ago while debugging some problems with others and they might be
interested as well.
I was sure I hadn't seen that hack in patches posted before.
I spent some time today and looked a bit more into it (also comitted
the LLE_I
Thank you.
The option "-iface" works as expected.
Also solved the problem when the squid 3.0.STABLE10 could not connect to
the real ip, which ISP issued on pppoe.
Now squid normally sees routes to these IP.
Li, Qing writes:
Hi,
I have committed a patch for this problem. Please sync-up to
On Dec 24, 2008, at 2:43 PM, Julian Elischer wrote:
Luigi Rizzo wrote:
On Wed, Dec 24, 2008 at 11:57:42AM +0100, Paolo Pisati wrote:
Julian Elischer wrote:
OR
ngctl mkpeer em0: echo lower echo
hm no this would leave the source and destination headers in
hte same order.. they need to
On Saturday 27 December 2008 21:21:25 Qing Li wrote:
> Right now I am also a bit leaning towards reintroducing
> the RTF_LLINFO flag bit. This is mainly due to the recent
> discovery of the "route" command issued with the
> "-iface/-interface" option, which conflicts with the
> way how "arp" and "n
Hi all,
The first chunk of work from the FreeBSD Foundation sponsored "Improving
the FreeBSD TCP Implementation" project [1] is ready for some public
review and testing. Being my first project related email, I'll point out
to anyone interested that you can track the overall project via [2,3].
12 matches
Mail list logo
