Bizarre. I use ACLs in my kernel daily, and I use nmap almost daily,
and haven't seen this. If you re-add ACLs with a fresh kernel build,
does the problem come back? Could you look at ktraces of nmap with and
without ACLs and see what causes it? Do you have ACLs enabled on any
file
Alright, it had nothing to do with ACL's. Unknown to me, someone got on
that machine and enabled the firewall, and added rules. Those rules were
causing the problem (I'm not sure why he added a firewall on a machine
already behind one on a 192.168.0.0/24 network). Anyway, sorry for
wasting
Bizarre. I use ACLs in my kernel daily, and I use nmap almost daily,
and haven't seen this. If you re-add ACLs with a fresh kernel build,
does the problem come back? Could you look at ktraces of nmap with and
without ACLs and see what causes it? Do you have ACLs enabled on any
file
Might devfs propagate ACL characteristics via /dev nodes into
applications? Otherwise, the symptom you described would have made me
point to the IP firewall first.
My machine that was showing the problem didn't have a firewall enabled.
I'll still mess with it some more to see what I can come
On Fri, Aug 29, 2003 at 02:31:56PM -0400, Kenneth Culver wrote:
Did the same thing, portupgrade -f nmap, and then ran it with the same
flags, and I'm still getting the same problem. It's doing this on all 3 of
my FreeBSD-CURRENT machines as well.
Ken
Are you running a packet filter of some
On Fri, 29 Aug 2003, Kenneth Culver wrote:
Bizarre. I use ACLs in my kernel daily, and I use nmap almost daily,
and haven't seen this. If you re-add ACLs with a fresh kernel build,
does the problem come back? Could you look at ktraces of nmap with and
without ACLs and see what causes
On Fri, 29 Aug 2003, Kenneth Culver wrote:
Might devfs propagate ACL characteristics via /dev nodes into
applications? Otherwise, the symptom you described would have made me
point to the IP firewall first.
My machine that was showing the problem didn't have a firewall enabled.
I'll
I just built a fresh nmap on my -current box and it appears to work fine
for me, as did the older nmap. So I guess that leaves me firmly in the
unable to reproduce camp. I have noticed that, on my wi0 boxes, I
tend to get a fair number of ENOBUFS errors when nmaping, but that
appears to be
I think I missed the message that this is a response to, but here's an
answer to the question: UFS_ACL controls only the introduction of ACL
code into UFS1 and UFS2 file systems, and enables conditional use of
ACLs code if the ACLs flag is set on a file system. If the ACLs flag is
not set on
Kenneth Culver [EMAIL PROTECTED] wrote:
Is anyone else seeing these problems? Is anyone working
on fixes?
Ken
I just ran portupgrade -f nmap on this box:
[EMAIL PROTECTED] root]# uname -a
FreeBSD tao.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Aug 24 13:35:21
BST 2003 [EMAIL
[EMAIL PROTECTED] root]# uname -a
FreeBSD tao.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Aug 24 13:35:21
BST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TAO i386
[EMAIL PROTECTED] root]# gcc -v
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model:
Just for more info, when was the last time you updated your /etc? on my
4th -CURRENT machine, with the same compiler etc... I havn't updated my
/etc/ since June 1, and that machine works, the other 3 have been updated
very recently, like within the last few weeks, and they're all broken. So
I
Kenneth Culver [EMAIL PROTECTED] wrote:
Just for more info, when was the last time you updated your /etc?
Every time I do a buildworld I run mergemaster and go through every diff. So
the last time would be august the 24th. From what I remember there have been a
few changes to network related rc
Just for more info, when was the last time you updated your /etc? on my
4th -CURRENT machine, with the same compiler etc... I havn't updated my
/etc/ since June 1, and that machine works, the other 3 have been updated
very recently, like within the last few weeks, and they're all broken. So
I
On Fri, 29 Aug 2003, Kenneth Culver wrote:
Just for more info, when was the last time you updated your /etc? on my
4th -CURRENT machine, with the same compiler etc... I havn't updated my
/etc/ since June 1, and that machine works, the other 3 have been updated
very recently, like within
Kenneth Culver [EMAIL PROTECTED] writes:
Just for more info, when was the last time you updated your /etc? on my
4th -CURRENT machine, with the same compiler etc... I havn't updated my
/etc/ since June 1, and that machine works, the other 3 have been updated
very recently, like within the
16 matches
Mail list logo
