Syncing with gdrive about consolepi

[Pack3tL0ss]

Should be resolved now. Let me know if not.
You'll have to run consolepi-upgrade to grab the update.

While attempting to speed things up, I mistakenly introduced an error in the sequence of things (as it relates to the initial creation of the file on Gdrive), I never noticed, as I failed to go back and test with the file not already there (ConsolePi.csv).

I'll keep this open for a bit - let me know if consolepi-upgrade resolves it, and I'll close.

[nintox]

It works now, thanks alot 👍
For the PI'es to find each other and connect over the sync, what is the requirements?
I mean having one PI to show all console connection like illustrated on your picture.

[Pack3tL0ss]

• They need to be reachable (need to be able to ping each other) on the network.
• To use the Gdrive sync they need to have internet access.
• They will discover each other over the local network if they are on the same subnet (with or without Gdrive).

You can use the same credentials.json and token.pickle file for all the Pis, they can use the same creds.

[nintox]

Okei, thats what i tought.
I need them to find each other over the "openvpn" network, should they do it? Or do i have to specify that in one config file?

[Pack3tL0ss]

Yes. Assuming you've configured OpenVPN. Also run consolepi-upgrade after populating the OpenVPN ovpn file, it will place a couple of lines at the end of the config (to trigger cloud sync after VPN connection) Each ConsolePi will then update gdrive once VPN is established. You should see the new entry in the spreadsheet on gdrive (ConsolePi.csv) with the TUN interface IP, as long as they can reach each other (i.e. ping) the remote side will show in the menu. May have to (r)efresh in the menu on the 1st Pi to connect if accessing the menu from that one.

…

On Wed, Sep 18, 2019, 4:26 AM nintox ***@***.***> wrote: Okei, thats what i tought. I need them to find each other over the "openvpn" network, should they do it? Or do i have to specify that in one config file? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#10?email_source=notifications&email_token=ABTGZITQB4SMYZQYXGNWE7DQKHQZXA5CNFSM4IXBOQA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD67H74Q#issuecomment-532578290>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABTGZISRQ34KJX2VM3TJRFDQKHQZXANCNFSM4IXBOQAQ> .