Configure all the gyrids

[TomNaessens]

Make sure everything works; try to put them in a circle

Label them from 101 to 107 (or 108?) and give them a corresponding ip adress (x.y.z.101 eg)

[TomNaessens]

OK means: installed, setup.sh run but no bridging network has been configured
FULLY OK means: OK + bridge set up + new number

• 108: FULLY OK, is now 105
• 109: FULLY OK, is now 106
• 110: FULLY OK, is now 104
• 121: FULLY OK, is now 101
• 102: FULLY OK, is now 102
• 113: FULLY OK, is now 103
• 330: FULLY OK, is now 107. actually: should be fine (Has a sticker: Valt uit?) but noticed no problems here

[TomNaessens]

Everything has network ... Let's try to complete the loop now.

[TomNaessens]

Yesh, it works. The loop is there, ports seem to do something.

[Procrat]

Reopening this for 2016.

[ninewise]

Note that we should be able to flash all gyrids cards with the device dump we've taken and used last year.

[Procrat]

Note for next year: to connect with the serial port, you can use one of these programs with baud rate 24000, 8 data bits, no parity bit and 1 stopbit.

[mivdnber]

Are you sure about that? I always connect at 38400 baud. Easiest is screen /dev/<PORT> 38400.

[TomNaessens]

2016:

All Connecting to: 10.1.2.178:2583 (configure in /etc/gyrid/gyrid.conf)
Configured with ssh keys of @silox @Procrat and @Iepoev (all on root account)

101: is sending data to CVC
102: should be ok (not configured for cvc yet, because of lack of adapter :P)
103: is sending data to CVC
104: is sending data to CVC
105: is sending data to CVC
112: is sending data to CVC
113: is sending data to CVC

[TomNaessens]

Current status: gyrids should be configured correctly and are all booting.
Next todo: check if they actually connect with CVC and send data

[TomNaessens]

Fixed the /usr/share/gyrid/network_middleware to s/caching/cache/ on line 675 or something. NOT DONE FOR 102 YET!!!

[Iepoev]

finished 102 config

[Iepoev]

on the topic of stp:

the problem was that the gyrids all have the same bridge priority id (because we are just copypasting the config/interfaces file). However, the id in this file is/was lower than the default bridge priority id of the cisco switch. This resulted in all of the gyrids getting into an ex aequo when electing the root. The solution was to lower the bridge priority id of the switch to 0.

PR #136 resolves this by increasing the bridge priority id of the config/interfaces to the maximum value

[becousae]

Reopen this for 2017.

[Iepoev]

all gyrids have been labeled and have been assigned a correct hostname + ip address
they still need to be patched
#114 (comment)

and hwclock -w has also not been run

[ninewise]

2017 edition is over. Also kindly open a new issue (with a link here) next year, this issue keeps showing up in my TODO.