You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bootstraping mechanisms are not finished yet. Once it is done, bots will be able to connect with each others using several techniques (a local list of well-kown peers, a local list of peers seen lately, a dga-like fallback component and the already existing GetPeerList and PeerList system messages exchange).
Connect bots for testing
I the meanwhile, if you want to play with it, you can open 2 consoles (cmd windows) and do the following:
In one cmd window type:
bin\Debug> Vinchuca p33332
where p means Port and 33332 is the port number
In the other cmd window type:
bin\Debug> Vinchuca p33333
Now we have two bots (in controller mode) running and listening for connections. Next, in the latest console where the bot listens in 33333 type: add-node 127.0.0.1:33332 <ENTER>. After this you should see they communicate one to the other. Just to verify they both are conected, type: debug get-peer-list and this will display the list of peers connected.
About the REPL
The REPL console has commands history using <Up-Arrow> and <Down-Arrow>. Also, it has word completions with <Tab>. Try it. At last, the help command provides the list of available commands. You can get command specific help typing ´help 'thecommand'´, for example: help ddos-start
@lontivero the backdoor does not display properly, just a note.
when you use the backdoor command, it does not say connected or anything. The packets received that show the info you asked for arent displaying on the main.
Testing this on localhost, how do I add a bot?
I tried listening on 33332 in a different cmd window, but it wouldn't connect
The text was updated successfully, but these errors were encountered: