vanhu writes:
'Lut Yvan,
> Another way to have this feature is to implement what we call "NAT
> before VPN": you can configure your kernel (or do it for specific NAT
> rules if you want to do a more flexible implementation) to do NAT
> process before doing IPsec stuff.
I've used it last week on
I'm so happy today: finally running a "ifp->if_snd.ifq_drv_maxlen =
4096;" and HZ=4000 kernel with 4100+ online users @500+ mbps, and, most
importantly, with absolutely 0 drops since boot time! ;-) Even if drops
do come in, I'll know where to look first. I'd like to express my
gratitude to Robe
On Tue, 20 Oct 2009, Eric Masson wrote:
Good evening,
vanhu writes:
'Lut Yvan,
Another way to have this feature is to implement what we call "NAT
before VPN": you can configure your kernel (or do it for specific NAT
rules if you want to do a more flexible implementation) to do NAT
process b
open:
* Test reports welcome, especially with 4965, 5150, 5300 and 5350.
At this point, if no issue come up, the driver has the same functionality as
the in tree one.
http://techwires.net/~bschmidt/patches/freebsd/iwn/sys/
or
http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn-20091020.
On Tue, Oct 20, 2009 at 4:47 PM, Bernhard Schmidt
wrote:
> On Sunday 18 October 2009 16:27:37 Bernhard Schmidt wrote:
>> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
>> > .. anyways, I'll post updates on sunday.
>>
>> Here we go.
>
> Update:
> * All reported issues should now be f
On Wednesday 21 October 2009 01:11:34 David Horn wrote:
> On Tue, Oct 20, 2009 at 4:47 PM, Bernhard Schmidt
>
> wrote:
> > On Sunday 18 October 2009 16:27:37 Bernhard Schmidt wrote:
> >> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
> >> > .. anyways, I'll post updates on sunday.
