Hmm, looks cool.
Here're the parts that exist in our setup:
1) The Door-controller <http://dc.osaa.dk> one on each door, talks to
a keypad and an RFID reader.
2) The controller server which runs on a local Linux box and talks UDP
to the door-controllers and https to the user database.
3) The user database which runs on a proper server hosted in a real
datacenter (ours is in an entirely different country)
The door controllers talk UDP to the controller server, it's a very
compact protocol to allow the 8-bit controllers to handle it
efficiently.
Each door controller has a fixed AES key and a fixed IP address, both
of which are set at compile time.
We currently mirror all RFID+PIN keys in EEPROM on the door
controllers, so they are completely stand alone and will only need
power to be able to let people in, we are planning to add an on-line
mode to be used for members who do not get 24x7 access.
At the moment the controller server consists of a logger which decodes
the UDP packages with log info from the door controllers and logs it a
plain text file and a tool which syncs key transactions from the user
database into the door controllers.
At some point I expect to code an on-line controller server which will
talk UDP to the door controllers and REST over https to the user
database system, so we can manage the locks directly from the user
database.
--
Flemming Frandsen - YAPH - http://dren.dk/