In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>> KM> A patch from Tatsuo Sekine <[EMAIL PROTECTED]> fixed this
>> KM> bug. Kondara's newer kernel package includes this patch.
>> KM>
>> KM> I checked Kondara with 2.4.0test which I compiled, and I can see
>> KM> same
I'm playing with the idea of adding an ldap service/daemon to my debian
machine. But before running one, I wanted to get a good idea of what
the general opinion of ldap servers is as far as security is concerned. I
also
was wondering if anyone had any opinions on which one I should use?
The only o
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>> KM> A patch from Tatsuo Sekine <[EMAIL PROTECTED]> fixed this
>> KM> bug. Kondara's newer kernel package includes this patch.
>> KM>
>> KM> I checked Kondara with 2.4.0test which I compiled, and I can see
>> KM> same
I'm playing with the idea of adding an ldap service/daemon to my debian
machine. But before running one, I wanted to get a good idea of what
the general opinion of ldap servers is as far as security is concerned. I
also
was wondering if anyone had any opinions on which one I should use?
The only
Am 16.3.2001, 20:32 (-0500) schrieb S.Salman Ahmed:
>
> Isn't ifconfig supposed to report if a network interface is in
> Promiscuous mode ? I thought it was.
Hi,
I have the same behaviour on my machine. ifconfig doesn't show the
PROMISC-mode of eth0. Whem I'm using 'iproute' instead of ifconfig,
Am 16.3.2001, 20:32 (-0500) schrieb S.Salman Ahmed:
>
> Isn't ifconfig supposed to report if a network interface is in
> Promiscuous mode ? I thought it was.
Hi,
I have the same behaviour on my machine. ifconfig doesn't show the
PROMISC-mode of eth0. Whem I'm using 'iproute' instead of ifconfig
FYI, I experienced similar bug with Kondara, the japanese
distribution (http://www.kondara.org/) uses 2.2.x kernel.
In that case, IPv6-patch changed libpcap's behavior about
promiscuous mode to incompatible with kernel.
A patch from Tatsuo Sekine <[EMAIL PROTECTED]> fixed
this bug. Kondara's newer
Check out
http://members.nbci.com/dsinet/network-sniffers/interface-promiscuity-obscurity.txt
The only other thing I can think of is, something (or someone) is resetting
interface flags (not even sure if that's still possible, the article's from
'98),
or there's some subtle bug in the nic's drive
8 matches
Mail list logo