Date: Thu, 30 Jun 2005 09:58:46 +0300 From: Abu Khaled <khaled.abu@gmail.com> To: Odhiambo Washington <wash@wananchi.com>, freebsd-questions@freebsd.org Subject: Re: Device access - /dev/ipnat Message-ID: <a64c109e05062923581fc4831b@mail.gmail.com> In-Reply-To: <20050629182231.GD53518@ns2.wananchi.com> References: <20050629182231.GD53518@ns2.wananchi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/29/05, Odhiambo Washington <wash@wananchi.com> wrote: > Hello FreeBSD lovers, >=20 > In the current FreeBSD ports, squid-2.5STABLE10 has a patch that allows > it to run without dying even though it does not have access to > /dev/ipnat. >=20 > This access is important where squid is running in a transparent proxy > setup. >=20 > I am running several FreeBSD 5.x boxes with squid in transparent proxy > mode, so this problem is a big one for me. >=20 > The patch seems to be a workaround, but I'd really like to give squid > access to this device anyway. >=20 > My thinking was that I can solve the problem of access to /dev/ipnat > using /etc/devfs.conf. However, my reading of the comments in this file > does not give me any clear method of achieving what I want. >=20 > Am I right in my thinking that /dev/ipnat device is created on the fly > in FreeBSD 5.x? As such I cannot change the permissions on it, yes? >=20 > How do I solve my problem, if anyone can advise me? It will server as > my first lesson with devices in 5.x. >=20 >=20 > Thanks in advance. >=20 >=20 > -Wash >=20 execute the following to enable squid to access /dev/ipnat # chgrp squid /dev/ipnat # chmod g+rw /dev/ipnat Add them to /etc/rc.local to execute them on boot/restart chgrp squid /dev/ipnat chmod g+rw /dev/ipnat --=20 Kind regards Abu Khaled
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a64c109e05062923581fc4831b>