Quote from: rbrunner7 on August 02, 2017, 08:19:11 PM

Quote from: clintar2 on August 01, 2017, 11:37:41 PM

Quote from: rbrunner7 on August 01, 2017, 07:55:12 AM

I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

...

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

...

Or still something not quite right with my new node?

Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now.

Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend.

But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ...

By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me.

No, here is fine.