Andrea Venturoli wrote:
Hello.
I have a setup with two FreeBSD 6.3 domain controllers using samba +
openldap + nss_ldap.
The company might be switching to Active Directory soon (not my
choice, before you ask :-), so I might need to reconfigure the two
FreeBSD boxes to become AD members (with
Hello.
I have a setup with two FreeBSD 6.3 domain controllers using samba +
openldap + nss_ldap.
The company might be switching to Active Directory soon (not my choice,
before you ask :-), so I might need to reconfigure the two FreeBSD boxes
to become AD members (with winbindd, nss, whatever).
Hi
On Fri, Oct 9, 2009 at 6:03 PM, Bernhard Schmidt wrote:
> On Friday 09 October 2009 19:08:39 Lutz Bichler wrote:
>> Hi,
>>
>> does anybody know what happened to the attempts to support Intel WiFi
>> 5100/5300 interfaces in the iwn-driver? Are any patches available which
>> could be used to s
On Fri, Oct 9, 2009 at 5:58 PM, Julian Elischer wrote:
> Jacques Fourie wrote:
>>
>> Hi,
>>
>> I've noticed what I believe to be a bug in ip_output(). The piece of
>> code in question is when the firewall changes the destination address
>> of an outgoing packet and the subsequent re-calculation of
I am out sick today, but I will see what I can find out early next week.
Jack
On Fri, Oct 9, 2009 at 12:03 PM, Julian Elischer wrote:
> Pyun YongHyeon wrote:
>
>> On Fri, Oct 09, 2009 at 11:17:00AM -0700, Jack Vogel wrote:
>>
>>> I am Jack, the network engineer at Intel responsible for all Free
Pyun YongHyeon wrote:
On Fri, Oct 09, 2009 at 11:17:00AM -0700, Jack Vogel wrote:
I am Jack, the network engineer at Intel responsible for all FreeBSD wired
lan drivers.
This is the first I've seen about this. Our understanding was that the
infrastructure needed
to do IPSec was not available for
On Fri, Oct 09, 2009 at 11:17:00AM -0700, Jack Vogel wrote:
> I am Jack, the network engineer at Intel responsible for all FreeBSD wired
> lan drivers.
> This is the first I've seen about this. Our understanding was that the
> infrastructure needed
> to do IPSec was not available for either Linux o
Jack Vogel wrote:
I am Jack, the network engineer at Intel responsible for all FreeBSD wired
lan drivers.
This is the first I've seen about this. Our understanding was that the
infrastructure needed
to do IPSec was not available for either Linux or FreeBSD, can you please
explain things?
If ever
On Friday 09 October 2009 19:08:39 Lutz Bichler wrote:
> Hi,
>
> does anybody know what happened to the attempts to support Intel WiFi
> 5100/5300 interfaces in the iwn-driver? Are any patches available which
> could be used to start working on support for these interfaces?
I'm curious too, as
I am Jack, the network engineer at Intel responsible for all FreeBSD wired
lan drivers.
This is the first I've seen about this. Our understanding was that the
infrastructure needed
to do IPSec was not available for either Linux or FreeBSD, can you please
explain things?
If everything is there exce
Hi,
does anybody know what happened to the attempts to support Intel WiFi 5100/5300
interfaces in the iwn-driver? Are any patches available which could be used to
start working on support for these interfaces?
Lutz
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten u
Hi everyone,
I would like to know if anyone knows the reason why I get a lot of
connections (more than 100) from the same IP in FIN_WAIT_2 state.
Refering to this diagram
(http://www.jxos.org/Projects/TCP/tcpstate.html), the connection enter
in FIN_WAIT_1 when the server closes the connectio
Jacques Fourie wrote:
Hi,
I've noticed what I believe to be a bug in ip_output(). The piece of
code in question is when the firewall changes the destination address
of an outgoing packet and the subsequent re-calculation of the route.
The issue should be clear from the attached diff - basically
Oleg Bulyzhin wrote:
On Wed, Oct 07, 2009 at 03:52:56PM +0500, rihad wrote:
You probably have some special sources of documentation ;-) According to
man ipfw, both "netgraph/ngtee" and "pipe" decide the fate of the packet
unless one_pass=0. Or do you mean sprinkling smart skiptos here and
the
Hi,
I've noticed what I believe to be a bug in ip_output(). The piece of
code in question is when the firewall changes the destination address
of an outgoing packet and the subsequent re-calculation of the route.
The issue should be clear from the attached diff - basically what
happens is that for
On Thu, Oct 08, 2009 at 09:18:23AM -0700, Julian Elischer wrote:
> that seems like a bug to me..
> neither tee should ever terminate a search.
agree. But documented bug is a feature ;) and i'm not sure if we fix this
wouldnt it break POLA?
>
> if you want to terminate it, add a specific rule to d
On Wed, 07 Oct 2009 20:02:21 +0500 rihad wrote:
>Ingo Flaschberger wrote:
>> Hi,
>>
>> can you send me the dmesg ouput from your networkcards when they are
>> detected at booting?
>>
>Hello,
>
>bce0: mem
>0xf400-0xf5ff irq 16 at device 0.0 on pci7
>bce0: Ethernet address: 00:1d:0
17 matches
Mail list logo
