2 suggestions :)
1. rename the box.
2. either update identd to support masq connections (there are patches and
there are other available ident servers) or remove it. The only thing more
likely to stop connections than no ident, is an ident error return, and most
ISPs that I've dealt with consider NO-USER to be an error condition.
Lourdes
I use oidentd, I have it set to forward ident requests to the linux machines
(also running oidentd) and return user aliases for the Windows machines.
http://www.ojnk.nu/~odin/ (http://199.4.146.19/~odin/ if name fails)
Pim Messelink wrote:
> Feb 28 13:48:18 fockhock in.telnetd[137]: connect from 192.168.0.2
> Feb 28 13:48:24 fockhock login[138]: ROOT LOGIN on `ttyp1'
> from `192.168.0.2'
> Feb 28 13:54:07 fockhock identd[150]: Connection from ns1.casema.net
> Feb 28 13:54:07 fockhock identd[150]: from: 195.96.96.33
> ns1.casema.net ) for: 61076, 25
> Feb 28 13:54:07 fockhock identd[150]: Returned: 61076 , 25 : NO-USER
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
