Date: Sun, 17 Sep 2000 09:43:19 +1200 From: "Dan Langille" <dan@langille.org> To: "Crist J . Clark" <cjclark@reflexnet.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: internal auth and inetd don't seem to like each other Message-ID: <200009162143.JAA16595@ducky.nz.freebsd.org> In-Reply-To: <20000916133407.Y69158@149.211.6.64.reflexcom.com> References: <200009161238.AAA13888@ducky.nz.freebsd.org>; from dan@langille.org on Sun, Sep 17, 2000 at 12:38:40AM %2B1200
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 Sep 2000, at 13:34, Crist J . Clark wrote: > It seems to work fine for me, I think I know why now. > Have you tried running inetd in debug mode, -d? This tells me more. I starte inetd like this: [root@ducky:~] # inetd -d -wW -R 1024 Within the first dozen or so lines of output, I see this: ADD : auth proto=tcp accept=1 max=0 user=root group=(null)class=daemon builtin=0x80501f0 server=internal policy="" It appears that inetd needs to be restarted to get the internal auth to work. A mere HUP won't work. Thanks. > > side note: from what I've seen of other working examples, I don't think > > this will provide a working auth for boxes behind the fw/nat box (on > > which the above was done). > > You are saying you will run this on the NAT box? It should work > fine. Use '-d' or '-g' options for auth. Yes, I will run this on the NAT box. But it doesn't appear to achieve my goals. I was hoping for an auth which would work for IRC clients on internal workstations with access through the firewall. It's not. But perhaps my expectations aren't reasonable. cheers -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ FreshPorts - http://freshports.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009162143.JAA16595>