On Fri, 30 Mar 2007, Julian Elischer wrote:
I have been looking at the IPFW code recently, especially with respect to
locking. There are some things that could be done to improve IPFW's
behaviour when processing packets, but some of these take a toll (there is
always a toll) on the 'updating'
Ilya Bobir wrote:
Julian Elischer wrote:
This is pretty close.. I know I've mentioned this to people several
times over
the last year or so. the trick is to try do it in a way that the
average packet
doesn't need to do any locks to get in and the updater does more work.
if you are willing to a
Da Rock wrote:
So I could use some guidance as to what I can do to rectifiy this
problem. I have 2 goals:
1. setup iwi to start on boot, and attach to my ap whenever its in range.
2. make sure iwi stays connected without manually monitoring it.
3. prioritise my routes via the rl0 and iwi if's
Call me dumb, but I'm having some strange issues trying to get my laptop to
communicate properly with my network.
First the iwi if works on boot, but then drops out. I have a wpa_supplicant
working, but after a while it drops off and loses the connection on me. The
only way for me to get it goin
On Sat, Mar 31, 2007 at 04:42:14PM +0300, Niki Denev wrote:
> Andrew Thompson wrote:
> > Hi,
> >
> >
> > Here is a patch to add OpenBSD's trunk(4) interface, and also includes
> > LACP support which came from agr(4) on NetBSD. Im interested in anyone
> > who wants to test this and in particular
