id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,mlocked 13593,Python: Use 'MasterServerName' instead of 'MasterServerIP',rcrdnalor,rcrdnalor,"Ticket #13024 : Networking Improvements introduced new settings for '!MasterServerName', '!BackendServerAddr' and '!BackendServerPort' and deprecates '!MasterServerIP' and '!MasterServerPort'. '!BackendServerAddr' can be an IPv4 or IPv6 in the classical ""dot/colon"" notation, or is provided in it's canonical form. {{{ From settings table: | value | data | hostname | +-------------------+---------------------+----------+ | BackendServerAddr | 192.168.1.100 | myserver | | BackendServerPort | 6543 | myserver | | MasterServerName | myserver | NULL | +-------------------+---------------------+----------+ or | value | data | hostname | +-------------------+---------------------+----------+ | BackendServerAddr | server.example.com | myserver | | BackendServerPort | 6543 | myserver | | MasterServerName | myserver | NULL | +-------------------+---------------------+----------+ }}} Thanks to Ross Boylan for pointing this out in the user mailing list and to and to Peter Bennett for additional explanation. The workaround until this ticket gets fixed is to use only IP addresses in the "".dot"" notation and take care, that the ""!MasterServerIP"" is identical to the ""!BackendServerAddr"". Attached patch uses these new settings for the Python Bindings instead of the deprecated ones.",Patch - Bug Fix,closed,minor,31.1,Bindings - Python,Master Head,medium,fixed,,,0