Hi,
I apologize if this issue has been discussed earlier. If so, please
point me to relevant information. Anyways, here it goes...
I plan on deploying Puppet to manage several separate nodes, all of
which are accessible directly from the Internet. The nodes are
connected by a VPN (OpenVPN), so th
Thanks for all your suggestions! Restricting access to managed nodes
using iptables occured to me after sending this post (stupid me). I
think that does the trick. If not, I'll try Daniel's approach.
Samuli
On 28 Mag, 06:25, Daniel Pittman wrote:
> sasepp writes:
> >
Hi,
I'm trying to deploy puppetd 0.25.4 (from ports) on two servers
running FreeBSD 8.0-RELEASE and 8.1-RELEASE. The puppetmaster 0.24.5
is running on Debian Lenny. Tcpdump on puppetmaster shows tons of
packets coming in and going out when puppetd is launched.
I've used this command for debuggin
> But clients being newer than the master is not a good thing and should
> be avoided at all costs. Seeing as the debian stable packages are rather
> ancient by now (lots of bugs fixed since), you may want to look for a
> way to upgrade those (i.e., use backport or unstable packages, not use
> pack
