![]() ![]() ![]() How? As far as I know there are only 2 ways to change it: (1) editing settings.json, and sending a HUP signal so the daemon re-reads the configuration file (I'm not sure if the daemon will try to bind to the new address) (2) using the -r (or -rpc-bind-address) parameter.but you already said that there is nothing wrong there Who's doing this changes? I doubt it is an exploit aimed at the daemon (a RPC command - are you using any 3rd party software to monitor/control the daemon?), more likely is something in the start-up script, or the options used by the script.Looking at the log would be interesting, I would expect an error logged about not being able to bind to that address then the daemon started with that "rpc-bind-address". Does this do anything? No if the daemon was already running, bind address only is used at the start, and binding to an nonexistent (in the local system's network interfaces) address shouldn't work anyway (unless its a broadcast, or multicast address) A strange address appears in settings.json's "rpc-bind-address". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |