hi,
Paul Querna wrote:
>
> On Tue, 2004-06-22 at 23:55 -0400, Takashi Okumura wrote:
> > hi,
> >
> > please take a look at mod_netnice. it uses netnice, another in-kernel
> > traffic control primitive on the platform. since you can control each
> > socket with netni
On Tue, Jun 22, 2004 at 08:39:48PM -0700, Paul Querna wrote:
> Hello,
> I am looking at methods to rate limit a single socket to a specific
> pipe or rate with FreeBSD. I would like to make an Apache module that
> could do its outgoing rate limit *in* kernel, making the module very
> simple,
Julian Elischer wrote:
> On Tue, 22 Jun 2004, Ian FREISLICH wrote:
> > Andre Oppermann wrote:
> > > Here is the next preview patch for the ipfw to pfil_hooks conversion:
> > >
> > > http://www.nrg4u.com/freebsd/ipfw-pfilhooks-and-more-20040621.diff
> > >
> > > This patch significantly cleans up
Ian FREISLICH wrote:
>
> Julian Elischer wrote:
> > On Tue, 22 Jun 2004, Ian FREISLICH wrote:
> > > Andre Oppermann wrote:
> > > > Here is the next preview patch for the ipfw to pfil_hooks conversion:
> > > >
> > > > http://www.nrg4u.com/freebsd/ipfw-pfilhooks-and-more-20040621.diff
> > > >
> >
Bruce M Simpson:
> Hi all,
>
> Whilst scanning GNATS, I found a number of PRs relating to requests
> for tcp_wrappers functionality and some outright bugfixes. Rather than
> commit these as-is, I think we should push the changes back to Wietse,
> as we maintain tcp_wrappers on a vendor branch.
>
On Wed, Jun 23, 2004 at 03:20:19AM -0400, Takashi Okumura wrote:
> hi,
>
>
> Paul Querna wrote:
> >
> > On Tue, 2004-06-22 at 23:55 -0400, Takashi Okumura wrote:
> > > hi,
> > >
> > > please take a look at mod_netnice. it uses netnice, another in-kernel
> > > traffic control primitive on the pla
On Tue, 22 Jun 2004, Paul Querna wrote:
> I am looking at methods to rate limit a single socket to a
> specific pipe or rate with FreeBSD. I would like to make an Apache
> module that could do its outgoing rate limit *in* kernel, making the
> module very simple, and more accurate by using t
I am having a lot of trouble trying to make the following work (after
some exhaustive googling etc)
Goal: 2 interfaces (em0 and em1) to be "combined" or bonded into one
virtual interface so as to provide both increased throughput and
failover. Both physical ports connected to either the same or di
hi,
Brooks Davis wrote:
>
> I think netnice looks really neat.
>
> Use of /proc would definaly limit the utility of integrating the code.
> We don't enable procfs by default because it's too hard to get procfs
> code right as the list of procfs security advisories demonstr
Hello,
I'm trying to have failover with a couple boxes and they're basically
doing NAT and firewalling. 1 box has a couple fxp and the other a couple
rls. Is this supposed to be a problem for freevrrpd?
Only fxp box actually can use the fail-over ips. The backup box cannot
use them if we start
10 matches
Mail list logo