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
{{ message }}
This repository has been archived by the owner on Jun 24, 2021. It is now read-only.
I just found out that when you setup the hyperglass-agent certificates they are not working until 2hrs after the inital setup if you have the CEST timezone configured.
I'f I check the generated cert it looks like this:
root@lg:/etc/hyperglass# openssl x509 -in certs/c02.fra.de.as49697.net.pem -text -noout
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
3c:01:bd:6d:b3:9e:79:c7:87:f4:f8:5d:76:cf:c3:a5:18:bd:1b:3c
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN = c02.fra.de.as49697.net, O = hyperglass
Validity
Not Before: Oct 7 13:01:53 2020 GMT
Not After : Oct 7 13:01:53 2022 GMT
But 13:01:53 2020 GMT means 15:01:53 CEST and currently it's only 13:01:53 CEST :D
The text was updated successfully, but these errors were encountered:
Starting in hyperglass v1.0.0-beta.76, I've started deprecating hyperglass-agent. Moving forward, FRR & BIRD can be interacted with in the same manner as any other device, i.e. via SSH. See here for details/caveats). Everything will still work as-is for now, but I'd encourage you to try moving to frr_ssh/bird_ssh as the nos (and of course, let me know of any problems via a new hyperglass issue).
Hey,
I just found out that when you setup the hyperglass-agent certificates they are not working until 2hrs after the inital setup if you have the CEST timezone configured.
I'f I check the generated cert it looks like this:
But 13:01:53 2020 GMT means 15:01:53 CEST and currently it's only 13:01:53 CEST :D
The text was updated successfully, but these errors were encountered: