./build/remote <ip>

[gobengo]

You can now provision remote linux hosts over SSH using ./build/bin/remote <user>@<ip>

exit_node_ip=165.227.241.194
./build/remote root@$exit_node_ip
# will provision the exitnode on that host, then reboot it and wait for it to come back

I tested this script on Digital Ocean: Ubuntu 16.04, 17.10

I have not tested an exitnode made with this script with a home node, and may not have a private internet connection to do so for a while.

Progress on testing:

• - I will make a new droplet and provision it using this PR. Update: It is 159.89.220.229, which was provisioned with commit 259ecee
• - Someone should test it with their home node. This can go in faster if someone else can test it, as I am on the road without in and our of hotels and stuff where I don't have a predictable internet connection to connect my homenode to.

[jhpoelen]

@bennlich would you be up for testing / merging this one?

[bennlich]

Yep.

[gobengo]

Yaaaaaaaay thanks.

…

On Mon, Mar 12, 2018, 11:10 PM Benny Lichtner ***@***.***> wrote: Yep. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKfBnim2CCfSvO6FumdzxhxuOp8p2fSks5tdziogaJpZM4SmCsR> .

[bennlich]

@gobengo no dice :-( The client tries to connect, but to no avail:

Tue Mar 13 00:39:34 2018 daemon.info td-client: Performing broker selection...
Tue Mar 13 00:39:55 2018 daemon.err td-client: No suitable brokers found.
Tue Mar 13 00:39:55 2018 daemon.info td-client: Performing broker selection...
Tue Mar 13 00:40:16 2018 daemon.err td-client: No suitable brokers found.

This is with the following /etc/config/tunneldigger:

config broker 'main'
       list address '159.89.220.229:8942'
        ...

If you wind up with time to try yourself, the steps are:

1. edit /etc/config/tunneldigger to use the ip of your exit node
2. /etc/init.d/tunneldigger restart
3. look at tunneldigger client logs: tail /var/log/messages | grep td-client

Probably hard to debug this further w/o being able to look at logs on the broker side.

[gobengo]

@bennlich Thanks for testing! And especially for the steps! Haven't done home node stuff for a few weeks so it was feeling intractable, but this will be invaluable when I next have a router to hook into. I will follow them and look at broker logs for suspicious stuff.

[bennlich]

Unfortunately I think we need to fix #9 before you'll be able to see any logs :-( Or you could run the broker manually and look at stdout.

[bennlich]

@gobengo logging is fixed in master by starting tunneldigger w/ systemd instead of init. To view logs:

sudo journalctl -u tunneldigger