Demonstration Guardian Program

From RFID Guardian

• The Linux PC at the VU that is connected to the Guardian prototypes has a checkout of a stable version of the Guardian software. It is: MRG = /home/rutger/projects/rfid-guardian/svn/mrg-demo. Preferably use this to do demonstrations. This PC usually has a minicom running in the lower left desktop, in the left-hand upper window.

• If there is no running minicom there, open a terminal window that listens to the serial port that is connected to the Guardian. Use hyperterm under Windows, use minicom -o under Linux. Settings: 115200 8N1.

The running program prints to/reads from this terminal. If the Triton is in its reset state, it will show the RedBoot prompt in the terminal (type <Enter> to check this):

RedBoot>

• The program mrg_rfid_guardian_main in ~MRG/test/guardian-main is used for Guardian demonstrations. A wrapper script ('spoof') is provided in that directory that builds the program (under the assumption that the necessary libraries already exist), resets the Triton, resets the Ethernet connection to the Triton, and uploads the program:

$ ./spoof

The program is started by typing 'c' or 'continue' to the gdb prompt:

(gdb) continue

The serial port terminal program will show lots of startup prints, then present the user with a User Interface prompt:

UI>

Alternatively, the BlueTooth interface can be connected. The Guardian listens to both User Interface channels.

• exit gdb by typing ^C^C^D

The Guardian program can be stopped by hand (using its reset relay or its reset button), or it can be reset automatically from a following run of ./spoof.

• If a reset relay is connected to the Guardian's reset button, it can be controlled from the PC:

$ ~MRG/bin/guardian-reset

• At startup, the Guardian currently has no ACL loaded. Spoofing is enabled by default, logging is disabled. If an RFID query is detected in this stage, the Guardian will notify the user that no ACL is loaded in the serial port terminal window. Printing this message may cause the spoof response to be late, so it is missed by the reader.

• Spoofing can be controlled from the UI:

UI> spoof enable

UI> spoof disable

This should lead to different behaviour in the Reader's inventory window.

• Currently, the Flash file system contains the following ACL directories:
  • /acl/allow Allows all access
  • /acl/ti-white Protects the white TI tag
  • /acl/ti-transparent Protects some transparent TI tags

The rules, tag definitions, and reader/role definitions can be viewed:

UI> cat /acl/allow/example.acl

shows the rule file for /acl/allow, etc. Directories can be browsed by first cd-ing to them, then typing

UI> ls

An ACL is selected and activated by the acl dir <directory> command, e.g.:

UI> acl dir /acl/allow

Ignore the error message in the serial line terminal about a diff for example.acl.

• Recommendations for a successful demo:
  • Choose /acl/ti-white for the protection demo. It hides just one tag.