Aliaksei,
Honestly, I had never heard of a loopback interface being assigned a routable
IP address. I guess this is why CFEngine ignores it when collecting information
about the system. This seems to be hardcoded behavior, don't know how easy it
would be to change.
--Diego
On Sep 3, 2012, at 9:58 AM, Aliaksei Sheshka <sheshka...@gmail.com> wrote:
> Hi list!
>
> I'm trying to setup cfengine on my network and faced unexpected behavior.
> Most of my linux nodes have routable IPs defined under lo interface,
> like 192.168.1.5/32 192.168.78.25/32 and so on,
> but looks like cfengine doesn't define class with the IPs of the
> loopback interface. Is it intended behaviour, if so, why ?
> Then running /var/cfengine/bin/cf-promises -v I'm getting:
> Defined classes = { 64_bit 8_cpus Afternoon Day3 GMT_Hr14 Hr14 Hr14_Q3
> Lcycle_2 Min35 Min35_40 Monday PK_MD5_c7d182a7a3561105b17ce0b7d207c59c
> Q3 September Yr2012 any as6453_net cfengine cfengine01
> cfengine01_as6453_net cfengine_3 cfengine_3_3 cfengine_3_3_5 common
> community_edition compiled_on_linux_gnu debian debian_6 debian_6_0
> have_aptitude linux linux_2_6_32_5_vserver_amd64 linux_x86_64
> linux_x86_64_2_6_32_5_vserver_amd64
> linux_x86_64_2_6_32_5_vserver_amd64__1_SMP_Sun_May_6_06_53_58_UTC_2012
> net verbose_mode x86_64 }
> That can be done about that ? Assigning routable IPs to loopback is a
> relatively common thing in the a) multihomed environments b)
> containerized environments (linux-vserver, FreeBSD jails).
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@cfengine.org
> https://cfengine.org/mailman/listinfo/help-cfengine
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
