FYI - We are running CentOS 6.5 with Firebird 2.5.4 SuperClassic and we are correctly getting the IP addresses in the monitoring tables.
-steve On Tue, Jun 9, 2015 at 3:56 AM, Marianne Castel - Titelive [email protected] [firebird-support] <[email protected]> wrote: > > > Hello , > > > > So Dmitry suggested it , we have disabled IPV6 on our server CentOS 7 > (Firebird 2.5.4 Classic server (I forgot to mention it in my first mail)). > > By following the centos FAQ : > http://wiki.centos.org/FAQ/CentOS7#head-8984faf811faccca74c7bcdd74de7467f2fcd8ee > > Rebooting the server. > > But even after this modification the mon$remote_address is still giving > 0.0.0.0 > > > > Any ideas are welcome. > > > > Marianne > > > > *De :* [email protected] [mailto: > [email protected]] > *Envoyé :* lundi 8 juin 2015 12:47 > *À :* [email protected] > *Objet :* [firebird-support] Re: Firebird 2.5.4 - CentOS - > mon$remote_address 0.0.0.0 > > > > > > 08.06.2015 10:02, Marianne Castel wrote: > > > > We were working with Firebird 2.5.2 on Debian . At that time, in the > > monitoring table MON$ATTACHEMENTS I could see the IP address of the > > client connected to a database. > > > > Now our administrators have decided to work with CentOS and the last > > available packages thus Firebird 2.5.4, and now in the databases on > > that server in the table MON$ATTACHEMENTS table the field > > mon$remote_address always contains : 0.0.0.0 > > > > May be that the server is different too (network connection?) … > > > > Any idea why the IP address is no more reported ? How could we have the > > IP address again in the monitoring table ? > > Interesting. One possible explanation can be found here: > > > http://stackoverflow.com/questions/17220006/in-what-conditions-getpeername-returns-ipport-0-0-0-00 > > Firebird 2.x does not support IPv6 and always listens on a AF_INET (i.e. > v4) socket, but maybe it could be related somehow. Have you tried to > disable IPv6 on the new server box? > > Dmitry > > >
