Hello, thanks! now I noticed this:
#netstat -ntpl | grep 10031 tcp 0 0 :::10031 :::* LISTEN 679/perl if I "force" to bind an ivp4 IP I do not get the error. So it looks like it's getting a ipv6 configuration from somewhere. On the other hand, If I change from tcp to unix socket I get another "DEFER"! and it is not working either. In cbpolicyd.log I see: Use of uninitialized value $ip in pattern match (m//) at /usr/local/lib/policyd-2.1/awitpt/netip.pm line 73. Use of uninitialized value $ip in pattern match (m//) at /usr/local/lib/policyd-2.1/awitpt/netip.pm line 75. Use of uninitialized value $ip in pattern match (m//) at /usr/local/lib/policyd-2.1/awitpt/netip.pm line 75. [2012/07/09-13:57:23 - 603] [TRACKING] ERROR: Failed to understand PeerAddress: awitpt::netip::new(78): Failed to guess IP address version [2012/07/09-13:57:23 - 603] [CBPOLICYD:603] DEBUG: Error getting session data cat /etc/cluebringer.conf ... # Protocol to use "tcp" or "unix", defaults to "tcp" #proto=tcp proto=unix # IP to listen on, * for all. Blank for unix sockets #host=192.168.66.98 #host=* # Port to run on, in the case of a unix socket it would be the path # eg. 10031 # eg. /var/run/cbpolicyd/policyd.sock #port=10031 port=/tmp/policyd.sock ... Thanks for your support!!! Regards. > Date: Mon, 9 Jul 2012 13:33:50 +0200 > From: [email protected] > To: [email protected] > Subject: Re: [policyd-users] policyd always rejects recipient > > > Ahh, > Manel, maybe this fixes your issue. > > marko > > Am 09.07.2012 12:57, schrieb Robert Anderson: > > On 09/07/2012 12:30, Manel Gimeno Zaragozá wrote: > >> I've created another virtual machine (HOST_B) with exactly the same > >> configuration (postfix, mysql) and it works perfectly. Once I had > >> this > >> one running I've modify the configuration of "HOST_A" to point the > >> BBDD > >> to the new one in "HOST_B" and the problem remains in "HOST_A". So I > >> can > >> conclude that it is not a BBDD issue. > >> > >> On the other hand, postfix has exactly the same configuracion, with > >> any > >> modification. So I can not find where the problem comes from. > > > > I believe the error received is due to netip's handling of an IPv4 > > mapped IPv6 address. eg. ::ffff:127.0.0.1 > > > > I hope to have a patch available for you later today that should > > resolve > > this issue. > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.policyd.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.policyd.org/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
