This guide is mainly for a reminder and for those familiar with Eggdrop already. There were some changes in 1.8 as far as linking goes. Mostly due to the addition of SSL and IPv6.
First off, decide which bot will be the “hub” and go to that directory. You will need to make an eggdrop.key and an eggdrop.crt file. To make a self-signed key, run this command:
openssl genrsa -out eggdrop.key 2048
To make the certificate to go with it, run this command:
openssl req -new -key eggdrop.key -x509 -out eggdrop.crt -days 365
Next, open up your config file with your favorite editor and uncomment
set ssl-privatekey and
set ssl-certificate. Also make note of your listen ports, as you will need those for linking. If they aren’t ssl ports, make them ssl ports by adding a + in front. SSL is required for linking.
For the commands below, replace hub/leafname with your hub/leaf bot’s name. Same goes for hub/leafport and hub/leafhost.
Start up the bots, and on the hub bot, do:
.+bot leafname leafhost +leafport
.chgpass leafname makeupsomepassword
The reason for the .chgpass line is to make sure the bots don’t complain about a wrong password from the start.
On the leaf bot, do:
+bot hubname hubhost +hubport
.chgpass hubname usethesamepasswordasabove
You can use another password if you want to, up to you.
On the hub bot, try linking to the leafbot:
If this works, then you can go ahead and add the flags. +h is for hub. +s is for aggressive sharing. +p is for passive sharing. +l is for leaf. On the hub:
.botattr leafname +lp
And on the leaf:
.botattr hubname +hs
And they will now share the user lists and link up automatically.