Class Setup & Enrollment

Once your RemoteRF server and SDRs are running, preparing a specific course offering takes only a few minutes from the server console (serverrf -s). With a course user group and enrollment codes configured, the platform runs autonomously throughout the academic term with little to no instructor intervention.

About User Groups & Enrollment Codes

RemoteRF uses user groups and enrollment codes to scope access per class without manually creating or editing individual student accounts:

  • User Groups: A user group defines the permissions and privileges of its members, including which SDR device IDs members can see and reserve, the maximum duration of each reservation, the maximum number of concurrent reservations a student may hold, and an optional expiration lifetime.
  • Enrollment Codes: An enrollment code is a token that students enter when enrolling via remoterf -r or remoterf --login. Registering or enrolling with an enrollment code automatically places the student’s account into the associated user group.

Multiple Courses on One Server: A single RemoteRF server can support multiple classes or research groups simultaneously. Simply create a separate user group for each course offering (e.g., ee123_f26 and ee230_f26) with its own device whitelist and reservation policy.

Step 1: Creating a User Group

First, inspect the connected radios in your running server@remoterf: shell so you know which device IDs to assign to your class:

devices list

Next, create a new user group for your course offering:

groups create

You will be prompted for the following settings:

  • Group name: Use a clear course and term identifier such as ee123_f26 (students see this group name when checking their permissions).
  • Devices whitelist: Comma-separated device IDs that members of this class may access (e.g., 0,1,2,3,4,5,6,7). You can optionally leave one SDR off the student whitelist to reserve it for instructor/TA testing.
  • Max reservation time: Maximum duration of a single reservation in seconds (default 1800 = 30 minutes).
  • Max concurrent reservations: Maximum concurrent reservations a student can hold at once (default 3).
  • Group lifetime: Group lifetime in seconds (0 means never expires, or set to the length of the academic term).
  • Max days ahead a reservation may start: Booking horizon in days (default 7 days; 0 means no limit).
  • Reachable via Global / Public: Whether enrolled students can access the group from outside your network via RemoteRF Global (default Y), and whether the group should be open to all Global users without an enrollment code (default N for courses).
Terminal
server@remoterf: groups create Available device IDs: 0, 1, 2, 3, 4, 5, 6, 7, 8 Enter group name (c to cancel): ee123_f26 Confirm group name 'ee123_f26'? (y/n): y Devices whitelist (e.g. 0,1,2) (c to cancel): 0,1,2,3,4,5,6,7,8 Max reservation time (sec) [1800] (c to cancel): 1800 Max concurrent reservations [3] (c to cancel): 3 Group lifetime (sec) [0=forever] (c to cancel): 0 Max days ahead a reservation may start [7] (0=no limit) (c to cancel): 7 Reachable from outside your network (via Global)? (Y/n) (c to cancel): y Public: open to anyone on RemoteRF Global? (y/N) (c to cancel): n ◆ Group 'ee123_f26' (group_id=1) created.
Recommended Classroom Policy: In undergraduate courses at UCLA with 60 to 100 students, setting reservation time slots to 30 minutes (1800 seconds) and allowing at most 3 concurrent reservations per student has proven ideal for balancing debugging time with fair access across the class.

After creating the group, verify it and record its group_id for the next step:

groups list

Step 2: Generating Enrollment Codes

Students need a valid enrollment code to enroll in your course group. To generate a batch of enrollment codes attached to your course’s group_id, run:

codes create

You will be prompted for:

  • How many enrollment codes to generate
  • Whether to attach a user group (Y) and the group_id of the user group to attach them to
  • Characters per code name (default 10, minimum 4; 4 or 5 characters is convenient for students)
  • Confirmation (Use these codes?) after previewing the generated code names
  • Uses per code (default 1 for single-use codes)
  • Duration in seconds of the code’s validity (0 = never expires)
Terminal
server@remoterf: codes create How many enrollment codes? (c to cancel): 90 Attach a user group? (Y/n) (c to cancel): y Group ID to attach codes to? (c to cancel): 1 Characters per code name? [10] (c to cancel): 5 Use these codes? (y/n): y Uses per code? [1] (c to cancel): 1 Duration in seconds? [3600] (0=never expires) (c to cancel): 0 ◆ Created 90 enrollment codes for group_id=1.

Generate Extra Spare Codes: If you teach a class of 60 students, generate around 90 to 120 single-use codes (uses = 1). Keeping extra single-use codes on hand makes it effortless to accommodate late-adding students or issue a replacement code on standalone local servers. Avoid using a single multi-use code for an entire class, as a single student could use it to register multiple accounts and bypass reservation quotas.

Step 3: Distributing Codes to Students

To export all generated enrollment codes to a CSV file in the server machine’s Downloads folder, run:

codes csv

You can also view active codes in the terminal with codes list or export group metadata with groups csv.

Quick Distribution Tip: Open the exported CSV file in Excel or Google Sheets and place each student’s university ID number next to an enrollment code. For added privacy when sharing a lookup sheet with your class, use =RIGHT(CELL, 4) to display only the last 4 or 5 digits of each student’s university ID alongside their assigned enrollment code, then export as a PDF. (Note that enrollment codes are not tied to a specific student until used to register.)

Mid-Course Modifications & Cleanup

Editing Group Permissions Mid-Term

If you add new SDRs to your deployment mid-quarter or want to adjust reservation limits before a final project deadline, run:

groups edit

Enter the group ID and update any combination of group name, device whitelist, maximum reservation time, maximum concurrent reservations, or group lifetime. Changes apply to all existing members of the user group.

Revoking Enrollment Codes

To revoke a single unused/leaked enrollment code by name, or all remaining codes for a group after add/drop ends:

codes remove

Removing enrollment codes only prevents new enrollments with those codes; students who have already enrolled remain in the group.

End-of-Term Cleanup

If your course user group was not already configured to expire automatically, you can manually remove it at the end of the term with groups remove (or disable access via groups edit) so students no longer hold reservation privileges on the hardware:

groups remove

Next Steps