path: root/openbsc/src/vty_interface_layer3.c
diff options
authorSylvain Munaut <tnt@246tNt.com>2010-06-09 13:03:39 +0200
committerHarald Welte <laforge@gnumonks.org>2010-06-14 20:43:50 +0200
commitc614a6a199b1b1ce4ebfe26ca427370488fe8c38 (patch)
tree6419f6ed8574e8247dd9232e432271a3a3c258dd /openbsc/src/vty_interface_layer3.c
parentb48216f9d1b15fe3e10cac5286a4e4cacc3d9791 (diff)
db: Rename AuthTuples to AuthLastTuples
Ultimately, we'll need to store both the last used tuple by a subscriber and a list of known tuples (for unknown Ki). What's currently implemented for AuthTuples is the former behavior, so reflect that. The second use case will be added as a separate table with separate accessors later on. Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
Diffstat (limited to 'openbsc/src/vty_interface_layer3.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/openbsc/src/vty_interface_layer3.c b/openbsc/src/vty_interface_layer3.c
index 807e165f..0b6da042 100644
--- a/openbsc/src/vty_interface_layer3.c
+++ b/openbsc/src/vty_interface_layer3.c
@@ -100,7 +100,7 @@ static void subscr_dump_full_vty(struct vty *vty, struct gsm_subscriber *subscr)
- rc = get_authtuple_by_subscr(&atuple, subscr);
+ rc = get_lastauthtuple_by_subscr(&atuple, subscr);
if (!rc) {
vty_out(vty, " A3A8 last tuple (used %d times):%s",
atuple.use_count, VTY_NEWLINE);