®

BC|Commander
v11 User Guide

User Guide Version: 11.5.0

Software Version: 11.5.0
Date: April 14, 2014

Corporate Headquarters
Rajant Corporation
400 East King Street
Malvern, PA 19355
Tel: (484) 595-0233
Fax: (484) 595-0244

http://www.rajant.com

Document Part Number: 03-100115-011

Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Copyright Statement
Rajant, the Rajant logo, BreadCrumb, Instamesh, BC|Commander, and Bring Your Network with You!
are registered trademarks of Rajant Corp. in the United States and certain other countries.

BC|Commander® v11 User Guide

Copyright © 2009–2014 Rajant Corp. All rights reserved.

2
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

GNU General Public License Statement

Certain components of the Rajant BreadCrumb firmware are subject to the GNU General Public License
Version 2, or other so-called open source licenses ("Open Source Software"). In compliance with the
terms of certain Open Source Software licenses like the GNU General Public License Version 2
("GPLv2"), Rajant makes certain modifications to Open Source Software that Rajant uses, modifies and
distributes pursuant to such licenses available to customers in source code form upon request. You are
free to use, modify and distribute Open Source Software so long as you comply with the terms of the
relevant Open Source Software license. In particular, the GPLv2 is available in the appendix of this
manual or at www.gnu.org/copyleft/gpl.html.

3
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Table of Contents
Copyright Statement.....................................................................................................................2
GNU General Public License Statement......................................................................................3
Preface........................................................................................................................................16
1 Introduction to BC|Commander...........................................................................................17
1.1 New for Version 11.5.0.....................................................................................................17
1.1.1 New Features and Enhancements...........................................................................17
1.1.2 Fixes.........................................................................................................................19
1.2 Version 10 Features Not Yet Implemented in Version 11................................................19
1.3 Upgrading from Version 10 to Version 11........................................................................19
1.4 Support Plus.....................................................................................................................20
2 Installing BC|Commander.....................................................................................................21
2.1 System Requirements......................................................................................................21
2.2 BreadCrumb Firmware Requirements.............................................................................21
2.3 Installing BC|Commander................................................................................................21
2.3.1 Upgrading BC|Commander......................................................................................21
2.3.2 Installing on 32-bit Microsoft Windows.....................................................................21
2.3.3 Installing on 64-bit Microsoft Windows.....................................................................21
2.3.4 Installing on Linux — Self-Extracting Shell Script....................................................22
2.3.5 Installing on Linux — tar file.....................................................................................22
2.3.6 Installing on Ubuntu Linux - .deb file........................................................................22
2.3.7 Installing on Fedora Linux - .rpm file........................................................................22
3 Launching BC|Commander..................................................................................................23
3.1 BreadCrumb User Accounts.............................................................................................23
3.2 Default Login Credentials.................................................................................................23
3.3 Changing Passwords.......................................................................................................24
3.4 Command Line Options....................................................................................................24
4 BC|Commander Application Layout....................................................................................26
4.1 Menu Bar..........................................................................................................................26
4.1.1 File Menu..................................................................................................................26
4.1.2 View Menu................................................................................................................27
4.1.3 Mesh Menu...............................................................................................................27
4.1.4 BreadCrumb Menu...................................................................................................28
4.1.5 Help Menu................................................................................................................28
4.2 Multiple Display Tabs........................................................................................................29
4.3 Filters................................................................................................................................29
4.3.1 Filter Types...............................................................................................................29
4.3.2 Filter Attributes..........................................................................................................29
4.3.3 Filter Input Field........................................................................................................29

4
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

4.3.4 Filter on Selection.....................................................................................................30

4.4 Dockable Panels...............................................................................................................30
4.5 Main View Panel...............................................................................................................30
4.5.1 BreadCrumb Table....................................................................................................30
4.5.2 Topology View...........................................................................................................30
4.6 System Information Panel................................................................................................30
4.6.1 Alerts.........................................................................................................................31
4.6.2 Tasks.........................................................................................................................31
4.6.3 Trace.........................................................................................................................31
4.6.4 Analysis.....................................................................................................................31
4.7 Details Panel....................................................................................................................31
4.7.1 Details.......................................................................................................................31
4.7.2 Peers.........................................................................................................................32
4.7.3 Clients.......................................................................................................................32
4.7.4 BCAPI Explorer.........................................................................................................32
4.8 Status Bar.........................................................................................................................32
4.9 Saved Layouts..................................................................................................................33
4.9.1 Create a Saved Layout.............................................................................................33
4.9.2 Apply a Saved Layout...............................................................................................33
4.9.3 Overwrite an Existing Saved Layout........................................................................34
4.9.4 Delete a Saved Layout.............................................................................................34
5 BreadCrumb Table.................................................................................................................36
5.1 Managing Table Columns.................................................................................................36
5.2 Creating Custom Columns ..............................................................................................37
6 Topology View........................................................................................................................39
6.1 General Topology View Use.............................................................................................39
6.1.1 BreadCrumb Display................................................................................................39
6.1.2 BreadCrumb Icons....................................................................................................40
6.1.3 Client Display............................................................................................................41
6.1.4 Link Display..............................................................................................................41
6.2 Topology View Context Menu...........................................................................................42
6.3 Mouse and Keyboard View Controls................................................................................43
6.4 Offline Tilesets..................................................................................................................44
6.5 Convert Image to Tileset..................................................................................................45
6.5.1 Import v10 Map.........................................................................................................47
7 Configuration Window..........................................................................................................48
7.1 Configuration Window Features.......................................................................................48
7.1.1 Save / Reset / Cancel...............................................................................................48
7.1.2 Import / Export..........................................................................................................49

5
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

7.1.3 Settings Tree.............................................................................................................50

7.1.4 Settings Filter............................................................................................................50
7.1.5 Settings Panel...........................................................................................................50
7.1.6 Help Panel................................................................................................................50
7.2 User Input and Validation.................................................................................................50
7.2.1 Text Field Validation..................................................................................................50
7.2.2 General Validation....................................................................................................51
7.3 Configuring Preferences...................................................................................................51
7.4 Configuring BreadCrumbs................................................................................................51
7.4.1 Bulk Configuration....................................................................................................51
7.4.2 No Reboot After Save...............................................................................................52
8 Preferences............................................................................................................................53
8.1 General.............................................................................................................................53
8.1.1 General: Hide Single Tab..........................................................................................53
8.1.2 File Editing: File Editor..............................................................................................53
8.1.3 File Editing: Run File Editor in Terminal...................................................................53
8.1.4 File Editing: Terminal................................................................................................53
8.1.5 Highlighting: Enable Peer Highlighting.....................................................................54
8.1.6 Highlighting: Peer Highlight Color............................................................................54
8.1.7 Highlighting: Filter Highlight Color............................................................................54
8.2 Alerts.................................................................................................................................54
8.2.1 Alerts: Filtered Alert Codes.......................................................................................54
8.2.2 Filtered Alert Codes: Remove All..............................................................................54
8.2.3 Filtered Alert Codes: Add..........................................................................................54
8.2.4 Filtered Alert Codes: Remove..................................................................................54
8.3 BCAPI...............................................................................................................................54
8.3.1 BCAPI: General Update Interval (sec).....................................................................54
8.3.2 BCAPI: GPS Update Interval (sec)...........................................................................54
8.4 BreadCrumb Discovery....................................................................................................54
8.4.1 BreadCrumb Discovery: Only Discover Manually Listed BreadCrumbs..................54
8.4.2 BreadCrumb Discovery: Addressing Protocol..........................................................54
8.4.3 BreadCrumb Discovery: Manual BreadCrumb Discovery List.................................54
8.4.4 Manual BreadCrumb Discovery List: Import............................................................55
8.4.5 Manual BreadCrumb Discovery List: Remove All....................................................55
8.4.6 Manual BreadCrumb Discovery List: Add................................................................55
8.4.7 Manual BreadCrumb Discovery List: Remove.........................................................55
8.5 Confirmation Dialogs........................................................................................................55
8.5.1 Confirmation Dialogs: Always Install After Firmware Upload...................................55
8.5.2 Confirmation Dialogs: Always Reboot After Firmware Install..................................55

6
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

8.5.3 Confirmation Dialogs: Always Set Manual Location in Map View............................55

8.5.4 Confirmation Dialogs: Always Clear Manual Location in Map View.........................55
8.6 Topology View...................................................................................................................55
8.6.1 Topology View: Background Color for Topology View..............................................55
8.6.2 BreadCrumbs: BreadCrumb Size (pixels)................................................................55
8.6.3 BreadCrumbs: Wrap BreadCrumb Labels................................................................55
8.6.4 BreadCrumbs: Character to Signify Wrapping.........................................................55
8.6.5 BreadCrumbs: Wrap at First, Last or All Occurrences.............................................55
8.6.6 BreadCrumbs: Minimum Label Wrap Threshold......................................................55
8.7 Animation..........................................................................................................................56
8.7.1 Animation: Topology View Frame Rate (frames/sec)...............................................56
8.7.2 Animation: Topology View Non-Focused Frame Rate (frames/sec)........................56
8.8 Link Display......................................................................................................................56
8.8.1 Link Display: Wired Link Color..................................................................................56
8.8.2 Link Display: Wired Link to APT Master...................................................................56
8.8.3 Link Display: Unknown Link Color............................................................................56
8.8.4 Link Display: Unselected Links.................................................................................56
8.8.5 Link Display: Normal Links.......................................................................................56
8.8.6 Link Display: Selected Links.....................................................................................56
8.8.7 Link Display: Links Coloring Scheme.......................................................................56
8.8.8 Link Display: Colors for Frequency Ranges.............................................................56
8.8.9 Colors for Frequency Ranges: Remove All..............................................................56
8.8.10 Colors for Frequency Ranges: Add........................................................................56
8.8.11 Colors for Frequency Ranges: Remove.................................................................56
8.9 Analysis: Link Statistics....................................................................................................56
8.9.1 Link Statistics: Good Cost Limit................................................................................56
8.9.2 Link Statistics: Signal Too High (dBm).....................................................................57
8.9.3 Link Statistics: SNR Worst (dB)................................................................................57
8.9.4 Link Statistics: SNR Best (dB)..................................................................................57
8.10 Analysis: Frequency Overlap..........................................................................................57
8.10.1 Guard Band............................................................................................................57
8.11 Tab Layouts....................................................................................................................57
8.11.1 Tab Layouts............................................................................................................57
8.11.2 Tab Layouts: Remove All........................................................................................57
8.11.3 Tab Layouts: Remove.............................................................................................57
9 BreadCrumb Configuration..................................................................................................58
9.1 General.............................................................................................................................58
9.1.1 General: BreadCrumb Name....................................................................................58
9.1.2 General: Notes..........................................................................................................58

7
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.1.3 Status LED: LED Mode............................................................................................58

9.1.4 Location: Latitude / Longitude..................................................................................58
9.1.5 Location: Altitude......................................................................................................59
9.1.6 Battery: Battery Warning Threshold (minutes).........................................................59
9.1.7 Battery: Battery Error Threshold (minutes)...............................................................59
9.1.8 Groups......................................................................................................................59
9.1.9 Groups: Remove All..................................................................................................59
9.1.10 Groups: Add............................................................................................................59
9.1.11 Groups: Remove.....................................................................................................59
9.2 Network............................................................................................................................59
9.2.1 Network: Network Name...........................................................................................59
9.2.2 Network: Administration Port....................................................................................59
9.2.3 Network: Enable DHCP Server................................................................................60
9.2.4 Network: Enable SNMP Server................................................................................60
9.2.5 IPv4: IPv4 Address Assignment Method..................................................................60
9.2.6 IPv4 Manually Assigned Settings.............................................................................60
9.3 VLANs...............................................................................................................................61
9.3.1 VLANs: Remove All..................................................................................................61
9.3.2 VLANs: Add..............................................................................................................61
9.3.3 VLANs: Remove.......................................................................................................61
9.3.4 VLANs: VLAN Number.............................................................................................61
9.3.5 VLANs: Name...........................................................................................................61
9.3.6 VLANs: Priority.........................................................................................................61
9.4 Port Forwarding................................................................................................................61
9.4.1 Port Forwarding: Remove All....................................................................................61
9.4.2 Port Forwarding: Add................................................................................................61
9.4.3 Port Forwarding: Remove.........................................................................................62
9.4.4 Port Forwarding: Incoming Port Range....................................................................62
9.4.5 Port Forwarding: Forwarded Port Range (low)........................................................62
9.4.6 Port Forwarding: Forward to Address.......................................................................62
9.4.7 Port Forwarding: Protocol Type................................................................................62
9.4.8 Port Forwarding: Enable...........................................................................................62
9.4.9 Port Forwarding: Application....................................................................................62
9.5 Capture.............................................................................................................................62
9.5.1 Capture: Enable Remote Capture............................................................................62
9.5.2 Capture: Maximum Packet Size (bytes)...................................................................62
9.5.3 Capture: Capture Listening Port...............................................................................62
9.6 Ports: Local.......................................................................................................................62
9.6.1 Local Port: Local Port Native VLAN.........................................................................62

8
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.7 Ports: wlanX.....................................................................................................................63

9.7.1 Mesh: Enable Meshing.............................................................................................63
9.7.2 Mesh: InstaMesh Minimum Cost Difference (%)......................................................63
9.7.3 Mesh: Enable Broadcast Receiver Address.............................................................63
9.7.4 Radio: Regulatory Compliance Mode.......................................................................65
9.7.5 Radio: Regulatory Domain.......................................................................................65
9.7.6 Radio: Channel Number...........................................................................................65
9.7.7 Radio: Channel Bandwidth.......................................................................................65
9.7.8 Radio: Transmit Power.............................................................................................66
9.7.9 Radio: Multicast Rate...............................................................................................66
9.7.10 Radio: Enable Compression...................................................................................66
9.7.11 Radio: Antenna Selection.......................................................................................66
9.7.12 Settings: Maximum Peers.......................................................................................66
9.7.13 Settings: Range (meters)........................................................................................66
9.7.14 Settings: Radio Beacon Interval (ms).....................................................................66
9.7.15 Settings: Radio Timeout (sec)................................................................................66
9.7.16 Settings: Noise Level Warning Threshold..............................................................66
9.7.17 Settings: Noise Level Error Threshold....................................................................66
9.7.18 Settings: Enable Packet Capture...........................................................................66
9.8 Ports: AP X.......................................................................................................................67
9.8.1 Access Point: Enable Access Point..........................................................................67
9.8.2 Access Point: ESSID................................................................................................67
9.8.3 Access Point: Enable ESSID Broadcast..................................................................67
9.8.4 Access Point: Ignore Broadcast Probe Requests....................................................67
9.8.5 Security: Security Mode............................................................................................67
9.8.6 Security: WEP Key...................................................................................................67
9.8.7 Security: WPA/WPA2 Key Type................................................................................67
9.8.8 Security: WPA/WPA2 Raw Key................................................................................68
9.8.9 Security: WPA/WPA2 Passphrase............................................................................68
9.8.10 Security: Cipher Suite.............................................................................................68
9.8.11 Security: GTK Rekey Interval (seconds)................................................................68
9.8.12 Security: Rekey When Station Leaves IBSS..........................................................68
9.8.13 Security: GMK Rekey Interval (seconds)...............................................................68
9.8.14 Security: Radius Primary Server Retry Interval......................................................68
9.8.15 Security: Accounting Primary Server Retry Interval...............................................68
9.8.16 Security: Radius and Accounting Servers..............................................................69
9.8.17 Radius and Accounting Servers: Port....................................................................69
9.8.18 Radius and Accounting Servers: Shared Secret....................................................69
9.8.19 Radius and Accounting Servers: Address..............................................................69

9
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.8.20 VLAN Configuration: Accept Untagged Packets....................................................69

9.8.21 VLAN Configuration: Accept Selected VLANs.......................................................69
9.8.22 VLAN Configuration: Accept Non-Selected VLANs...............................................69
9.8.23 VLAN Configuration: Native VLAN (always accepted)...........................................69
9.8.24 VLAN Configuration: Selected VLANs...................................................................69
9.9 Ports: ethX........................................................................................................................70
9.9.1 Ethernet: Ethernet Mode..........................................................................................70
9.9.2 Ethernet: Alternate Gateway....................................................................................70
9.9.3 Ethernet: Port Speed................................................................................................70
9.9.4 Ethernet: Duplex Mode.............................................................................................71
9.9.5 Ethernet: Gateway Assignment Method...................................................................71
9.9.6 Ethernet: IPv4 Manually Assigned Settings.............................................................71
9.9.7 Ethernet: Request Fallback......................................................................................71
9.9.8 VLAN Configuration..................................................................................................71
9.10 Security...........................................................................................................................72
9.10.1 Security: Packet Cipher..........................................................................................72
9.10.2 Security: MAC Address Cipher...............................................................................72
9.10.3 Security: Per-Hop Authentication Algorithm...........................................................72
9.10.4 Security: Network Key............................................................................................72
9.10.5 Security: Network Key Sequence Number.............................................................72
9.10.6 Security: Version 10 Network Encryption Key........................................................72
9.10.7 Security: Version 10 Network Authentication Key..................................................72
9.10.8 Security: FIPS-Equivalent Mode............................................................................73
9.11 ACL.................................................................................................................................73
9.11.1 ACL: ACL Mode......................................................................................................73
9.11.2 ACL: AP Only..........................................................................................................73
9.11.3 ACL: White List.......................................................................................................73
9.11.4 ACL: Black List.......................................................................................................73
9.12 BCAPI.............................................................................................................................74
9.12.1 User Credentials: Passphrase for "View" role........................................................74
9.12.2 User Credentials: Passphrase for "Admin" role.....................................................74
9.12.3 User Credentials: Passphrase for "Crypto Officer" role.........................................74
9.12.4 SSL/TLS Settings: Security Profile.........................................................................74
9.12.5 SSL/TLS Settings: Certificate and Security Bits.....................................................74
9.12.6 SSL/TLS Settings: Handshake Priority String........................................................74
9.13 InstaMesh.......................................................................................................................74
9.13.1 General: InstaMesh DS (packets)..........................................................................75
9.13.2 General: InstaMesh DT (sec).................................................................................75
9.13.3 General: Max TTL (1/100 sec)................................................................................75

10
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.13.4 General: GC Interval (sec)......................................................................................75

9.13.5 General: Minimum GC Age (sec)...........................................................................75
9.13.6 General: MAC Garbage Collection Threshold........................................................75
9.13.7 General: ARP Garbage Collection Threshold........................................................75
9.13.8 General: BreadCrumb Garbage Collection Threshold...........................................75
9.13.9 General: Neighbor Discovery Garbage Collection Threshold................................76
9.13.10 General: ARP Proxy Timeout (sec)......................................................................76
9.13.11 General: Enable Tactical Multicast.......................................................................76
9.13.12 General: Tactical Multicast Coalesce Interval......................................................76
9.13.13 General: Cost Weighted Moving Average Interval...............................................76
9.13.14 General: Excellent Quality Passing Lane Maximum Cost....................................76
9.13.15 General: Good Quality Passing Lane Maximum Cost.........................................76
9.13.16 General: Fair Quality Passing Lane Maximum Cost............................................77
9.13.17 General: Enable STP Filter...................................................................................77
9.13.18 General: Enable v10 Compatibility.......................................................................77
9.13.19 General: Enable Peer Statistics Reporting...........................................................77
9.13.20 Flood: Max Flood (packets/sec)...........................................................................77
9.13.21 Flood: Max Flood per Source (packets/sec)........................................................77
9.13.22 Flood: Allow Bursting............................................................................................77
9.13.23 Flood: Flood Limits...............................................................................................78
9.13.24 Wireless: Connection Timeout (sec)....................................................................78
9.13.25 Wireless: Keepalive Interval (sec)........................................................................78
9.13.26 Wireless: Broadcast Receive Address Threshold (peer/radio)............................78
9.13.27 Protocol Tunneling: APT Timeout (sec)................................................................78
9.13.28 Protocol Tunneling: APT Keepalive Interval (sec)................................................78
9.13.29 Protocol Tunneling: APT Priority...........................................................................78
9.13.30 Protocol Tunneling: Remote Protocol Tunneling Connection Attempt Interval....79
9.13.31 Protocol Tunneling: Remote Protocol Tunneling Host Names or Addresses.......79
9.13.32 Remote Protocol Tunneling Host Names or Addresses: Remove All..................79
9.13.33 Remote Protocol Tunneling Host Names or Addresses: Add..............................79
9.13.34 Remote Protocol Tunneling Host Names or Addresses: Remove.......................79
9.14 TRoIP..............................................................................................................................79
9.14.1 TRoIP: Instance Count...........................................................................................79
9.14.2 TRoIP: Enable Local Audio Mixing.........................................................................79
9.14.3 TRoIP: Mixmaster Election Bias.............................................................................79
9.14.4 TRoIP: Enable Multicast Media Streaming............................................................80
9.14.5 Audio: Enable Side Tone........................................................................................80
9.14.6 Audio: Side Tone Gain............................................................................................80
9.14.7 Audio: Enable Earpiece..........................................................................................80

11
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.14.8 Audio: Earpiece Volume.........................................................................................80

9.14.9 Audio: Voice Activity Detection...............................................................................80
9.14.10 Audio: Voice Activity Threshold............................................................................80
9.14.11 Audio: Enable Microphone...................................................................................80
9.14.12 Audio: Direct Microphone to.................................................................................80
9.14.13 Audio: Microphone Gain.......................................................................................80
9.14.14 Audio: Auxiliary Audio Channel Available.............................................................80
9.14.15 Audio: Enable Auxiliary Audio Channel................................................................80
9.14.16 Audio: Direct Auxiliary Input to..............................................................................80
9.14.17 Audio: Auxiliary Audio Gain..................................................................................80
9.14.18 Audio: Enable HID PTT Feature...........................................................................80
9.14.19 Audio: Raw HID PTT Protocol..............................................................................80
9.14.20 Audio: Double Tap Action.....................................................................................80
9.14.21 Audio: Audio Codec..............................................................................................81
9.14.22 Groups: Right Ear Call Group..............................................................................81
9.14.23 Groups: Left Ear Call Group.................................................................................81
9.14.24 Groups: Call Group Slots......................................................................................81
9.14.25 Call Group Slots: Remove All...............................................................................81
9.14.26 Call Group Slots: Add...........................................................................................81
9.14.27 Call Group Slots: Remove....................................................................................81
9.14.28 Call Group Slots: Group Number.........................................................................81
9.14.29 Call Group Slots: Group Name.............................................................................81
9.14.30 Call Group Slots: Join Group................................................................................81
9.15 Industrial Applications.....................................................................................................82
9.15.1 General: Modbus Mode..........................................................................................82
9.15.2 Modbus: Modbus TCP port.....................................................................................82
9.15.3 Modbus: Modbus Device Slave ID.........................................................................82
9.15.4 Modbus: Serial Port................................................................................................82
9.15.5 Modbus: Serial Line Baud Rate..............................................................................82
9.15.6 Modbus: Serial Line Data Bits................................................................................82
9.15.7 Modbus: Serial Line Parity Mode...........................................................................82
9.15.8 Modbus: Serial Line Stop Bits................................................................................82
10 Administrative Tasks...........................................................................................................83
10.1 General Administration...................................................................................................83
10.1.1 Manually Adding BreadCrumbs..............................................................................83
10.1.2 Upgrading BreadCrumb Firmware.........................................................................83
10.1.2.1 Over-the-Air (OTA) Firmware Upgrade...........................................................83
10.1.2.2 USB Firmware Upgrade..................................................................................84
10.1.2.3 USB Based Zeroize.........................................................................................85

12
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

10.2 Managing Clients............................................................................................................85

10.2.1 Access Control........................................................................................................85
10.3 Troubleshooting Tasks....................................................................................................85
10.3.1 Taking Network Snapshots.....................................................................................85
10.3.2 InstaMesh Trace.....................................................................................................85
10.3.2.1 Trace Result ....................................................................................................86
10.3.2.2 Multiple Trace Tabs .........................................................................................87
10.3.2.3 Trace Output....................................................................................................87
10.3.2.4 Visual Trace.....................................................................................................88
10.3.3 Compute v11 IP Addresses....................................................................................89
10.3.4 Create Memory Dump............................................................................................90
10.4 Security-Related Tasks...................................................................................................90
10.4.1 Zeroize Keys / Restore Factory Defaults................................................................90
11 BC|Commander Analysis....................................................................................................91
11.1 Configuration Settings....................................................................................................91
11.1.1 Inconsistent Settings Table.....................................................................................91
11.1.2 Consistent Settings Table.......................................................................................92
11.2 Link Statistics..................................................................................................................93
11.2.1 Link Statistics Summary Table...............................................................................93
11.2.2 Link Statistics Detail Table......................................................................................94
11.3 Noise Analysis................................................................................................................95
11.3.1 Noise Summary Table............................................................................................95
11.3.2 Noise Detail Table...................................................................................................95
11.4 Frequency Overlap Analysis...........................................................................................96
12 BreadCrumb Network Security..........................................................................................98
12.1 Securing a BreadCrumb Network..................................................................................98
12.2 Security Checklist...........................................................................................................98
12.3 Securing Mesh Links......................................................................................................98
12.4 Securing Station Links....................................................................................................98
12.5 Examples......................................................................................................................100
12.5.1 Unintended Transmission Of Cleartext.................................................................100
12.5.2 Unintended Admission To Network......................................................................100
12.5.3 Unintentional Weakening Of Security...................................................................100
12.5.4 In Through The Ethernet......................................................................................101
Appendix A: Radio Channels and Frequencies..................................................................102
Appendix B: Error and Warning Codes................................................................................107
Appendix C: Ports and Protocols.........................................................................................111
Appendix D: BCAPI Query Language...................................................................................112
Appendix E: Rajant End User License Agreement.............................................................121

13
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Appendix F: GNU General Public License...........................................................................129

Index of Figures
Figure 1: Default Login Credentials Window..............................................................................24
Figure 2: BC|Commander v11 Default Layout...........................................................................26
Figure 3: BreadCrumb Filter.......................................................................................................29
Figure 4: BCAPI Explorer...........................................................................................................32
Figure 5: Create a Saved Layout................................................................................................33
Figure 6: Apply a Saved Layout..................................................................................................34
Figure 7: Saved Layout Preferences..........................................................................................35
Figure 8: BreadCrumb Table.......................................................................................................36
Figure 9: BreadCrumb Table - Add Column................................................................................37
Figure 10: BreadCrumb Table - Add Custom Column................................................................38
Figure 11: Topology View Bullseye Layout.................................................................................39
Figure 12: BreadCrumbs Icons...................................................................................................40
Figure 13: Link Display...............................................................................................................42
Figure 14: Save Offline Tileset....................................................................................................44
Figure 15: Create an Offline Tileset Dialog Box.........................................................................46
Figure 16: BreadCrumb Configuration Window..........................................................................48
Figure 17: BreadCrumb Configuration Export............................................................................49
Figure 18: Image Upload Window..............................................................................................83
Figure 19: USB Flash Manager..................................................................................................84
Figure 20: InstaMesh Trace Dialog Box.....................................................................................86
Figure 21: InstaMesh Trace Output............................................................................................87
Figure 22: Mesh Analysis: Inconsistent Settings........................................................................91
Figure 23: Mesh Analysis: Inconsistent Settings w/ Selected Cell.............................................92
Figure 24: Consistent Settings Table..........................................................................................93
Figure 25: Link Statistics Summary Table..................................................................................94
Figure 26: Link Statistics Detail Table.........................................................................................94
Figure 27: Noise Summary Table...............................................................................................95
Figure 28: Noise Detail Table......................................................................................................95
Figure 29: Frequency Overlap Analysis......................................................................................96
Figure 30: Frequency Overlap - Selected..................................................................................97

Index of Tables
Table 1: BreadCrumb User Accounts.........................................................................................23
Table 2: Color Codes for BreadCrumb Status............................................................................40
Table 3: BreadCrumb Icons and Their Meanings.......................................................................41
Table 4: 2.4 GHz Radio Channels and Frequencies................................................................102

14
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Table 5: 5 GHz Radio Channels and Frequencies...................................................................103

Table 6: 900 MHz Radio Channels and Frequencies...............................................................104
Table 7: 4.8 GHz Radio Channels and Frequencies................................................................105
Table 8: 4.9 GHz Radio Channels and Frequencies................................................................106
Table 9: Ports and Protocols.....................................................................................................111
Table 10: BQL - Top-level Data Objects...................................................................................112
Table 11: BQL - Field Types.....................................................................................................113
Table 12: BQL – Logical Comparators......................................................................................114
Table 13: BQL – Repeated Fields Operations..........................................................................116
Table 14: BQL – Built-In Filters.................................................................................................117

15
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Preface
Purpose and Scope
This manual provides information and guidance to all personnel who are involved with and use Rajant
Corporation's BC|Commander® to administer wireless mesh networks using Rajant Corporation's
BreadCrumb® Wireless Network devices ("BreadCrumbs®").
Who This Manual is For
Administrators of BreadCrumb wireless mesh networks should have a working knowledge of TCP/IP
networking, such as DHCP, NAT, and DNS. While the network lay person may be able to perform some
administrative tasks, it is recommended that network configuration be performed by experienced
network administrators.
Certain advanced features require additional in-depth knowledge, such as 802.11i security, VLANs, and
traffic prioritization.
Feedback Welcome
The user of this manual is encouraged to submit comments and recommended changes to improve this
manual and all Rajant products. Please send your feedback to [email protected]. Please be sure to
include the version number of the manual or product you are using as well as the relevant page numbers
if appropriate.

16
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

1 Introduction to BC|Commander
BC|Commander is Rajant's standard management and monitoring application for wireless mesh
networks built with Rajant BreadCrumb wireless devices. BC|Commander provides a graphical user
interface to help visualize the entire mesh and to monitor and configure individual BreadCrumbs. There
are several advanced features that are helpful for managing and monitoring large or complex networks.
1.1 New for Version 11.5.0
Rajant recommends to its customers that they upgrade their networks to this release after testing it for
their individual application and networking needs.

1.1.1 New Features and Enhancements

● Per-MAC multicast flood limits are now supported in InstaMesh configuration in addition to the
existing global and per-source multicast limits, allowing fine-grained control over multicast
traffic.

● Flood limiting can be configured to disallow bursting such that a minimum inter-packet spacing
is enforced, allowing administrators to enforce stricter multicast policies.

● A new AP option has been added to disable broadcast probe responses. This can improve the RF
environment considerably in dense networks.

● A new BCAPI Explorer view has been added for viewing raw BCAPI data. This can be helpful
for viewing information that BC|Commander does not otherwise display and for developing
alternative BCAPI client applications.

● Ethernet link state changes (plug/unplug) are now tracked and reported in BC|Commander. This
can assist administrators in finding faulty hardware connected to the mesh.

● A new "FIPS-Compatible Mode" has been added that enforces all FIPS 140-2 rules. Note: this
implementation is not validated by NIST, but is identical to the implementation currently under
NIST review.

● Added XSalsa-20 cipher for packet and MAC address encryption, providing considerable
performance benefits over AES-based ciphers (actual performance will vary with traffic and RF
characteristics). For more information on this cipher, see https://en.wikipedia.org/wiki/Salsa20.

● A new Channel Overlap report has been added to the Mesh Analysis function, providing a
graphical display of spectrum consumption to assist with channel management.

● A new "Filter on Selection" feature has been added to temporarily remove all non-selected
BreadCrumbs from the current tab, providing a quick means to create a task-focused view.

● Columns in tables throughout BC|Commander can now be selectively shown/hidden to support

task-specific layouts.

● Customized window layouts may now be saved and applied to assist with administrative
17
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

workflows.

● Custom columns may now be added to the Table View using the same syntax as Filters for a fully
customized display.

● Documentation for Filter and Custom Column syntax (BCAPI Query Language or "BQL") has
been greatly enhanced, including a new Appendix in the BC|Commander User Guide.

● Documentation of IP ports and protocol information required for firewall configuration has been
added to the BC|Commander User Guide.

● Documentation for Mesh Analysis is now covered in depth in a new Analysis chapter of the
BC|Commander User Guide.

● The "APT Only" Ethernet mode has been renamed to "Mesh Only" and the "Bridge" Ethernet
mode has been renamed to "Bridge+Mesh" to clarify their use.

● BreadCrumbs with APT peers that disagree on whether they should be in Mesh-Only mode now
issue a warning to alert of a potentially unsecure misconfiguration.

● Administrators can now force BreadCrumbs to reboot even if they are performing a task (such as
taking a Mesh Snapshot) via a new reboot dialog option, reducing the need to visit remote nodes.

● BC|Commander can now receive unsolicited discovery responses, allowing it to more quickly
display BreadCrumbs that have just been turned on or plugged into a mesh.

● BreadCrumbs now issue a warning when enabling TKIP attack countermeasures, helping
administrators troubleshoot wireless client connectivity issues. For information on
countermeasures, see https://en.wikipedia.org/wiki/Temporal_Key_Integrity_Protocol#Security

● Manufacturer information is now displayed for wireless client devices in the Topology View and
Clients list. This can help to determine the type of client device. Information is derived from the
IEEE OUI database.

● When viewing a loaded snapshot, the name of the snapshot file is now displayed, eliminating
confusion when reviewing multiple snapshots.

● Radio configurations with WEP on 40 MHz-wide channels are now disallowed, matching
specifications.

● More BC|Commander installers are now available: 64-bit Windows, and Linux .deb and .rpm.

● Mesh analysis now shows the index of repeated fields in consistency report, facilitating
administrative analysis.

● Mesh analysis reports now include time and date, eliminating confusion when reviewing

18
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

snapshots.

● General/Radio/Ethernet detail panes are now individually collapsible, allowing more tailored
views that dedicate screen real estate to the information you require.

● Additional InstaMesh garbage collection thresholds are now configurable, enabling fine control
over InstaMesh memory and CPU consumption. These should only be modified when
recommended by Rajant.

● Miscellaneous additional enhancements

1.1.2 Fixes
● Two separate issues that could cause a BreadCrumb to stop processing traffic and responding to
BC|Commander have been resolved. (Causes were a specific type of ICMPv6 packet and an
extremely unusual APT usage scenario)

● An issue that could cause Mesh Snapshots to freeze has been resolved.

● An issue that could cause immediate failover to a secondary RADIUS server on boot has been
corrected.

● Two-antenna radios operate at proper performance level when enabling only the second antenna.

1.2 Version 10 Features Not Yet Implemented in Version 11

● Export tables to .csv file (currently implemented in some tables, but not yet all)
● Peer link filters.
● Client nicknames.
● Fast frames.
To see the latest features and fixes, see the release notes on our support web site.
1.3 Upgrading from Version 10 to Version 11
Although BreadCrumbs running v10 and v11 can communicate with one another when configured
properly, BC|Commander version 10 cannot communicate with BreadCrumbs running v11 firmware.
Similarly, BC|Commander version 11 cannot communicate with BreadCrumbs running v10 firmware.
In order to upgrade BreadCrumbs from v10 to v11, you will need both versions of BC|Commander
installed.
Alternatively, you can prepare a USB stick with v11 firmware using either v10 or v11 BC|Commander.
Chapter 10.1.2.2 USB Firmware Upgrade gives detailed instructions on how to prepare the USB stick
and perform the USB upgrade.
BreadCrumbs must be running firmware v10.32 or later. Earlier versions of v10 firmware will not
support the upgrade to v11. Use BC|Commander version 10 to initiate the firmware update.
Once updated, the BreadCrumbs can be re-configured using BC|Commander version 11.

19
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

1.4 Support Plus

BC|Commander no longer requires an Enterprise License to unlock any features. All features are
available in the software at the time of purchase. Annual Software Support Plus includes one year of
software and firmware updates, documentation, and BreadCrumb product phone support. Contact your
Rajant sales representative for more information.

20
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

2 Installing BC|Commander
Rajant periodically releases updated BC|Commander software. This updated software must be obtained
from Rajant.
2.1 System Requirements
BC|Commander runs on Windows XP and later, and on most Linux operating systems. Both require a
Java Runtime Environment (JRE), version 1.7 or higher. The latest version can be obtained and
downloaded from http://www.java.com. The BC|Commander installers for Windows, available from the
Rajant download website include OpenJDK in the install. This will not replace an existing system JRE,
but will provide BC|Commander with the tools it requires to run properly. There are also installers
available that do not include Java.
2.2 BreadCrumb Firmware Requirements
BC|Commander version 11 can only discover and administer BreadCrumbs running version 11
firmware. BreadCrumbs running version 10 firmware will need to be upgraded before they can be
administered by the new BC|Commander.

Both BC|Commander and the BreadCrumbs it administers should be operated at the

Important same version number.

2.3 Installing BC|Commander

2.3.1 Upgrading BC|Commander
When a new release of BC|Commander becomes available, it can be upgraded by simply running the
standard installation procedures shown below. It is not necessary to uninstall an earlier v11 installation.
Version 10 BC|Commander will NOT be removed by installing version 11. Both v10 and v11 versions
of BC|Commander can run simultaneously and independently of each other.
Important: If an installer package without Java (JRE or OpenJDK) is used, then it is up to the user to
make sure that the computer includes a Java Runtime Environment (JRE), version 1.7 or higher. The
latest version can be obtained and downloaded from http://www.java.com.
2.3.2 Installing on 32-bit Microsoft Windows
1. Obtain one of the two available 32-bit Windows installers from Rajant. At the time of this
writing, the relevant filenames are:
(a) bcc_windows_11_5_0_8.exe – includes OpenJDK 7
(b) bcc_windows_11_5_0_8_nojava.exe – does not include OpenJDK 7
2. Double-click on the installation program to begin the installation process.
3. Be sure to read and agree to the Rajant End User License Agreement.
4. Follow the rest of the on-screen instructions.
2.3.3 Installing on 64-bit Microsoft Windows
1. Obtain one of the two available 64-bit Windows installers from Rajant. At the time of this
writing, the relevant filenames are:
(a) bcc_windows_11_5_0_8_64bit.exe – includes OpenJDK 7

21
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

(b) bcc_windows_11_5_0_8_nojava_64bit.exe – does not include OpenJDK 7

2. Double-click on the installation program to begin the installation process.
3. Be sure to read and agree to the Rajant End User License Agreement.
4. Follow the rest of the on-screen instructions.

2.3.4 Installing on Linux — Self-Extracting Shell Script

Most of these Linux application installers do not include Java. It is up to the user to make sure that
Linux includes a Java Runtime Environment (JRE), version 1.7 or higher. The latest version can be
obtained and downloaded from http://www.java.com.
1. Obtain one of the two available installation packages from Rajant. The current installation
packages at the time of this writing are:
(a) bcc_unix_11_5_0_8.sh – includes Java JRE
(b) bcc_unix_11_5_0_8_nojre.sh – does not include Java JRE
2. Install the package with the following command (your filename may be different).
sudo sh bcc_unix_11_5_0_8_nojre.sh

2.3.5 Installing on Linux — tar file

1. Obtain the installation package from Rajant. The current installation package at the time of this
writing is bcc_unix_11_5_0_8.tar.gz – does not include Java JRE
2. Extract the files with the following command (your filename may be different).
tar -xf bcc_unix_11_5_0_8.tar.gz
3. The extracted files will be located in a bcc11 directory. The file you need to run BC|Commander
is bcc11. If you wish to include this in your search path or create a shortcut to the launcher,
follow your system's instructions to do so.
2.3.6 Installing on Ubuntu Linux - .deb file
1. Obtain the installation package from Rajant. The current installation package at the time of this
writing is bcc_unix_11_5_0_8.deb – does not include Java JRE
2. Install the package with the following command (your filename may be different).
sudo dpkg -i bcc_unix_11_5_0_8.deb
3. Program files will be installed to /opt/bcc11/ with symbolic links in /usr/local/bin/
2.3.7 Installing on Fedora Linux - .rpm file
1. Obtain the installation package from Rajant. The current installation package at the time of this
writing is bcc_unix_11_5_0_8.rpm – does not include Java JRE
2. Install the package with the following command (your filename may be different).
sudo yum localinstall bcc_unix_11_5_0_8.rpm
3. Program files will be installed to /opt/bcc11/ with symbolic links in /usr/local/bin/

22
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

3 Launching BC|Commander
During installation on Microsoft Windows, a "Rajant BCCommander" folder is added to your start
menu. This folder contains a shortcut for launching BC|Commander. Depending upon the options you
selected during installation, you may also have a BC|Commander shortcut on your desktop or in your
quick links bar.
Click on the BC|Commander shortcut on the start menu or quick link bar or double-click on the
BC|Commander shortcut on the desktop in order to launch BC|Commander.
No shortcuts are automatically created on Linux, although you may opt to create your own. To launch
BC|Commander, type bcc11 at a console.
3.1 BreadCrumb User Accounts
BC|Commander does not require a user to log in to use the application. However, an administrator must
first log in to individual BreadCrumbs in order to monitor and manage them. BC|Commander provides
three different login options, each with different privileges (See Table 1).

Table 1: BreadCrumb User Accounts.

Account Name / (Role) Default Password Access

view
breadcrumb-view Read-only access to configuration and status.
(Viewer)

Read access to configuration and status, read/write

access to non-security-related configuration.
admin
breadcrumb-admin Permitted to execute non-security-related
(Administrator)
commands such as "reboot", "zeroize" and
"upgrade firmware."

Read and write access to all configuration. Read

co
breadcrumb-co access to status. Permitted to execute all
(Crypto Officer)
commands, set encryption keys, and set passwords.

3.2 Default Login Credentials

Because it is impractical to log in to each BreadCrumb individually, and because most BreadCrumbs in
a network will have the same set of passwords, BC|Commander will automatically attempt to log in to
any BreadCrumb it discovers using default login credentials (i.e., username and password).
Whenever BC|Comamander is launched, the "Default Login Credentials" dialog window appears (see
Figure 1 below). This dialog can also be accessed from the "Mesh" menu.

23
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 1: Default Login Credentials Window

Specifying Default Login Credentials is only a means to automatically log in to

BreadCrumbs discovered by BC|Commander. It is NOT a means to log in to
BC|Commander itself. BC|Commander never requires you to log in. If you click the
Note "Cancel" button, the Default Login Credentials dialog will be dismissed and
BC|Commander will continue to discover BreadCrumbs, but will not automatically log
in to them.

An administrator can also log in to individual BreadCrumbs, or groups of BreadCrumbs. To do this,

select the desired BreadCrumb and either right click, or click the "BreadCrumb" menu. Then select
Login. A "Login to BreadCrumbs" dialog, similar to the one shown in Figure 1, will appear. Multiple
BreadCrumbs may be selected by holding down the shift key during selection (to select a contiguous set
of rows) or by holding down the ctrl key during selection (to toggle selection for individual
BreadCrumbs).
3.3 Changing Passwords
The passwords of the three administrator accounts on a BreadCrumb can be changed in the
Configuration Window. See section 9.12 BCAPI for more information on these settings. You must be
logged in as Crypto Officer in order to change these settings.
3.4 Command Line Options
BC|Commander has several command line options that can be used when launching the application from
a command prompt or they can be added to desktop shortcuts.
Usage: bcc11 [(-u|--user) <user>] [(-p|--pass) <pass>] [(-l|--level) <logLevel>]
[-c|--console] [--no-topo] [(-r|--reset) <reset>] [-h|--help] [--snapshot
<snapshot>] [--render <render>]

[(-u|--user) <user>]
Use with --pass to automatically log in to BreadCrumbs as the specified user
(view|admin|co).

24
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

[(-p|--pass) <pass>]
Use with --user to automatically log in to BreadCrumbs using the specified
password. NOTE: the password may be visible in your computer's process list
if
specified on the command line.

[(-l|--level) <logLevel>]
Controls the level of detail in application logs
(off|trace|debug|info|warn|error|all). (default: info)

[-c|--console]
Enables logging to console.

[--no-topo]
Disables the Topology View, e.g. to reduce system requirements or work around
graphics card issues.

[(-r|--reset) <reset>]
Resets BC|Commander settings. Options are:
l, layout reset all application layout options
p, prefs reset all application preferences
c, cache clear application caches
a, all reset all of the above

[-h|--help]
Displays this message.

[--snapshot <snapshot>]
Loads the specified snapshot file immediately upon launch.

[--render <render>]
Sets the graphics rendering pipeline. Must be one of: JAVA, XRENDER, or
OPENGL.

[--profile <profile>]
Selects an alternate application profile directory (for settings, logs,
etc.).
(default: default)

25
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

4 BC|Commander Application Layout

The default layout of the BC|Commander v11 application will look familiar to anyone who has used v10
BC|Commander. There are several new features, however, aimed at making an administrator's tasks
easier and generally improving the user experience.

Figure 2: BC|Commander v11 Default Layout

4.1 Menu Bar

The menu bar is at the top of the screen. It provides access to actions both at the application level and at
the individual BreadCrumb level as described below.
4.1.1 File Menu
Use the File Menu to access the following application features.
● New Tab – Creates a new view tab with the default layout.
● USB Flash Manager... – Opens in a new window. The USB Flash Manager is used to prepare a
USB flash drive to perform firmware upgrades on BreadCrumbs, or to zeroize BreadCrumbs.
● Export as Google Earth KML file... – Saves the current Mesh as a .KML file which shows
BreadCrumb locations and corresponding noise at each location when loaded into Google Earth.
● Open Snapshot... – Open a previously saved snapshot for viewing in virtual mode in

26
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

BC|Commander. No live BreadCrumbs will be displayed while in offline mode.

● Save Snapshot As... – Collects information from the selected BreadCrumbs and the Mesh
network for analysis and advanced troubleshooting by Rajant Corporation.
● Preferences... – Opens the Application Preferences dialog.
● Exit – Exits BC|Commander.
4.1.2 View Menu
Use the View Menu to change the view in the main application window, and to show or hide certain
panels.
● Filter – Show or hide the BreadCrumb filter bar.
● BreadCrumb Table Columns – Select which columns are visible in the BreadCrumb Table.
● Topology Layouts – Select the layout for the Topology View.
● BreadCrumb Table – Show or hide the BreadCrumb Table tab in the main view panel.
● Topology View – Show or hide the Topology View tab in the main view panel.
● Alerts – Show or hide the System Alerts panel.
● Tasks – Show or hide the Tasks panel.
● Details – Show or hide the BreadCrumb Details tab in the details panel.
● Peers – Show or hide the BreadCrumb Peers tab in the details panel.
● Clients – Show or hide the BreadCrumb Clients tab in the details panel.
● BCAPI Explorer – ( ) Examine the state, configuration and hardware
attributes of the selected BreadCrumb
● Save Layout As... – ( ) Save the current arrangement of a tab
● Apply Layout – ( ) Load and apply a saved layout or default layout
4.1.3 Mesh Menu
Use the Mesh Menu to access the following application features.
● Scan for BreadCrumbs – Instructs BC|Commander to immediately probe for BreadCrumbs on
the local network by issuing a Multicast DNS query.
● Triggers and Actions – This feature is not yet implemented.
● Live Mesh – When viewing a saved snapshot in virtual mode, this will remove the snapshot's
virtual BreadCrumbs from the display and return BC|Commander to a live Mesh display.
● Set Default Login Credentials... – Set the login credentials that BC|Commander uses to
automatically login in to BreadCrumbs when they are discovered.
● Clear Default Login Credentials – Clears the default login credentials. BC|Commander will no
longer automatically log in to BreadCrumbs when they are discovered.
● Analyze – Performs a link and configuration analysis against the current mesh and displays the

27
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

results in the current tab.

4.1.4 BreadCrumb Menu
Use the BreadCrumb Menu to access features for configuring BreadCrumbs. Some items in the
BreadCrumb menu may be disabled if no BreadCrumbs are currently selected. If one or more
BreadCrumbs are selected, the actions provided via this menu apply to all selected BreadCrumbs. Most
items in this menu can be accessed from a right-click menu in the Table View or Topology View.
● Configure... – Opens the BreadCrumb Configuration dialog.
● Reboot – Reboots the selected BreadCrumbs.
● Zeroize Keys / Restore Factory Defaults – Restores a BreadCrumb to its factory state, resets all
settings to their default values and destroys all security related keys and passphrases.
● Identify – Toggles the LED Identify state which causes a BreadCrumb's LED to blink all colors
in rapid succession.
● Filter on Selection – ( ) Creates and applies a filter to only display the
selected BreadCrumbs
● Instamesh Trace – Provides an interface to trace paths through the mesh.
● View Log – View the contents of a BreadCrumb's snapshot while in offline mode.
● Remove from Display – Removes the selected BreadCrumbs from the display. The BreadCrumbs
will reappear if they are rediscovered.
● Login... – Opens a Login window. Logs in to the selected BreadCrumbs with new credentials
provided, overriding previous login permissions. The user has the option to set the new
credentials as the Default Login Credentials for BC|Commander
● Logout – Logs out of the selected BreadCrumbs.
● Upload Firmware... – Opens a new window. Uploads a firmware file to the selected
BreadCrumbs. The user has the option to automatically begin installing the firmware as soon as
the upload is completed. The user also has the option to automatically reboot the BreadCrumbs
as soon as the installation is complete.
● Install Firmware – Installs firmware that has been previously uploaded to the selected
BreadCrumbs.
4.1.5 Help Menu
Use the Help Menu to access version information for the active BC|Commander session.
● Compute v11 IP Address... – Calculates a BreadCrumb's default IP address based on its serial
number, using the V11 method.
● Rajant Support → Create Memory Dump... – Generates a full memory dump of the
BC|Commander application and saves it to a local file. Rajant Support may ask the user for a
memory dump to help troubleshoot BC|Commander issues.
● About Rajant BC|Commander... – Displays version and license information.

28
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

4.2 Multiple Display Tabs

BC|Commander supports multiple display tabs. Each tab can display its own view and maintain its own
BreadCrumb selections independently of other tabs. This can make it easy for an administrator to
quickly switch back and forth between different views, or to open up a new tab to handle a separate task
without changing the view or selection on the current tab.
By default, BC|Commander has a single tab open. Additional tabs can be added by selecting New Tab
from the File menu, using the Ctrl-T keys, or by clicking the small tab with the New Tab ( ) icon. Tabs
can be renamed by right-clicking on the tab name. Close tabs by clicking on the Close Tab ( ) next to
the tab name.
When the Hide Single Tab option is checked in the Preferences dialog, and there is only one active tab,
the tabs, including the New Tab ( ) are not displayed, meaning the main view can be a little larger.
This can be important on a laptop or PC with a small screen.
4.3 Filters
Filters allow you to define a subset of BreadCrumbs and change what is displayed in the BreadCrumb
table and topology views based on one or more attributes of the BreadCrumbs in the mesh.
4.3.1 Filter Types
● Show Only – Display BreadCrumbs which match the supplied filter.
● Hide – Hide BreadCrumbs which match the supplied filter.
● Highlight – Emphasize BreadCrumbs which match the supplied filter.
4.3.2 Filter Attributes
You can filter based on one or more BreadCrumb attributes by using expressions in BCAPI Query
Language ("BQL"). The attributes available include the internal state of the BreadCrumb plus
configuration values and properties of the BreadCrumb hardware. BreadCrumb attributes are defined in
the Protocol Buffer Definitions section of the BCAPI developer documentation. For information on
writing BQL expressions for filters see Appendix BCAPI Query Language
4.3.3 Filter Input Field
The drop down list of the filter input field will display all available attributes (lower case) and
predefined shortcuts (start with upper case). As you type, the list of available choices is narrowed to
attributes or shortcuts which contain the text you entered. The matching is case-sensitive. The Filter
Input Field also provides validation as you type.

Figure 3: BreadCrumb Filter

29
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

4.3.4 Filter on Selection

The Breadcrumb menu and the context menu (accessed via the right mouse button) include the "Filter on
Selection" option which creates a filter string from all selected BreadCrumbs and executes the filter.
4.4 Dockable Panels
The different panels that make up the application layout are now dockable. This means that you can
arrange the application layout to suit your own needs. The main features of dockable panels are:
● Drag and drop – You can drag any tab to a new location by dragging and dropping. An outline
will appear that shows the new location of the tab.
● Combine or separate tabs – By dragging and dropping, you can combine individual tabs into a
single panel, or separate tabs into their own panels.
● Maximize Panel – You can maximize any panel by double-clicking in the tab area of the panel or
by clicking the Maximize button ( ). Double-clicking again or clicking the Normalize button
( ) will return the panel to its previous size and location.
● Show or Hide Tabs – Tabs can be shown or hidden by checking or unchecking the tab name in
the View menu. You can also hide, or close the tab by clicking the on the tab itself.
The application layout, including the current arrangement of the dockable panels is saved on shutdown
and reloaded when BC|Commander restarts. To return to the default layout, simply open a new tab.
4.5 Main View Panel
By default, the Main View Panel is located on the left side of the current tab and accounts for the
majority of the screen space. It contains tabs which display the BreadCrumbs in the Mesh either in the
BreadCrumb Table or the Topology View. The panel can be resized by picking the right side or the
bottom of the panel's frame and dragging it. Individual tabs in the panel can be shown or hidden by
checking or unchecking the tab name in the View menu. When all tabs in the Main View Panel are
closed or hidden, the whole panel will be hidden.
4.5.1 BreadCrumb Table
The BreadCrumb Table tab displays, in a table, all BreadCrumbs that BC|Commander is aware of,
except for those removed from the display or otherwise filtered. Each BreadCrumb corresponds to a
single row in the table, which will be filled in with data if BC|Commander has received a status update
from the BreadCrumb. See 5 BreadCrumb Table for a more detailed description of the BreadCrumb
Table. The tab can be shown or hidden by checking or unchecking BreadCrumb Table in the View
menu. You can also hide, or close the tab by clicking the on the tab itself.
4.5.2 Topology View
The Topology View tab displays a graphical representation of all BreadCrumbs that BC|Commander is
aware of, except for those removed from the display or otherwise filtered. Each BreadCrumb and
wireless client is represented by a single node in the display. Lines connecting nodes in the display
represent active Mesh or APT links between those nodes. See 6 Topology View for a more detailed
description of the Topology View. The tab can be shown or hidden by checking or unchecking Topology
View in the View menu. You can also hide, or close the tab by clicking the on the tab itself.
4.6 System Information Panel
By default, the System Information Panel is located at the bottom of the current tab which contains the
Alerts and Tasks tabs. Additionally, it can contain Trace and Analysis tabs. The panel can be resized by

30
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

picking the top of the panel's frame and dragging it. Individual tabs in the panel can be shown or hidden
by checking or unchecking the tab name in the View menu. When all tabs in the System Information
Panel are closed or hidden, the whole panel will be hidden.
4.6.1 Alerts
The Alerts tab displays a table showing any current warnings or errors reported by BreadCrumbs. The
tab can be shown or hidden by checking or unchecking Alerts in the View menu. You can also hide, or
close the tab by clicking the on the tab itself.
4.6.2 Tasks
Tasks are processes that are initiated by the user via BC|Commander. These include uploading and
installing firmware, zeroizing, and rebooting. The Tasks tab displays a table showing any current or
completed tasks on all BreadCrumbs on the Mesh, including tasks initiated by other BC|Commander
sessions. The tab can be shown or hidden by checking or unchecking Tasks in the View menu. You can
also hide, or close the tab by clicking the on the tab itself.
4.6.3 Trace
The Trace tab displays the results of an IMTrace action. The label on the Trace tab will display the
source and destination of the IMTrace using the format (source → destination). Multiple Trace tabs
may be present. Unlike the Alerts or Tasks tabs, Trace tabs cannot be hidden or shown. The tab is
automatically displayed when you initiate an IMTrace action. The information in a Trace tab is not
updated automatically. Pressing the "Trace Again" button will manually update the results by
performing another IMTrace. If the tab is closed, the trace information contained in the tab is discarded.
4.6.4 Analysis
Multiple Analysis tabs display mesh-wide analysis of configuration and operational information.
Several tabs are displayed when you select the "Mesh | Analyze" option from the main menu. Analysis
information is not updated automatically. To refresh the information, select "Mesh | Analyze" from the
main menu again. If an Analysis tab is closed, the information contained in the tab is discarded.
● Link Statistics – Provides Signal to Noise Ratio (SNR) and Cost information for all
BreadCrumbs in the mesh.
● Inconsistent Settings – Consolidates configuration settings for all BreadCrumbs in the mesh,
allowing you to easily detect inconsistencies.
● Noise Analysis – Displays noise information for all frequencies in use by BreadCrumbs in the
mesh.
● Frequency Overlap - ( ) Visualizes frequency overlap and spectrum spacing.
For more information see Chapter 11 BC|Commander Analysis
4.7 Details Panel
By default, the Details Panel is located on the right side of the current tab. It contains tabs which
display data about a single selected BreadCrumb, including general details, as well as peer and client
information. The panel can be resized by picking the left side of the panel's frame and dragging it.
Individual tabs in the panel can be shown or hidden by checking or unchecking the tab name in the View
menu. When all tabs in the Details Panel are closed or hidden, the whole panel will be hidden.
4.7.1 Details
The Details tab shows a high-level summary of the selected BreadCrumb's current status, plus additional

31
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

information for each of its radios and Ethernet interfaces. The tab can be shown or hidden by checking
or unchecking Details in the View menu. You can also hide, or close the tab by clicking the on the tab
itself.
4.7.2 Peers
The Peers tab shows a list of currently connected peers plus information regarding those connections
such as SNR, MAC address, and data rate. The tab can be shown or hidden by checking or unchecking
Peers in the View menu. You can also hide, or close the tab by clicking the on the tab itself.
4.7.3 Clients
The Clients tab shows a list of currently connected clients, plus information regarding those connections
such as SNR, MAC address, and data rate. The tab can be shown or hidden by checking or unchecking
Clients in the View menu. You can also hide, or close the tab by clicking the on the tab itself.
( ) The Peers and Clients signal strength column has been updated. In addition to
SNR (signal to noise ratio), signal strength is a useful statistic for validating an installation. Signal is
measured in dBm and values closer to zero indicate a stronger signal. For example, -25 dBm is a
stronger signal than -35 dBm.
4.7.4 BCAPI Explorer
The BCAPI Explorer tab offers a collapsible display of all available state, configuration and hardware
attributes of the selected BreadCrumb. This provides a much deeper and more detailed look at a
BreadCrumb's configuration (both saved and active) as well as its packet statistics, admin sessions, radio
information, tasks and alerts. The tab can be shown or hidden by checking or unchecking BCAPI
Explorer in the View menu. You can also hide, or close the tab by clicking the on the tab itself.

Figure 4: BCAPI Explorer

4.8 Status Bar

The status bar at the bottom of the application window displays information about the current state of
the application. The left hand side of the status bar displays the total number of BreadCrumbs that have
been discovered by BC|Commander. The center of the status bar will indicate when BC|Commander is
scanning for BreadCrumbs and indicate when BC|Commander is in Offline Mode. The right side of the

32
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

status bar displays the version of BC|Commander.

4.9 Saved Layouts
Saved Layouts allow you to visually arrange the UI and persist the arrangement for later or repeated
reuse. The Saved Layout can then be applied to a tab to easily recreate the desired arrangement.
Multiple layouts may be saved. Prior to BC|Commander 11.5 layouts were saved with the tab. If the tab
was ever closed the layout information was discarded.
By default, BC|Commander automatically saves the arrangement of panels, docks and other UI elements
for each tab the user has defined. The information saved for each tab includes the size, location and
visibility of panels and docks, visible columns, their order and sorting information for the BreadCrumb,
Peers and Client tables (Updated for 11.5) .
In the Topology View the position and scaling is saved for all Topology layouts and the Map Provider
(Street View, Aerial, Custom) is saved for the MapLayout ( ). In the BreadCrumb
Table view, the position and filter expressions for custom columns are saved. For both views, any
full-view filter expression can optionally be saved.
4.9.1 Create a Saved Layout
Arrange the UI to meet your needs
Select "File | Save Layout As" from the main menu.
Provide a unique name and click "Save"
When saving a layout, the "Save filter with layout" check box will be enabled if the current tab contains
a valid filter. If a filter is saved with the layout then it will be used when the Saved Layout is applied.

Figure 5: Create a Saved Layout

4.9.2 Apply a Saved Layout

Select "View |Apply Layout "

33
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Choose the name of the layout to use

Figure 6: Apply a Saved Layout

4.9.3 Overwrite an Existing Saved Layout

Select "File | Save Layout As" from the main menu.
Select an existing name from the list and click "Save"

4.9.4 Delete a Saved Layout

Select "File | Preferences"
Navigate to the "Tab Layout" preference
Highlight the Layout in the provided list and click "Remove"
Click "Save" at the top of the preferences window to save the modified preferences.

34
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 7: Saved Layout Preferences

Saved Layouts are implemented as templates which are manually applied to a tab during the "Apply
Layout" action. Once the layout has been applied to the tab, changes to the tab do not affect the Saved
Layout. Conversely changes to a Saved Layout will not be automatically propagated to any existing tab.

In addition to user-defined Saved Layouts, a "Default" layout is available which will return BCC to it's
default arrangement. Unlike the user-defined Saved Layouts, the "Default" template cannot be
modified.

Save Layouts are stored as part of the user profile, if you delete your profile all Saved Layouts will be
discarded.

35
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

5 BreadCrumb Table
The BreadCrumb Table shows all BreadCrumbs that BC|Commander is aware of, except those removed
from the display or otherwise filtered. Each BreadCrumb corresponds to a single row in the table, which
will be filled in with data if BC|Commander has received a status update from the BreadCrumb.

Figure 8: BreadCrumb Table

Right-clicking on a BreadCrumb (or one of several selected BreadCrumbs) will present the BreadCrumb
menu.
Multiple BreadCrumbs may be selected by holding down the shift key during selection (to select a
contiguous set of rows) or by holding down the ctrl key during selection (to toggle selection for
individual BreadCrumbs).
5.1 Managing Table Columns
Columns can be added to or removed from the table by right-clicking on the table header, expanding the
Add Column menu item and checking or unchecking the desired column. Columns will be added to the
right of the currently selected column. Columns can also be removed by right-clicking the table header
of the column to remove and selecting Remove Column. Multiple columns may be added or removed by
selecting "View | BreadCrumb Table Columns" from the main menu and selecting the column to add or

36
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

remove. Columns identified by a check mark will be visible in the table.

Figure 9: BreadCrumb Table - Add Column

Columns may be rearranged by dragging the heading of a column to move to a new position.
Any column may be sorted by single-clicking on its heading. Additional clicks on the heading will
toggle between ascending and descending sort. The sort order will be maintained as BreadCrumb status
updates continue to be received.
5.2 Creating Custom Columns
Custom BreadCrumb Table columns can be created by right-clicking any BreadCrumb Table column
title and selecting "Add Custom Column". In the Create Custom Column settings dialog, enter a name

37
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

for the column and a valid BCAPI Query Language ("BQL") expression based on BreadCrumb
attributes. BreadCrumb attributes include the internal state of the BreadCrumb plus configuration values
and properties of the BreadCrumb hardware. There are also many simple predefined short-hand filters
available in BQL for commonly filtered attributes.
The BQL expression in the Create Custom Column dialog shown below is a simple expression based on
an attribute of the BreadCrumb "state" object.

Figure 10: BreadCrumb Table - Add Custom Column

The available objects and attributes are a subset of those defined in the Protocol Buffer Definitions
section of the BCAPI developer documentation. For information on writing BQL expressions see
Appendix BCAPI Query Language
To edit a custom column, right-click on the column and select Edit Custom Column.
To remove a custom column, right-click on the column's title and select Remove Column.

38
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

6 Topology View
6.1 General Topology View Use
The BC|Commander topology view is a graphical display of the equipment and the connectivity of a
BreadCrumb wireless mesh network. The topology view supports several display options, including a
map view. The topology view is useful for real time monitoring of the connections between equipment
in the BreadCrumb network. Configuration of BreadCrumbs is also supported from the topology view.

Figure 11: Topology View Bullseye Layout

6.1.1 BreadCrumb Display

BreadCrumbs are represented in the topology view by an oval graphic. The name of the BreadCrumb is
displayed in the center of the oval. Selected BreadCrumbs are highlighted with a yellow ring. The color
of the oval indicates the status of the BreadCrumb. The table below describes each of the status modes.
BreadCrumbs can have several smaller icons under them to indicate additional information. See section
6.1.2 BreadCrumb Icons below for more information. Colored link lines between the BreadCrumbs
represent the wireless and Ethernet links between them. See section 6.1.4 Link Display below for more
information.

39
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Table 2: Color Codes for BreadCrumb Status

Status Color Status Mode

CONNECTED: BC|Commander is connected to and can administer the

GREEN
BreadCrumb.

REBOOT REQUIRED: A reboot is required to apply a configuration

ORANGE
change to the BreadCrumb.

YELLOW REBOOTING: The BreadCrumb is in the process of rebooting.

HANDSHAKING, CONNECTING, LOGGING IN, READING:

BLUE
BC|Commander is in the process of forming a connection.

DISCOVERED: BC|Commander has discovered the BreadCrumb, but is

GRAY
not yet connected to it.

CONNECTION FAILED, LOGIN FAILED, CONNECTION LOST:

RED
BC|Commander is not connected to a cached BreadCrumb.

6.1.2 BreadCrumb Icons

BreadCrumbs in the topology view can have several icons attached to them which indicate, at a glance,
important information to the user.

Figure 12: BreadCrumbs Icons

40
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Table 3: BreadCrumb Icons and Their Meanings

Icon Meaning

Access Point enabled, but no clients are connected.

Access Point enabled, with connected clients.

APT Master.

GPS Coordinates known.

Displayed while the user drags a BreadCrumb to a new location in the

MAP view to set manual GPS coordinates.

Displayed while the user drags a BreadCrumb out of the MAP view and
back into the Gallery to clear the manual GPS coordinates.

TRoIP Mix Master

TRoIP Client

Warning

Error

6.1.3 Client Display

The Topology View displays wireless clients that are associated with BreadCrumbs. Wireless clients are
represented by a rectangular graphic which displays the client's MAC address or Nickname. A solid line
between the wireless client and a BreadCrumb represents the AP connection. Clients can be shown or
hidden from view by selecting Show/Hide All Clients from the topology view's right-click menu.
6.1.4 Link Display
The Topology View displays the connectivity between BreadCrumb peers and the connectivity between
wireless clients and BreadCrumb equipment. Three connection types are represented in the topology
view:
● Wireless connections between BreadCrumbs.
● Connections between BreadCrumbs and wireless clients.
● Wired APT connections.
By clicking on the link lines in the Topology View, a window appears which displays the SNR, Wireless
Data Rate, and Cost of the wireless connection.

41
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 13: Link Display

Multiple links between BreadCrumbs can be shown as a single line by selecting Only Show Single Link
Per Peer from the topology view's right-click menu.
6.2 Topology View Context Menu
Right-click in a blank area of the Topology view (not on a BreadCrumb, client, or link) to bring up the
Topology view context menu. This menu includes the same items as Topology Layouts in the main View
menu, along with some additional commands.
● Default Layout – This layout disperses the BreadCrumbs over the available screen area.
BreadCrumbs repel each other to ensure there is no overlap.
● Circle Layout – BreadCrumbs are arranged in a circle.
● Bullseye Layout – Allows a user to see the number of network hops between BreadCrumbs. By
dragging a BreadCrumb into the center drop zone, BC|Commander will determine the minimum
number of hops to every other BreadCrumb on the network and arrange them from closest to
furthest. All BreadCrumbs in the first ring are 1 hop away, BreadCrumbs in the second ring are
2 hops away, and so on... BreadCrumbs outside the shaded rings are not connected to the center
BreadCrumb (either directly or indirectly).

The actual paths taken by traffic may differ from the paths shown in this view due to RF
Note and network conditions.

● Spring Layout – This layout disperses the BreadCrumbs over the available screen area.
BreadCrumbs will attract their peers but repel other BreadCrumbs that are not direct peers.
● Grid Layout – BreadCrumbs are arranged in a grid.
● Map Layout – BreadCrumbs are arranged based on latitude/longitude and displayed over a Map.
BreadCrumbs which do not have coordinates are arranged in a Gallery at the bottom of the
screen. Users can assign lat/lon by dragging BreadCrumbs from the Gallery onto the Map.
BreadCrumbs which have manually assigned coordinates can be dragged to different locations to
update their lat/lon positions, or can be dragged into the Gallery to clear their coordinates.
● Refresh – Refresh the current layout.
● Map Providers: MapQuest Street – Displays the online street view.

42
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

● Map Providers: MapQuest Aerial – Displays the online aerial (photographic) view.
● Map Providers: Save Offline Tileset – Opens the Save Offline Tileset dialog.
● Map Providers: Load Offline Tileset – Opens a file browser.
● Map Providers: Convert Image to Tileset – Converts a 2d map image into a tileset.
● Only Show Single Link Per Peer – When checked, show a single line between peers instead of a
line for each linked interface.
● Only Show Links for Selected BreadCrumb(s) – When checked, only show the links from the
selected BreadCrumbs to their peers. All other links are hidden.
● Show/Hide all Clients – Toggle the visibility of all wireless clients of the mesh.
● Zoom to Fit – Centers the view on the current layout and zooms to fit the available screen area.
6.3 Mouse and Keyboard View Controls
Right Click:
● Over BreadCrumb – Show BreadCrumb context menu. This will also select the BreadCrumb.
● Over Client – Show Client context menu.
● Over Nothing – Show TopoView context menu.
Single Left Click:
● Over BreadCrumb – Selects BreadCrumb.
● Over Link – Selects Peer Link and shows link information window.
● Over Client – Selects Client.
● Over Nothing – Clears Selection and link information window.
CTRL+Left Click:
● Multi-Selects either BreadCrumbs or Links.
● Removes an individual BreadCrumb from a selection of multiple BreadCrumbs.
Left Press and Drag:
● Over BreadCrumb – Moves BreadCrumb. This will also select the BreadCrumb.
● Over Nothing – Pans screen.
● Over Link Info Window – Click in the gray title bar area to move the window.
CTRL+Left Press and Drag:
● Move all selected BreadCrumbs as a set.
DoubleClick:
● On BreadCrumb – Opens the BreadCrumb Configuration Window.
● On Background – Zoom in.

43
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Scroll Mouse Wheel:

● Up – Zoom in.
● Down – Zoom-out.
● Shift+Up – Increase the size of the BreadCrumb icon.
● Shift+Down – Decrease the size of the BreadCrumb icon.
● Alt+Up - Increases the space between BreadCrumbs and individual link lines.
● Alt+Down - Decreases the space between BreadCrumbs and individual link lines.
Arrow Keys:
● Up Arrow – Zoom in.
● Down Arrow – Zoom out.
● Shift-Up – Pan up.
● Shift-Down – Pan down.
● Shift-Left – Pan left.
● Shift-Right – Pan right.
6.4 Offline Tilesets
The Save Offline Tileset feature allows you to save a collection of map tiles from an online map provider
to a file for use when offline.
To use this feature, center the map view in BC|Commander over the area you wish to save offline and
select Map Providers -> Save Offline Tileset from the right-click menu. This brings up the Save Offline
Tileset dialog.

Figure 14: Save Offline Tileset

The path field determines the path to the offline tileset. Zoom level is controlled by the minimum and

44
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

maximum zoom fields. These are expressed in terms of integer zoom levels, where 0 represents the
lowest zoom (entire world), and 18 generally represents the maximum zoom (street level).
BC|Commander will download all of the map tiles that overlap the visible area at all indicated zoom
levels. This will allow you to zoom in and out over the region while offline, but requires extra storage
space and time to download the tiles. As you modify the desired zoom levels, an estimate of how many
tiles will be downloaded and how much space they will consume is provided.

Be conservative in selecting desired zoom levels for offline maps. Selecting all
Warning available zoom levels for large regions can result in downloading more tiles than you
have space available to store.

When ready, click OK, and a progress dialog appears as the download completes. Once all tiles have
been downloaded, click Done.
This file can be loaded into the map view at any time by selectiong Map Providers -> Load Offline
Tileset from the right-click menu.

When viewing offline tiles, areas outside of the region downloaded will not be
Note available. In this case, it will fill in these areas using tiles from lower zoom levels,
which when enlarged will appear pixelated.

6.5 Convert Image to Tileset

In order to use a 2 dimensional image file in the Topology View's Map Layout, you must first convert
the image file into a tileset. From the View menu, select Topology Layouts, then Map Providers, then
Convert Image to Tileset. Alternately, you can open the Topology View context menu (right-click in the
Topology View) and select Map Providers, then Convert Image to Tileset. This will open up the Create
an Offline Tileset dialog box.

45
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 15: Create an Offline Tileset Dialog Box

Once the Create an Offline Tileset dialog box is open, follow the steps below:
1. Click the Select Image... button.
2. Browse to the location of the source image and open the file.
3. For the positioning algorithm to work, GPS coordinates for two reference points on the map must
be entered. To improve the accuracy of the positioning algorithm, choose two points close to
diagonally opposite corners of the network map in order to maximize their vertical and
horizontal separation.
4. Enter the Latitude and Longitude of the two reference points.
5. Finally, locate both reference points on the map. Click the Locate button for Location 1, position
the pointer over Location 1 on the map image and left click. A green dot surrounded by a circle
will appear on the map.
6. Repeat previous step for Location 2.
7. Specify a filename for the output file, or click the Choose button to browse for a tileset to update

46
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

(overwrite). Tileset files will end with a ".tileset" extension.

8. Click the Save Tileset button to create the tileset.
Once complete, you can use the tileset in the Map View by selecting Load Offline Tileset from the View
menu or the Topology View's context menu.

BC|Commander v11 mapping uses Mercator projection, which has a non-uniform Y axis
(latitudes are further apart at the poles). When importing non-Mercator maps, such as
Important maps using uniform grids, this could result in GPS positions being incorrect when
positioning BreadCrumbs. As a reference, the error is generally less than 10 m when the
reference points are up to 10 km apart at extreme latitudes.

6.5.1 Import v10 Map

You can easily convert a v10 GPS Map File into a tileset usable in v11. Instead of following the steps
outlined above, click the Import v10 Map button and browse to the location of the v10 map file with file
extension ".bcm". The map image and its reference points will be automatically imported into the fields
of the dialog box. Finish by specifying a filename for the output file and click the Save Tileset button.

47
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

7 Configuration Window
The configuration window is used for configuring BreadCrumbs as well as user preferences for the
application.

Figure 16: BreadCrumb Configuration Window

7.1 Configuration Window Features

7.1.1 Save / Reset / Cancel
The Save, Reset and Cancel buttons are located in the Configuration Window's title bar.
The Save button will commit any changes that were made to the settings. The save button will be
disabled if any of the changes results in validation errors.
In the BreadCrumb configuration window, a window will pop-up to indicate progress, success or failure
of a save. When a save fails due to a connection problem, you have the option to Retry the save when
the connection to the BreadCrumb is restored. You can also Reboot BreadCrumbs with successful saves,
or close the window without rebooting by clicking the Finish button.
The Reset button will undo any changes that have been made to the settings since the window was

48
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

opened.
The Cancel button will exit the configuration window without applying any changes to the selected
BreadCrumb(s).
7.1.2 Import / Export
The BreadCrumb config window provides a way to import settings to, and export settings from a
selection of BreadCrumbs. Saved settings can be imported to multiple BreadCrumbs simultaneously,
saving time and reducing the number of equipment configuration errors. The Import and Export buttons
are located on the Configuration Window's title bar.

Figure 17: BreadCrumb Configuration Export

While encryption keys, passphrases, and shared secrets cannot be imported or exported,
the choice to enable security features CAN be. After loading a configuration file that
Warning enables security features, remember to manually enter the necessary encryption keys,
passphrases or shared secrets BEFORE rebooting the BreadCrumb(s).

49
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

The Import / Export panel will open up on left-hand side of the configuration window. Enter or browse
for the desired directory. For Import, select from the list of available configuration files. For Export,
enter a filename (required) and name and comment for a new file, or select from the list of available
configuration files, if you wish to overwrite a file.
Use the check-boxes in the configuration panels to select which individual settings or categories of
settings will be included in the import or export action. Click Finish when you are done, or Cancel to
return to the configuration window without importing or exporting.

You can only import a configuration file to a BreadCrumb that matches the model (e.g.
Note ME4) and hardware configuration (e.g. 2409) of the BreadCrumb from which the
configuration was saved.

7.1.3 Settings Tree

Configurable settings are organized in a hierarchical tree, shown on the left hand side of the config
window. Some categories are divided into sub-categories. These categories can be expanded or
collapsed by clicking on the arrow to the left of the category name.
7.1.4 Settings Filter
At the top of the settings tree on the left-hand side of the configuration window is a blank text box
containing the prompt "type filter text". To quickly find a category or sub-category in the settings tree,
you can begin to type the name of the category and the settings tree will update to show only those
categories that match what you have entered. The filter is case insensitive and will support regular
expressions.
7.1.5 Settings Panel
Selecting a category will display the associated settings on the right hand side of the config window in
the settings panel. The settings will be grouped under one or more headings, and will show the settings'
current values.
7.1.6 Help Panel
When a specific setting is selected in the settings panel, help text is displayed in a panel in the lower
right hand side of the config window. This help text will give more information about the setting, its
active value, if it has one, and its default value, if it has one.
7.2 User Input and Validation
7.2.1 Text Field Validation
Values in text fields are validated as they are entered by the user. As the input changes, the background
color of the text field will change to alert the user to any validation problems that occur. There are three
background validation colors:
● Green: Indicates that the input value matches all of the validation rules.
● Yellow: Indicates that the input value is incomplete, but otherwise matches the validation rules.
● Red: Indicates that the input value does not match at least one validation rule.
For example, the validation rules for the raw key for WPA security define a valid entry to be 40
hexadecimal characters. As you start to type the key, the field will show yellow as long as the characters
being entered are hexadecimal. If the user makes a mistake and enters a non-hexadecimal character, the

50
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

field will immediately change to red. Once all 40 characters are entered correctly, the field will show
green.
7.2.2 General Validation
Any setting that is determined to be not valid will show either a warning ( ) or an error ( ) icon.
These icons will also show on any categories in the settings tree that contains that setting. A
configuration that contains an error will NOT be saved. The user must correct the offending value
before continuing or cancel the configuration. A configuration that contains a warning will still be
saved.

It is sometimes possible, during bulk configuration for example, for the Configuration
Window to open with existing warnings. You may correct these warnings if you wish,
Important but the config window will allow you to make changes to other settings and save the
config successfully without altering the warnings.

Clicking the blue "undo" style arrow ( ) next to any setting that has been changed will reset that
setting to its original value.
7.3 Configuring Preferences
To access the application preferences window, open the File menu and select Preferences, or use the
keyboard shortcut keys Alt-P.
7.4 Configuring BreadCrumbs
Configuring BreadCrumbs is an Admin level action, although some settings require Crypto Officer level
access to change. Make sure to supply at least Admin level login credentials to BC|Commander. To
access the BreadCrumb Configuration Window, select the BreadCrumb(s) you wish to configure in
either the BreadCrumb Table or the Topology View, then open the configuration window using one of
the following methods:
● From the BreadCrumb menu, select Configure.
● Use the keyboard shortcut keys Alt-C.
● Use the right mouse button to bring up the pop-up menu and select Configure.

Double-click on a single connected BreadCrumb to open the configuration window for

Tip that unit.

7.4.1 Bulk Configuration

You can now configure multiple BreadCrumbs at the same time, as long as they are all the same Model
of BreadCrumb (e.g. ME4) with the same radio hardware configuration (e.g. "2409") and are running the
same firmware version. Simply select multiple BreadCrumbs from the BreadCrumb Table or Topology
View and access the Configuration Window by the methods listed above.
During bulk configuration, some settings will be disabled. In some cases, this is because the field must
remain unique, like the IP address of a wired interface. In other cases, settings will be disabled because
they depend on other settings which differ on the selected BreadCrumbs.

51
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

7.4.2 No Reboot After Save

Some settings no longer require the BreadCrumb to reboot to make the new value active. Those settings
include BreadCrumb Name in the General settings and all of the InstaMesh and TRoIP settings. All
other settings still require a reboot. After you have saved your configuration changes, if none of the
changes requires a reboot, then the Reboot button in the pop-up window will be disabled and only the
Finish button is enabled. If any change requires a reboot, then both the Reboot and Finish buttons will
be enabled.

52
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

8 Preferences
The user can change certain application preferences by making changes to the Application Preferences
Dialog. The Preferences window works just like the BreadCrumb Configuration Window.

8.1 General
8.1.1 General: Hide Single Tab
When the Hide Single Tab option is checked, and there is only one active tab, the tabs, including the
New Tab ( ) are not displayed, meaning the main view can be a little larger. This can be useful on a
laptop or PC with a small screen. BC|Commander must be restarted in order for a change to take effect.
8.1.2 File Editing: File Editor
The name of the editor to use when viewing logs. Leave empty to let BC|Commander attempt to
determine the default file editor for your environment.
8.1.3 File Editing: Run File Editor in Terminal
Set to true if your file editor should be launched in a terminal window.
8.1.4 File Editing: Terminal
The name of the terminal to launch the file editor in, if enabled (such as xterm or gnome-terminal).

53
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

8.1.5 Highlighting: Enable Peer Highlighting

When selecting peers in the Peers Table, always highlight the peer BreadCrumb in the table and
topology views.
8.1.6 Highlighting: Peer Highlight Color
Color used to highlight peers in the table and topology views.
8.1.7 Highlighting: Filter Highlight Color
Color used to highlight filtered BreadCrumbs in the table and topology views.
8.2 Alerts
8.2.1 Alerts: Filtered Alert Codes
A list of alert codes that will be filtered from the Alerts Panel by default.
8.2.2 Filtered Alert Codes: Remove All
The Remove All button removes all of the entries from the Filtered Alert Codes list.
8.2.3 Filtered Alert Codes: Add
The Add button adds a new entry in the Filtered Alert Codes list.
8.2.4 Filtered Alert Codes: Remove
The Remove button removes the currently selected alert from the Filtered Alert Codes list.
8.3 BCAPI
8.3.1 BCAPI: General Update Interval (sec)
Minimum interval (in seconds) between status updates from BreadCrumbs. Valid values are 0-3600 (up
to 1 hour). If set to zero, the interval will be automatically set based upon the size of the network. This
setting will take effect following logout/login of all currently connected BreadCrumbs.
8.3.2 BCAPI: GPS Update Interval (sec)
Minimum interval (in seconds) between GPS updates from BreadCrumbs. Valid values are 0-3600 (up
to 1 hour). If set to zero, the interval will be automatically set based upon the size of the network. This
setting will take effect following logout/login of all currently connected BreadCrumbs.
8.4 BreadCrumb Discovery
8.4.1 BreadCrumb Discovery: Only Discover Manually Listed
BreadCrumbs
If set, BC|Commander will only discover BreadCrumbs listed in the Manual BreadCrumb Discovery
List. This can reduce network traffic and visual clutter.
8.4.2 BreadCrumb Discovery: Addressing Protocol
Address Protocol to use when communicating with BreadCrumbs. There are three protocol options to
choose from: IPv4, IPv6, or Both
8.4.3 BreadCrumb Discovery: Manual BreadCrumb Discovery List
The Manual BreadCrumb Discovery List allows you to manage known BreadCrumb IP addresses that
BC|Commander attempts to discover by unicasting to the specified address. If a BreadCrumb is found at
the specified address, it will be added to BC|Commander. Uncheck "Enable" to prevent scanning.

54
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

8.4.4 Manual BreadCrumb Discovery List: Import...

Opens a dialog box to select any file containing IP addresses to import into this table. Imported entries
will automatically be enabled.
8.4.5 Manual BreadCrumb Discovery List: Remove All
This removes all of the entries from the Manual BreadCrumb Discovery List.
8.4.6 Manual BreadCrumb Discovery List: Add
The Add button creates a new row in the Manual BreadCrumb Discovery List. Enter the IP address of
the target BreadCrumb, and check the Enable checkbox. Uncheck Enable to prevent scanning.
8.4.7 Manual BreadCrumb Discovery List: Remove
The Remove button removes the currently selected BreadCrumb IP from the Manual BreadCrumb
Discovery List.
8.5 Confirmation Dialogs
8.5.1 Confirmation Dialogs: Always Install After Firmware Upload
Set the "Automatically install firmware after upload" option to 'checked' in the Upload Image dialog
box.
8.5.2 Confirmation Dialogs: Always Reboot After Firmware Install
Set the "Automatically reboot after install" option to 'checked' in the Upload Image dialog box.
8.5.3 Confirmation Dialogs: Always Set Manual Location in Map View
Automatically set or update the Manual Location of non-GPS BreadCrumbs when dragging in the Map
View. Checking this will disable the confirmation dialog.
8.5.4 Confirmation Dialogs: Always Clear Manual Location in Map View
Automatically clear the Manual Location of non-GPS BreadCrumbs in the Map View when dragging to
the Gallery. Checking this will disable the confirmation dialog.
8.6 Topology View
8.6.1 Topology View: Background Color for Topology View
Color of the Topology View background using RGB hex values (000000 = black, FFFFFF = white). The
left two hex digits are a hex value for red from 00 (none) to FF (most). The middle two hex digits are the
green value. The right two hex digits are the blue value.
8.6.2 BreadCrumbs: BreadCrumb Size (pixels)
The size (in pixels) of the BreadCrumb icons in the Topology View.
8.6.3 BreadCrumbs: Wrap BreadCrumb Labels
Attempt to wrap BreadCrumb Labels when enabled.
8.6.4 BreadCrumbs: Character to Signify Wrapping
Character to indicate when to wrap the BreadCrumb label.
8.6.5 BreadCrumbs: Wrap at First, Last or All Occurrences
Choose between First Occurrence, Last Occurrence or All.
8.6.6 BreadCrumbs: Minimum Label Wrap Threshold
Only attempt to wrap labels with at least this number of characters.

55
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

8.7 Animation
8.7.1 Animation: Topology View Frame Rate (frames/sec)
The frame rate of the Topology View. Higher frame rates provide a smoother user experience, but use
more CPU.
8.7.2 Animation: Topology View Non-Focused Frame Rate (frames/sec)
The frame rate when the Topology View is visible but does not have focus.
8.8 Link Display
8.8.1 Link Display: Wired Link Color
The color of wired links which do NOT connect to an APT Master.
8.8.2 Link Display: Wired Link to APT Master
The color of wired links which connect to an APT Master.
8.8.3 Link Display: Unknown Link Color
The color of links which do not fall inside a defined range.
8.8.4 Link Display: Unselected Links
Transparency mask for non-selected links. Lower values make the links more transparent.
8.8.5 Link Display: Normal Links
Transparency mask for links when no BreadCrumbs or links are selected. Lower values make the links
more transparent.
8.8.6 Link Display: Selected Links
Transparency mask for links when BreadCrumbs or links are selected. Lower values make the links
more transparent.
8.8.7 Link Display: Links Coloring Scheme
Currently the only color scheme choice is Frequency Range.
8.8.8 Link Display: Colors for Frequency Ranges
The colors for Frequency Ranges table allows you to create and manage the colors of wireless links
displayed in the Topology view.
8.8.9 Colors for Frequency Ranges: Remove All
The Remove All button removes all of the entries from the colors table.
8.8.10 Colors for Frequency Ranges: Add
The Add button creates a new row in the colors table. The Start and End values of the frequency range
are shown in MHz. The color is an RGB hex value.
8.8.11 Colors for Frequency Ranges: Remove
The Remove button removes the currently selected range from the colors table.
8.9 Analysis: Link Statistics
8.9.1 Link Statistics: Good Cost Limit
The upper limit of a good cost. Cost values over this amount are candidates for improvement.

56
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

8.9.2 Link Statistics: Signal Too High (dBm)

The value, in dBm, which indicates the signal is too high. Greater / more positive values are worse.
8.9.3 Link Statistics: SNR Worst (dB)
The lower limit of a good to excellent SNR Range. Smaller values are worse.
8.9.4 Link Statistics: SNR Best (dB)
The upper limit of a good to excellent SNR Range. Links whose SNR exceeds this value are displayed
as "SNR High".
8.10 Analysis: Frequency Overlap
8.10.1 Guard Band
Amount of guard band (in MHz) for a 20MHz wide channel when checking for overlapping channels.
The size of the guard band automatically scales with channel width. If a 5MHz guard band is defined for
a 20MHz wide channel, the computed guard band for a 10Mhz channel would be 2.5Mhz.
8.11 Tab Layouts
8.11.1 Tab Layouts
User defined layouts. A layout is the arrangement of docks, tabs and panels in the user interface. In
addition a layout will include column visibility, ordering and sizing for tables. Layouts are created via
the File | Save Layout As menu.
8.11.2 Tab Layouts: Remove All
The Remove All button removes all of the entries from the Tab Layouts list.
8.11.3 Tab Layouts: Remove
The Remove button removes the currently selected entry from the Tab Layouts list.

57
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9 BreadCrumb Configuration
9.1 General
The General category includes several user definable settings which allow an administrator to organize a
BreadCrumb network for a specific application. These include a BreadCrumb Name, a Notes field, and
a list of one or more Groups. Other General Settings include LED Mode and GPS Location settings.
9.1.1 General: BreadCrumb Name
The BreadCrumb Name is an easily identifiable or readable name that you can give to your
BreadCrumb. The BreadCrumb Name is displayed on the BreadCrumb graphic in the Topology View
and can be displayed in the Table View. This field may remain blank.
9.1.2 General: Notes
The Notes field can be used for additional notes for the BreadCrumb. This field may remain blank.
9.1.3 Status LED: LED Mode
The LED Mode controls the default display state of a BreadCrumb's Status LED. There are four default
display states to choose from:
● On: Status LED displays errors, warnings, and link status.
● Off: Status LED remains off and does not display errors, warnings, or link status.
● Alerts Only: Status LED remains off unless there is an error or warning, in which case it
alternates between displaying the link status and the error or warning code.
● Off (switchable): Status LED remains off and does not display errors, warnings, or link status.

The status LED on LX, LX3 and ME3 may exhibit a short blink after a warm reset
condition that occurs due to system error or is initiated by the user (e.g., performing a
reboot command through BC|Commander, performing the Zeroize Keys and Restore
Warning Factory Defaults procedure). The LEDs on the JR cannot be turned off. The LED must
be physically masked (such as adding tape to the LED lens) to guarantee that no light is
emitted at any time.

Except for 'Off', each default display state has a corresponding alternate state. The BreadCrumb's LED
Configuration Switch can toggle back and forth between the default state and its alternate state. See the
BreadCrumb user guide for more information about the LED Configuration Switch.
The alternate display state for 'On' is 'Off'. The alternate display state for 'Alerts Only' is 'On'. The
alternate display state for 'Off (switchable)' is 'On'.
The 'Off' mode does NOT have an alternate state. The BreadCrumb's LED Configuration Switch will
NOT turn the LED on. This is to prevent accidental illumination during nighttime operations.
9.1.4 Location: Latitude / Longitude
The Latitude and Longitude fields are reserved for the position coordinates of a BreadCrumb. The data
must be entered as DDDMM.MMMMN where DDD indicates whole degrees, MM.MMMM indicates
minutes and N indicates direction. Example: "07530.4963W" indicates 75 degrees, 30.4963 minutes
West longitude.

58
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.1.5 Location: Altitude

The Altitude field is reserved for the installed altitude of the BreadCrumb. The altitude is referenced
from mean sea level. This field can be updated manually or automatically from a GPS receiver. When
using a GPS receiver, the reported Altitude is the altitude of the GPS receiver.
9.1.6 Battery: Battery Warning Threshold (minutes)
This setting applies only to BreadCrumb models that have an internal battery (ME3), and is unavailable
for all other BreadCrumb models.
When a battery is in use and the time remaining equals or is below the Battery Warning Threshold, a low
battery warning is reported both by the BreadCrumb's Status LED and in the System Alerts panel in
BC|Commander. The default value is 60 minutes for the ME3.
9.1.7 Battery: Battery Error Threshold (minutes)
This setting applies only to BreadCrumb models that have an internal battery (ME3), and is unavailable
for all other BreadCrumb models.
When a battery is in use and the time remaining equals or is below the Battery Error Threshold, a low
battery error is reported both by the BreadCrumb's Status LED and in the System Alerts panel in
BC|Commander. The default value is 30 minutes for the ME3.
9.1.8 Groups
This is a list of zero, one or more user defined Groups, which provides tags for BreadCrumbs that have
similar properties. For example, a Group may be assigned to a cluster of BreadCrumbs that operate on
the same radio channel, use the same ESSID, or are deployed in the same type of vehicle. This list may
remain empty.

Assigning one or more groups to a BreadCrumb does not apply any other settings to the
Important BreadCrumb. Only the values of the Groups list are changed.

9.1.9 Groups: Remove All

The Remove All button removes all of the entries from the Groups list.
9.1.10 Groups: Add
The Add button creates a new group in the Groups list.
9.1.11 Groups: Remove
The Remove button removes the currently selected group from the Groups list.
9.2 Network
The Network category includes the Mesh Network Name, Administration Port, the Enable DHCP Server
property and IP settings.
9.2.1 Network: Network Name
The Network Name is an easily identifiable or readable name that you can give to your mesh network.
This name is used, along with a Network Key and Crypto settings, to create a Network ID. InstaMesh
uses this Network ID to establish mesh links.
9.2.2 Network: Administration Port
The port that BC|Commander uses to communicate with the BreadCrumbs.

59
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.2.3 Network: Enable DHCP Server

BreadCrumbs are capable of running a DHCP server. When a BreadCrumb IP address mode is
Computed, the DHCP server on that BreadCrumb can be enabled. It is safe to run multiple BreadCrumb
DHCP servers on the same mesh.
9.2.4 Network: Enable SNMP Server
BreadCrumbs are capable of running an SNMP server. It provides data about the BreadCrumb over the
SNMP protocol.
9.2.5 IPv4: IPv4 Address Assignment Method
BreadCrumbs support four IP address assignment methods.
● DHCP: This mode enables DHCP client software on the BreadCrumb. Choosing this method
will disable the DHCP server on the selected BreadCrumb. The BreadCrumb will request an
address from a DHCP Server on the same segment as the BreadCrumb Network.
● Manually Assigned: In this mode, a static IP address can be assigned to the BreadCrumb.
● Computed (v11 method): This mode generates a unique IPv4 address based on the BreadCrumb
serial number. The advantage of the computed IP address mode is that a unique IP address is
automatically assigned to the BreadCrumbs without using a DHCP server, or manually
configuring a static IP address. Computed addresses are always in the 10.x.y.1 class A address
space.
● Computed (v10 method): This mode generates a unique IPv4 address based on the MAC address
of the data interfaces. The advantage of the computed IP address mode is that a unique IP
address is automatically assigned to the BreadCrumbs without using a DHCP server, or manually
configuring a static IP address. Computed addresses are always in the 10.x.y.1 class A address
space.

The computed IP address (v10) for a BreadCrumb can change if an interface is disabled
or replaced by Rajant while servicing a repair or becomes non-functional. By default
Important the seed for the BreadCrumb computed IP address is the MAC address of the WLAN0
interface. If WLAN0 is disabled, then the MAC address for WLAN1 becomes the seed
for generating the BreadCrumb Computed IP address.

9.2.6 IPv4 Manually Assigned Settings

When the IPv4 Address Assignment Method is set to Manually Assigned, the following IP settings are
enabled for user entry:
● IPv4: IPv4 Address: The manually assigned static IPv4 address.
● IPv4: Subnet: The manually assigned subnet.
● IPv4: Gateway: The manually assigned gateway address.
● IPv4: DNS: The manually assigned DNS address.

60
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.3 VLANs
BreadCrumb Firmware supports configurable Virtual LANs (VLANs) and Quality of Service (QoS)
control. The VLANs table allows you to create and manage the VLANs on a BreadCrumb.

To manage VLANs on the individual ports of the BreadCrumb, including the Local Port,
Important go to each port in the configuration tree and find its VLANs settings.

A VLAN is identified by a VLAN number, or tag, and is given a priority. A packet, or frame, that
belongs to a VLAN will have a special header that includes the VLAN's tag and priority.
9.3.1 VLANs: Remove All
The Remove All button removes all of the entries from the VLANs table.
9.3.2 VLANs: Add
The Add button creates a new VLAN in the VLANs table. A newly created VLAN is automatically
assigned the next available VLAN Number and a Priority of 0 (Best Effort). Any field in the VLANs
table can be changed at any time.
9.3.3 VLANs: Remove
The Remove button removes the currently selected VLAN from the VLANs table.
9.3.4 VLANs: VLAN Number
The VLAN number ranges from 0 to 4,095. Frames with a VLAN number of 0 are treated the same as
non-VLAN frames. VLAN numbers 1 and 4,095 are often reserved for management.
9.3.5 VLANs: Name
The VLAN Name is an easily identifiable or readable name that you can give to the VLAN. This field
may remain blank. It is displayed wherever VLANs are listed.
9.3.6 VLANs: Priority
The VLAN priority ranges from 0 to 7. The order of priorities, in ascending order, is: 1, 2, 0, 3, 4, 5, 6,
and 7. Non-VLAN frames are treated as priority 0. For a more detailed description of VLANs, see
http://en.wikipedia.org/wiki/VLAN.
9.4 Port Forwarding
Port Forwarding is used to pass data through a BreadCrumb Gateway port to allow connections into the
mesh via the gateway interface of a BreadCrumb in gateway mode.
9.4.1 Port Forwarding: Remove All
The Remove All button removes all of the rules from the Port Forwarding table.
9.4.2 Port Forwarding: Add
The Add button creates a new, blank rule in the Port Forwarding table. Any field in the Port Forwarding
Table can be changed at any time.

A new rule will not be validated until all values in the rule are valid, or until the rule is
Note removed.

61
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.4.3 Port Forwarding: Remove

The Remove button removes the currently selected rule from the Port Forwarding table.
9.4.4 Port Forwarding: Incoming Port Range
Incoming Port Range (low) and Incoming Port Range (high) specify the range of ports on the Gateway
port for the Port Forwarding rule. When the port range is one, simply specify the same port number for
both forward ports.
9.4.5 Port Forwarding: Forwarded Port Range (low)
This setting specifies the starting port for the designated BreadCrumb client. The forwarded port range
defined above will be mapped to an equivalently-sized range at the client beginning with this port
number.
9.4.6 Port Forwarding: Forward to Address
This address specifies the IP address of a client on the BreadCrumb network for the active port forward
rule. Data sent to the Gateway port are forwarded to the specified client on the BreadCrumb network.
9.4.7 Port Forwarding: Protocol Type
A port forwarding rule can be limited to either TCP or UDP, or it can be applied to both TCP and UDP.
9.4.8 Port Forwarding: Enable
This switch activates a Port Forwarding rule. It is possible to set up multiple rules, and then selectively
activate some of the rules.
9.4.9 Port Forwarding: Application
This is a user definable alias. It is a reference to the application that requires the active port forwarding
rule, and is helpful in reading the list of forwarded ports.
9.5 Capture
9.5.1 Capture: Enable Remote Capture
Enable the selected BreadCrumb as a remote wireless capture device for the RRADS.

The RRADS must have a wired connection to this BreadCrumb. While in capture
Note mode, the BreadCrumb will not participate in the Mesh.

9.5.2 Capture: Maximum Packet Size (bytes)

Incoming wireless packets that exceed the maximum size will be truncated.
9.5.3 Capture: Capture Listening Port
TCP listening port on the BreadCrumb. The RRADS connects to this port to receive the capture data.
9.6 Ports: Local
A BreadCrumb uses its Local port to communicate with administrative software like BC|Commander, as
well as to run DHCP and Gateway services. These services will not be available if VLANs are
incorrectly configured.
9.6.1 Local Port: Local Port Native VLAN
The Local Port can have at most one VLAN assigned to it as its Native VLAN. Choose from a list of
VLANs previously defined in the VLANs Table (see section 9.3VLANs above), or choose (none).

62
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Packets from the Native VLAN are always accepted by the local port. The Native VLAN of the local port
MUST match the VLAN, if any, being used to administer the BreadCrumb.
The local port will always accept untagged packets (packets that do not have a VLAN header). If you
assign a Native VLAN to the local port, the local port will only accept packets tagged with the Native
VLAN, as well as any untagged packets.

It is possible to be locked out of the BreadCrumb by misconfiguring VLANs. For

example, if the user assigns a Native VLAN to all Ethernet ports and APs, but does not
Warning assign a Native VLAN for the Local Port, the user will not be able to directly connect to
the BreadCrumb with BC|Commander. A USB or button Zeroize can erase all settings.

In the simplest case, the client (running BC|Commander for example) has no VLAN set and is connected
directly to a port on a BreadCrumb. That port must have the same Native VLAN as the BreadCrumb's
Local Port and must also be set to accept untagged frames. Packets sent from the local port into the
mesh will be tagged with the Native VLAN.
9.7 Ports: wlanX
There is a numbered "wlan" category (wlan0, wlan1, etc...) for each radio card in the BreadCrumb. The
category name in the settings tree will display the frequency of the radio card associated with the wlanX
(2.4 GHz, 900 MHz, etc...). Along with the wireless settings in this category, each radio will have four
(4) AP sub-categories (AP 0, AP 1, etc...) that contain ESSID and security settings.
9.7.1 Mesh: Enable Meshing
When Enable Meshing is checked, the radio card supports Mesh connections to other BreadCrumbs.
9.7.2 Mesh: InstaMesh Minimum Cost Difference (%)
A change in the cost of an InstaMesh connection triggers an update of the routing table and a reporting
event. InstaMesh Minimum Cost Difference is the minimum percentage change of the link cost which
must occur to trigger the update to the routing table and the reporting event.
Since updates to the routing table increase the load on the BreadCrumb and reporting events are loads on
the network bandwidth, this parameter can be used to set a higher Difference threshold which will
reduce the frequency of these events, and make more bandwidth available for other network
applications. Increasing the Minimum Cost Difference also increases how long it takes the forwarding
table to adjust to changes in cost.
9.7.3 Mesh: Enable Broadcast Receiver Address
This setting (formerly Use Broadcast Receive Address) allows a radio to send multicast Ethernet traffic
and MAC address discovery traffic using a single wireless packet sent to all peers. This setting is only
used when the BreadCrumb has at least as many peers as the Broadcast Receive Address Threshold (a
setting found in the InstaMesh configuration). Packets are sent without retries and at a static configured
802.11 data rate, the radio's multicast rate.
If it is not set, the broadcast receive address is never used and all multicast Ethernet traffic and MAC
address discovery is flooded to each mesh peer individually with wireless unicast packets that are sent
reliably.
Three scenarios are possible.

63
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

● If Enable Broadcast Receiver Address is not checked, multicast and MAC discovery Ethernet
packets will not be sent to the wireless broadcast receive address. They will be sent to each
wireless peer individually in a process known as flooding.
● If Enable Broadcast Receiver Address is checked and the number of peers is at least the number
set in InstaMesh: Broadcast Receive Address Threshold and each of their peers has at least this
number of peers, multicast and MAC discovery Ethernet packets will be sent from this radio to
the wireless broadcast receive address. All peers can receive this single packet.
● If Enable Broadcast Receiver Address is checked, but the number of peers is less than the
number set in InstaMesh: Broadcast Receive Address Threshold, multicast and MAC discovery
Ethernet packets will be sent as individually to each wireless peer in a process known as
flooding.
Flooding provides a more reliable method of transmitting multicast traffic. Flood packets are unicast
packets at the wireless level and are acknowledged. The sender will resend the data multiple times at
different data rates until the maximum retry is reached.
Using the broadcast receive address reduces the processor load on the BreadCrumb and reduces the
amount of wireless traffic required to send multicast and broadcast Ethernet traffic. If broadcast receive
address is not used, a multicast packet must be sent to each wireless peer one at a time. Each of these
transmissions must be acknowledged by the peer and may be retried. Conversely, if the broadcast
receive address is used, only one packet must be sent per radio. This packet is sent once per radio at the
Multicast Rate and is not acknowledged or retried.
For maximum performance in high distance and/or low density applications that use little multicast
traffic, turn off the Broadcast Receiver Address.
For maximum performance of applications that use multicast traffic, turn on the Broadcast Receiver
Address and increase the Multicast Rate to twice the required minimum actual throughput. If your
multicast application requires 3 Mbps, set the Multicast Rate to at least 6 Mbps. Make sure that the
InstaMesh setting Broadcast Receive Address Threshold is set to less than or equal to the number
BreadCrumbs in your mesh.
For maximum performance in dense networks, turn on the Broadcast Receiver Address. You may want
to increase the Multicast Rate to reduce the increased wireless bandwidth used by slow rate packets.

64
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.7.4 Radio: Regulatory Compliance Mode

There are two modes: Automatic and Manual.
● Automatic mode restricts the available channels and output power of the radio card to comply
with the wireless certification for the BreadCrumb by the relevant authority. Compliance to the
BreadCrumb wireless certification requires the use of the standard antennas that are shipped with
BreadCrumbs.
● Manual mode exposes all of the operating channels supported by the card and exposes the
maximum transmit power setting that the card is capable of. Access to these settings may be
needed to satisfy installation requirements. This determination and configuration must be made
by a qualified professional radio equipment installer.

By enabling Manual Regulatory Compliance Mode you acknowledge that modifications

to radio settings (including transmit power, channel frequency, bandwidth, and antenna)
Warning could void the user's license to operate the equipment (see, e.g., Code of Federal
Regulations Title 47, §15.21). Rajant strongly advises that radio configuration must not
deviate from the range(s) permitted by the applicable regulatory authorities.

9.7.5 Radio: Regulatory Domain

The Regulatory Domain (formerly Country Code) affects the Channel and TX Power settings for
Automatic mode. Designating a Regulatory Domain configures the radio card to operate within the
wireless certification limits of a particular country. Consult the BreadCrumb User Guides for guidance
on the wireless certification approvals for a BreadCrumb device.
9.7.6 Radio: Channel Number
The radio card channel and operating frequency can be set from this drop down menu. The available
channels are dependent on the Regulatory Compliance Mode and Regulatory Domain.
9.7.7 Radio: Channel Bandwidth
Normal 802.11 channels occupy 20 MHz of channel bandwidth (10 MHz on either side of the center
frequency). Some channels on some radios support a turbo mode that uses 40 MHz of channel
bandwidth for increased performance. Decreasing the channel bandwidth will decrease the maximum
throughput but may increase the range and reduce interference.
For supported radios, this drop down menu offers the following choices for bandwidth:
● 40 MHz (Turbo)
● 20 MHz (Standard)
● 10 MHz (Half rate)
● 5 MHz (Quarter rate)
● HT40+
● HT40-
● HT20
Please see Appendix A for more detailed information about which radios support alternate bandwidth

65
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

options.
9.7.8 Radio: Transmit Power
This sets the transmit power of the radio card. Settings are reported in dBm, and represent the transmit
power at the antenna port of the BreadCrumb, not including any antenna gain or cable loss. The
transmit power choices are dependent on the Regulatory Compliance Mode, the Regulatory Domain and
the Channel Number.
9.7.9 Radio: Multicast Rate
This is the Multicast Packet Data Rate. The default Multicast Rate is 1 Mbps. This is the lowest rate, but
it is the most dependable and will travel the farthest. This rate is only used on packets with a broadcast
receive address. (See Mesh: Enable Broadcast Receive Address)
9.7.10 Radio: Enable Compression
This enables hardware compression for the radio's wireless links. The support is negotiated with each
peer; both sides must have this feature enabled for the compression to work.
9.7.11 Radio: Antenna Selection
For radio cards with more than one antenna port, this setting identifies which antenna is used for 802.11
reception.
9.7.12 Settings: Maximum Peers
Maximum number of peers this radio will connect to simultaneously. If additional peers are available,
stale peers may be disconnected before the Radio Timeout is exceeded.
9.7.13 Settings: Range (meters)
This affects the timeouts that the radio uses in waiting for acknowledgments of packets. Generally this
setting is made a bit longer than the maximum distance expected to travel. Setting the range higher than
needed will reduce the performance when interference is present.
9.7.14 Settings: Radio Beacon Interval (ms)
This is the time in (ms) between 802.11 beacons. Increasing the beacon interval in very dense networks
may improve wireless communications. Setting the beacon interval > 400 ms may result in clients being
unable to associate.
9.7.15 Settings: Radio Timeout (sec)
This parameter sets the maximum allowable time in seconds following the receipt of a packet (including
an 802.11 transmission acknowledgment) from a BreadCrumb peer or wireless client or until a
connection times out.
9.7.16 Settings: Noise Level Warning Threshold
A warning will be issued if the noise floor of the radio exceeds this value. The warning will
automatically be cleared if the noise floor falls back below the threshold.
9.7.17 Settings: Noise Level Error Threshold
An error will be issued if the noise floor of the radio exceeds this value. The error will automatically be
cleared if the noise floor falls back below the threshold. If the noise floor exceeds both the Noise Level
Warning Threshold and the Noise Level Error Threshold, only the error will be issued.
9.7.18 Settings: Enable Packet Capture
Controls whether this radio will be used for wireless packet capture when Enable Remote Capture is set

66
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

to true.
9.8 Ports: AP X
There are four (4) AP (Access Point) sub-categories (AP 0, AP 1, etc...) for each wlanX port (radio card)
in the BreadCrumb. Each contains ESSID and security settings.
9.8.1 Access Point: Enable Access Point
When Enable Access Point is checked, the radio card supports connections to wireless clients. This
feature is disabled by default on v11 BreadCrumbs.
9.8.2 Access Point: ESSID
The 802.11 radios used in BreadCrumb products support the use of multiple ESSIDs. The BreadCrumb
can be configured with different security settings for each ESSID. This capability offers several
advantages.
● By supporting multiple access control schemes, legacy clients that do not implement the latest
access control methods, such as 802.11i, can connect through another method such as WEP or
WPA personal.
● An administrator can restrict wireless client access to VLANs in order to prioritize and/or isolate
traffic.
The ESSID is case sensitive, and special whitespace characters (such as tab, or line return) should not be
used. The length of the ESSID must be at least one character.
9.8.3 Access Point: Enable ESSID Broadcast
This setting determines whether or not beacons containing this ESSID are sent out. If Enable ESSID
Broadcast is left unchecked, wireless clients will need to be configured with the ESSID to connect
because they will not be able to discover it through scanning.
9.8.4 Access Point: Ignore Broadcast Probe Requests
This setting determines whether the AP should respond to Probe Requests that do not specify the SSID.
This field is ignored if Enable SSID Broadcast is not set.
9.8.5 Security: Security Mode
BreadCrumbs support eight (8) available security options: Open Network (no security), WEP, WPA
Personal, WPA Enterprise, WPA2 Personal, WPA2 Enterprise, WPA2 Personal Mixed or WPA2
Enterprise Mixed.

BC|Commander must be connected with "Crypto Officer" credentials to a BreadCrumb

Note in order to configure any security settings.

9.8.6 Security: WEP Key

The WEP Key must be either 10 Hexadecimal characters for 40-bit WEP or 26 Hexadecimal characters
for 104-bit WEP. You must enter the key twice to confirm. This is only enabled if the Security Mode is
set to WEP.
9.8.7 Security: WPA/WPA2 Key Type
The WPA/WPA2 Raw Key can be either a Raw Key or a Passphrase. This is only enabled if the Security
Mode is set to WPA Personal, WPA2 Personal or WPA2 Personal Mixed.

67
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.8.8 Security: WPA/WPA2 Raw Key

The WPA/WPA2 Raw Key must be 64 Hexadecimal characters. You must enter the key twice to confirm.
This is only enabled if the WPA/WPA2 Key Type is set to Raw Key.
9.8.9 Security: WPA/WPA2 Passphrase
The WPA/WPA2 Passphrase must be between 8 and 63 characters. You must enter the passphrase twice
to confirm. This is only enabled if the WPA/WPA2 Key Type is set to Passphrase.
9.8.10 Security: Cipher Suite
The WPA and WPA2 security modes support three possible cipher suite modes
● TKIP
● CCMP
● TKIP + CCMP
Temporal Key Integrity Protocol (TKIP) is implemented in both the WPA and WPA2 security modes.
Counter Mode with Cipher Block Chaining Message Authentication Code Protocol (CCMP) is
implemented in WPA2 security, and is supported in some WPA implementations. The Cipher Suite
mode should be set to correspond to the WPA/WPA2 Cipher mode that is supported by the client
devices. By default, TKIP is disabled. This setting is enabled if the Security Mode is set to any WPA or
WPA2 option.
9.8.11 Security: GTK Rekey Interval (seconds)
Specifies the time interval for creating a new WPA Group Temporal Key.
9.8.12 Security: Rekey When Station Leaves IBSS
A BreadCrumb network consists of two types of radio links: Mesh Links and Station Links. Mesh Links
are connections between BreadCrumbs. Station Links are links between a client device (such as a
laptop) and a BreadCrumb.
If checked, this will force the BreadCrumb to generate a new group key (shared with all associated
stations) whenever a station leaves the BreadCrumb. If not checked, the station that has left the network
will still have a current group key and will thus be able to decrypt some packets from the wireless
network of which it is no longer a member.
Turning this off will reduce the amount of management traffic required for very mobile clients and/or
BreadCrumbs.
9.8.13 Security: GMK Rekey Interval (seconds)
This parameter specifies the time interval for creating a new WPA Group Master Key, from which
Group Temporal Keys are derived.
9.8.14 Security: Radius Primary Server Retry Interval
The maximum time, in seconds, before transitioning from the primary Radius Server to a designated
secondary server.
9.8.15 Security: Accounting Primary Server Retry Interval
The maximum time, in seconds, before transitioning from the primary Accounting Server to a designated
secondary server.

68
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.8.16 Security: Radius and Accounting Servers

When WPA and WPA2 Enterprise security schemes are used, the IP address, the port, and shared keys of
the Radius and Accounting Server must be specified. BC|Comander can be configured to use a primary
server, and two secondary servers.
9.8.17 Radius and Accounting Servers: Port
Use this field to designate the port used by the Radius and Accounting server applications.
9.8.18 Radius and Accounting Servers: Shared Secret
Use this field to set the passphrase for the Radius and Accounting servers.
9.8.19 Radius and Accounting Servers: Address
Use this field to designate the IP address of the Radius and Accounting servers.
9.8.20 VLAN Configuration: Accept Untagged Packets
The Accept Untagged Packets setting applies to both incoming and outgoing VLAN traffic (packets
entering or leaving the mesh through a BreadCrumb's port). If this setting is checked, the port will send
and receive all untagged (non-VLAN) packets.
If the port also has a Native VLAN, any incoming untagged packet will be tagged with the Native
VLAN. Similarly, any outgoing packets tagged with the Native VLAN will be stripped of their VLAN
headers.
If Accept Untagged Packets is not checked, and the port has any VLANs assigned to it, then the port will
not send or receive any untagged packets.
9.8.21 VLAN Configuration: Accept Selected VLANs
The Accept Selected VLANs setting applies to both incoming and outgoing VLAN traffic (packets
entering or leaving the mesh through a BreadCrumb's port). If this setting is checked, the port will send
and receive all packets tagged with any VLAN that is checked in Selected VLANs list (see below).
9.8.22 VLAN Configuration: Accept Non-Selected VLANs
The Accept Non-Selected VLANs setting applies to both incoming and outgoing VLAN traffic (packets
entering or leaving the mesh through a BreadCrumb's port). If this setting is checked, the port will send
and receive all packets tagged with any VLAN that is NOT in the Selected VLANs list (see below),
including any VLANS that are not defined in the VLANs Table (see section 9.3VLANs above).
9.8.23 VLAN Configuration: Native VLAN (always accepted)
A port can have at most one VLAN assigned to it as its Native VLAN. Choose from a list of VLANs,
previously defined in the VLANs Table (see section 9.3VLANs above), or choose (none). Packets from
the Native VLAN are always accepted by the port. A packet from the Native VLAN will always be
stripped of its VLAN header before it is sent out of the port (out of the Mesh). When an untagged
packet is allowed into a port, the port assigns its Native VLAN to the packet (see Accept Untagged
Packets above). Generally, any port that has a Native VLAN should also apply the Accept Untagged
Packets setting.
9.8.24 VLAN Configuration: Selected VLANs
The Selected VLANs list is automatically populated with the VLANs defined in the VLANs Table (see
section 9.3VLANs above). Any of these VLANs which are checked are considered Selected for the
purposes of Accept Selected VLANs and Accept Non-Selected VLANs.

69
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.9 Ports: ethX

There is a numbered "eth" category (eth0, eth1) for each Ethernet port in the BreadCrumb. These
categories contain Ethernet and VLANs settings for each wired port.
9.9.1 Ethernet: Ethernet Mode
There are five possible Ethernet Modes which can be independently set for each BreadCrumb Ethernet
Port:
● Bridge+Mesh: (formerly Bridge) In Bridge+Mesh mode, the IP address of the Ethernet port and
the BreadCrumb are the same. Depending on the VLAN configuration, data sent on the wireless
network is available via the BreadCrumb Ethernet port.

Connecting a client to a BreadCrumb in Bridge mode can be a security risk as

the wired client can have complete access to wireless network. For
Important BreadCrumbs left unattended with no wired connections, it is recommended
that the Ethernet ports be disabled.

● Gateway: In Gateway mode, the IP address of the Ethernet port is different from the BreadCrumb
IP address. Outbound NAT is configured so that any Mesh traffic destined for the wired Ethernet
subnet appears to originate from the Ethernet port, and inbound traffic from the wired Ethernet
subnet must be sent through a forwarded port.
● Ingress Gateway: In Ingress Gateway mode, as in Gateway mode, the Ethernet port is configured
to exist on a different network than the BreadCrumb's other interfaces. NAT, however, is
configured in the direction opposite to that of Gateway Mode. Inbound traffic from the wired
Ethernet subnet appears on the MESH side to originate from the BreadCrumb, and outbound
traffic from the Mesh must be sent through a forwarded port.
● Mesh Only: (formerly APT Only) In Mesh Only mode, the Ethernet port will only make Mesh
(APT) connections to other other BreadCrumbs' Ethernet ports and will not allow raw Ethernet
traffic to enter the Mesh network, even if the BreadCrumb is the master of the APT connection.
BreadCrumbs connected directly to each other via Ethernet function as single node, effectively
treating this connection as an extremely fast wireless connection. This is accomplished using
Rajant's unique APT (Automatic Protocol Tunneling) technology.
● Disabled: When disabled, a BreadCrumb Ethernet does not operate. Data cannot be sent or
received with this port.
9.9.2 Ethernet: Alternate Gateway
When the wired interface is in gateway mode, it will have a separate IP address from the local interface
of the BreadCrumb. It will also set the local interface to respond to 10.0.0.1. Only one BreadCrumb in
a Mesh should have a given IP address. To prevent additional BreadCrumbs from using the gateway
address, set the Alternate Gateway to true.
Alternate gateway also changes the gateway and DNS server given out to be its own local address. This
can provide some load balancing so that clients that get their DHCP information from this BreadCrumb
will use it as their gateway.
9.9.3 Ethernet: Port Speed
The parameter sets the data rate of the BreadCrumb Ethernet port. For BreadCrumbs with 10/100

70
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Ethernet Ports, there are two available settings.

● Automatic: The port will auto-negotiate a data rate with a link partner.
● 10 Mbps: The port will only support a 10 Mbps connection with a link partner.
● 100 Mbps: The port will only support a 100 Mbps connection with a link partner.
● 1000 Mbps: The port will only support a 1000 Mbps connection with a link partner. Not all
BreadCrumbs support this setting.
9.9.4 Ethernet: Duplex Mode
There are three possible Duplex Modes which can be independently set for each BreadCrumb Ethernet
Port:
9. Automatic
10. Full Duplex
11. Half Duplex
9.9.5 Ethernet: Gateway Assignment Method
When the Ethernet Mode is set to Gateway or Ingress Gateway, the Gateway Assignment Method must
be specified. This affects how the IP address is assigned to the Ethernet port. There are two methods:
● DHCP: The IP address of BreadCrumb's Ethernet port will be assigned by a DHCP server on the
wired network.
● Manual: With this setting, you must manually designate the IP address of the Gateway Port.
9.9.6 Ethernet: IPv4 Manually Assigned Settings
When the Gateway Assignment Method is set to Manual, the following IP settings are enabled and must
be entered manually:
● Ethernet: IPv4 Address: This value specifies the IPv4 address of the Gateway Ethernet Port of
the BreadCrumb.
● Ethernet: Subnet: This is the netmask for the IP address. Enter the appropriate netmask for the
address class implemented on the wired network.
● Ethernet: Gateway: This field specifies the IP address of the gateway on the wired network.
● Ethernet: DNS: This field specifies the IP address of the DNS server on the wired network.
9.9.7 Ethernet: Request Fallback
When checked, the BreadCrumb will immediately indicate its willingness to be APT Master when it
reboots or its Ethernet port is reconnected to the Mesh network. When unchecked, the BreadCrumb will
wait for the duration of the APT Timeout before it indicates its willingness to be APT Master. It can still
become APT Master during this time period but will only be chosen by other slaves. A current master
will not yield to the newly connected node even if it would normally have a higher priority. The result is
that when an APT Master is restarted or otherwise disconnected and then reconnected to the Mesh
network, the new APT Master will not fallback to the old one.
9.9.8 VLAN Configuration
VLAN Configuration for Ethernet ports is exactly the same as for wireless ports. See sections starting
with 9.8.20 VLAN Configuration: Accept Untagged Packets for more information about these

71
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

settings.
9.10 Security
The Security category includes Mesh security settings and subcategories for BC|Commander login
credentials, Access Control with white and black lists, and BCAPI security settings.

BC|Commander must be connected to BreadCrumbs with "Crypto Officer" Credentials

Note in order to configure any security settings on the BreadCrumb.

9.10.1 Security: Packet Cipher

This is used to encrypt user data sent between BreadCrumbs in the mesh in order to provide protection
from eavesdropping. A number of algorithms and key sizes are available with different security and
performance characteristics. Note that if wireless clients are being used in the network then AP security
must also be enabled to protect from eavesdropping, but AP security is not a factor in determining
whether two BreadCrumbs will mesh.
9.10.2 Security: MAC Address Cipher
This is used to encrypt MAC addresses in user data sent between BreadCrumbs in the mesh in order to
provide protection from traffic analysis. A number of algorithms and key sizes are available with
different security and performance characteristics.
9.10.3 Security: Per-Hop Authentication Algorithm
This is used to verify the validity and integrity of packets at each hop through the mesh in order to
provide protection from traffic injection and MAC spoofing. A number of algorithms and key sizes are
available with different security and performance characteristics.
9.10.4 Security: Network Key
This is a master key set on a BreadCrumb from which other keys are derived. It may be set as a raw
256-bit key (64 hexadecimal characters) or as a passphrase of at least eight characters from which a
master key is derived. This key must be kept secret by the crypto officer.
9.10.5 Security: Network Key Sequence Number
This is an additional factor used to derive keys from the Network Key. By changing the Network Key
Sequence Number, which does not have to be kept secret, devices can be effectively rekeyed without
having to actually change the Network Key.
9.10.6 Security: Version 10 Network Encryption Key
The Network Encryption Key (NEK) is 256-bit and can be specified as a raw key or a passphrase. The
NEK is used by version 10 firmware to encrypt multicast and broadcast packets and to establish Mesh
connections. When InstaMesh: Enable v10 Compatibility is checked, the NEK must match the NEK of
the v10 BreadCrumbs in order to form Mesh connections. You must enter the key twice to confirm. The
default NEK for both v10 and v11 is:
0000000000000000000000000000000000000000000000000000000000000000.
9.10.7 Security: Version 10 Network Authentication Key
The Network Authentication Key (NAK) is 256-bit and can be specified as a raw key or a passphrase.
The NAK is used by version 10 firmware to authenticate other BreadCrumbs to establish Mesh
connections. When InstaMesh: Enable v10 Compatibility is checked, the NAK must match the NAK of
the v10 BreadCrumbs in order to form Mesh connections. You must enter the key twice to confirm. The

72
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

default NAK for both v10 and v11 is:

0000000000000000000000000000000000000000000000000000000000000000.
9.10.8 Security: FIPS-Equivalent Mode
If set, the BreadCrumb will enforce various rules as required to satisfy FIPS 140-2 requirements. Note
that this does not imply that the device or firmware has been validated under FIPS 140-2 unless
specifically indicated by Rajant.
9.11 ACL
The ACL (Access Control List) category allows you to select the ACL Mode and maintain a Whitelist
and a Blacklist for wireless clients.
9.11.1 ACL: ACL Mode
There are three access control modes available:
● No ACL: In this mode, all wireless clients are allowed to form AP connections with the
BreadCrumb.
● Whitelist: In Whitelist mode, only a wireless client with a MAC address that appears on the
Whitelist can form an AP connection with the BreadCrumb.
● Blacklist: In Blacklist mode, any wireless client with a MAC address that appears on the
Blacklist is forbidden from forming an AP connection with the BreadCrumb.
Each BreadCrumb in a network can only support one ACL mode at a time, but each BreadCrumb can
have a unique access control configuration.

While ACLs provide some control over the devices that may connect to a mesh, it
Important should not be depended upon as a security solution as MAC addresses are easily forged.

9.11.2 ACL: AP Only

Set to true to only apply the ACL to the Access Points on this BreadCrumb. Set to false to apply the
ACL to all packets that enter this BreadCrumb.
9.11.3 ACL: White List
Wireless clients that are specified on the White List are the only clients that can form an AP connection
with a BreadCrumb when that BreadCrumb is set to White List mode. Click the Add button to create a
new item in the White List table. Enter the MAC address of the device you wish to include on the list.
You may enter a comment here, but it is not necessary. If a client is added to this list from the context
menu in the client table or in the Topology view, this information will be filled in automatically.
To remove a client from this list, click on any field in that row and click the Remove button.
9.11.4 ACL: Black List
Clients that are specified on the Black List cannot form an AP connection with a BreadCrumb when that
BreadCrumb is set to Black List mode. Click the Add button to create a new item in the Black List
table. Enter the MAC address of the device you wish to include on the list. You may enter a comment
here, but it is not necessary. If a client is added to this list from the context menu in the client table or in
the Topology view, this information will be filled in automatically.
To remove a client from this list, click on any field in that row and click the Remove button.

73
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.12 BCAPI
The user credentials allow BC|Commander to log in to BreadCrumbs that have been discovered. In
order to change the passphrase for any of these accounts on a BreadCrumb, BC|Commander must be
logged in as "Crypto Officer" on that BreadCrumb. See section 3.1 BreadCrumb User Accounts for
more information about these login credentials.
9.12.1 User Credentials: Passphrase for "View" role
The view role grants read-only access to configuration and status. The view passphrase must be 8-63
characters in length. You must enter the passphrase twice to confirm.
9.12.2 User Credentials: Passphrase for "Admin" role
The admin role grants read access to configuration and status, write access to non-security-related
configuration. Permitted to execute non-security related commands such as “reboot” and “upgrade
firmware. The admin passphrase must be 8-63 characters in length. You must enter the passphrase twice
to confirm.
9.12.3 User Credentials: Passphrase for "Crypto Officer" role
The Crypto Officer, or co, role grants read/write access to all configuration, read access to status.
Permitted to execute all commands, set encryption keys, and set passwords. The crypto officer
passphrase must be 8-63 characters in length. You must enter the passphrase twice to confirm.
9.12.4 SSL/TLS Settings: Security Profile
This setting controls the SSL/TLS parameters of the BCAPI connection used by BC|Commander and
other BCAPI clients. There are six security profiles available:
● Suite B
● FIPS
● Android 4.x+
● Android 2.x+
● Compatibility
● Custom
9.12.5 SSL/TLS Settings: Certificate and Security Bits
See the gnutls manual for cryptographic key sizes. Section 6.11:
http://www.gnutls.org/manual/gnutls.html#Selecting-cryptographic-key-sizes. This is only enabled
when the BCAPI: Security Profile is set to Custom.
9.12.6 SSL/TLS Settings: Handshake Priority String
See the gnutls manual for handshake priority strings. Section 6.10:
http://www.gnutls.org/manual/gnutls.html#Priority-Strings. This is only enabled when the BCAPI:
Security Profile is set to Custom.
9.13 InstaMesh
InstaMesh® is a proprietary wireless networking protocol developed by Rajant Corporation. InstaMesh
is the communication protocol for the transfer of data between BreadCrumbs.
The InstaMesh category contains settings for configuring InstaMesh parameters. Changes to these
settings take effect immediately upon saving the configuration and do NOT require the BreadCrumb to

74
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

reboot.

Adjustment of InstaMesh settings should only be attempted by Advanced Adminstrators.

Important It is strongly recommended that Network Administrators contact a Rajant support
engineer for assistance with fine-tuning InstaMesh parameters.

9.13.1 General: InstaMesh DS (packets)

The maximum number of packets from a single source expected to be in transit within the mesh at any
given time.
9.13.2 General: InstaMesh DT (sec)
InstaMesh DT has multiple uses:
● The maximum amount of time expected for a packet to traverse the mesh during periods of
heavy traffic.
● DT is also used to limit how often a client is allowed to move from BreadCrumb to BreadCrumb
via 802.11 client association. If a client moves more often than once per DT, its packets are
dropped until the next DT interval.
● When the location of a destination is not known, a BreadCrumb must search for it. The first
search occurs immediately. A second search is not allowed until one second after the first search.
A third search is not allowed until two seconds after the second search. This time between
allowed searches continues to double until it reaches DT.
● DT is also used to limit the rate of broadcast ARPs when the ARP Proxy Timeout has been
reached. See 9.8.11 ARP Proxy Timeout.
9.13.3 General: Max TTL (1/100 sec)
Specifies the Maximum Time to Live in hundredths of a second for an InstaMesh packet.
9.13.4 General: GC Interval (sec)
The time interval at which the BreadCrumb checks for and removes stale routes, ARP proxy entries, and
BreadCrumbs. Set to 0 to disable all garbage collection. This will also disable all timeout calculations.
Ethernet ports will never enable (although APT will work).
9.13.5 General: Minimum GC Age (sec)
Sets the minimum time threshold for a stale route. Set to 0 to never age out MACs, ARPs, NDs, or
BreadCrumbs from their tables.
9.13.6 General: MAC Garbage Collection Threshold
Sets the maximum size of the MAC address table before garbage collection will be performed.
9.13.7 General: ARP Garbage Collection Threshold
Sets the maximum size of the ARP table before garbage collection will be performed.
9.13.8 General: BreadCrumb Garbage Collection Threshold
Sets the maximum size of the BreadCrumb table before garbage collection will be performed.

75
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.13.9 General: Neighbor Discovery Garbage Collection Threshold

Sets the maximum size of the Neighbor Discovery table before garbage collection will be performed.
9.13.10 General: ARP Proxy Timeout (sec)
The age of an ARP proxy entry that is considered to be stale. The ARP proxy saves the MAC address to
IP and VLAN mapping in all ARP requests and ARP responses on the network. Later broadcast ARP
requests from wireless clients, wired clients, or from the BreadCrumb itself are answered by the ARP
proxy directly if the request arrives with the timeout. If the broadcast ARP request arrives between the
timeout and twice the timeout, the broadcast ARP request is turned into a unicast ARP request. If further
broadcast ARP requests arrive after twice the timeout, the first such request is sent immediately. A
second broadcast ARP request that arrives after twice the timeout is only allowed one second after the
first. A third broadcast ARP request that arrives after twice the timeout is only allowed two seconds
after the second. This time between allowed broadcast ARP requests continues to double until it reaches
DT. Note, this limiting is done per IP address requested in the ARP. A single source may send many
ARP requests for different IP addresses. This may be limited through the Max Flood per Source
parameter.
IP networks that use static IP addresses may increase the ARP Proxy Timeout to a large value to reduce
unnecessary ARP traffic. Increasing the ARP Proxy Timeout may increase the time for a wired client to
discover that an IP address was reassigned from one node in the mesh to another.
While the information in unicast ARP requests is saved by the ARP proxy, unicast ARP requests are
always passed through the ARP proxy without alteration.
9.13.11 General: Enable Tactical Multicast
Check this setting to use Tactical Multicast for all multicast and broadcast traffic. Tactical Multicast
reduces the number of packets in the air for multicast and broadcast traffic by only forwarding packets to
BreadCrumbs that the previous sender of the packet can not see with good links. In other words, it only
forwards to the BreadCrumbs that didn't already hear the packet. This setting is enabled (checked) by
default
9.13.12 General: Tactical Multicast Coalesce Interval
The BreadCrumb will delay notification of changes to the tactical multicast encapsulator ID list by a
time that varies randomly from this setting to one less than twice this setting. This serves to combine
multiple changes that occur in rapid succession into one message. Use larger values for very dense
networks to reduce processing overhead. Use smaller values to make tactical multicast react more
quickly to network changes.
9.13.13 General: Cost Weighted Moving Average Interval
Decreasing the delay will make the cost react more quickly to changing conditions. Increasing the delay
will make the cost ride out temporary changes in the conditions more smoothly.
9.13.14 General: Excellent Quality Passing Lane Maximum Cost
The maximum cost to be considered part of the excellent quality passing lane. Connections in the
excellent quality passing lane get up to a +1 adjustment to their quality of service priority.
9.13.15 General: Good Quality Passing Lane Maximum Cost
The maximum cost to be considered part of the good quality passing lane. Connections in the good
quality passing lane get no change to their quality of service priority.

76
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.13.16 General: Fair Quality Passing Lane Maximum Cost

The maximum cost to be considered part of the fair quality passing lane. Connections in the fair quality
passing lane get up to a -1 adjustment to their quality of service priority. Connections with costs greater
than the fair quality maximum cost go into the poor quality passing lane. Connections in the poor
quality passing lane get up to a -2 adjustment to their quality of service priority.
9.13.17 General: Enable STP Filter
If connected to a network that is running spanning tree protocol (STP), this setting determines whether
STP packets are forwarded through the mesh. In general, these packets should be filtered (i.e. not
forwarded) in order to prevent conflicts with the InstaMesh built-in loop prevention.
9.13.18 General: Enable v10 Compatibility
If enabled, maintain compatibility with BreadCrumbs running v10 firmware. This feature is expected to
be used only during the upgrade process of a running mesh from v10 to v11 firmware or if a mixed
v10/v11 mesh network is to be used.
Compatibility with v10 BreadCrumbs also requires the following configuration of the v11 BreadCrumb:
● Access Point: Enable Access Point must be checked, and Access Point: ESSID must match the
primary ESSID of the v10 BreadCrumb on at least one radio of the same frequency. Version 10
firmware uses the BreadCrumb's primary ESSID instead of the Network Name.
● Security: Version 10 Network Authentication Key and Security: Version 10 Network Encryption
Key must match the NAK and NEK of the v10 BreadCrumb. Both v10 and v11 have the same
default values.

To prevent clients from connecting to enabled access points on the v11 BreadCrumbs
Note while in v10 Compatibility Mode, configure the ACL: ACL Mode to "Whitelist" and
leave the ACL: Whitelist empty.

9.13.19 General: Enable Peer Statistics Reporting

This setting turns on additional statistics reporting per mesh connection through BCAPI. It increases the
CPU load on the system.
9.13.20 Flood: Max Flood (packets/sec)
Flood packets are multicast or broadcast packets that can be sent to all BreadCrumb peers. Max Flood
(packets/s) sets the maximum number of packets that a BreadCrumb will receive and convert to flood
packets per second. If zero or blank, no limit is imposed. Setting this limit too low could cause ARP
requests to be dropped or BC|Commander's BreadCrumb discovery to fail.
9.13.21 Flood: Max Flood per Source (packets/sec)
Max Flood per Source (packets/s) sets the maximum number of packets received from a given source
MAC address that this BreadCrumb will convert to flood packets. If zero or blank, no limit is imposed.
Packets are still subject to the BreadCrumb-wide Max Flood (packets/s) limit. Setting this limit too low
could cause ARP requests to be dropped or BC|Commander's BreadCrumb discovery to fail.
9.13.22 Flood: Allow Bursting
True if flood limiting will allow bursting. With burst, multicast packets are counted wtihin a second.
Once the limit is reached packets are dropped until one second has passed. With bursting disallowed,

77
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

multicast packets are dropped when the rate of arrival is faster than indicated by the packets per second
configured.
9.13.23 Flood: Flood Limits
A list of flood limits to be applied to specific MAC addresses. A flood limit is applied to multicast
traffic destined for the mesh. Limits are given in packets per unit of time. Time is expressed in seconds
and microseconds. If allowBurst is set, the source MAC may send up to the number of packets noted in
the time limit. If allowBurst is not set, an inter-packet interval is calculated and packets are dropped that
exceed this rate.
9.13.24 Wireless: Connection Timeout (sec)
The period during which at least one packet must be received on a given interface in order to keep the
interface active. When an interface goes from active to inactive, it is removed from all routes and is no
longer displayed in BC|Commander. As soon as any data is received, the route becomes active again.
9.13.25 Wireless: Keepalive Interval (sec)
The interval between which keepalive packets are transmitted on idle interfaces in order to keep the
interface active.

Administrators may wish to increase the keepalive interval in dense mesh networks
where each BreadCrumb may have many peers. This may be desired in order to reduce
Important the total number of keepalive packets sent per second. Administrators must take care to
ensure that the associated Keepalive setting on other BreadCrumbs is consistent with
any large Keepalive Interval setting in order to prevent excessive connection timeouts.

9.13.26 Wireless: Broadcast Receive Address Threshold (peer/radio)

If the Broadcast Receiver Address is enabled for a given radio, the number of peers that radio must have
and that each peer reached through that radio must have in order to use the broadcast receive address.
For detailed information about this feature please refer to the Enable Broadcast Receiver Address setting
(in the Ports.. wlanX.. Mesh configuration).
9.13.27 Protocol Tunneling: APT Timeout (sec)
The APT Timeout is the number of seconds an APT peer will wait without receiving a keepalive
message or any other data before terminating the connection. It is also how long a BreadCrumb waits
when an Ethernet port is plugged in to find a BreadCrumb that should be the APT master. Increasing the
APT timeout decreases the risk of an APT connection getting dropped due to packet loss. It also
increases the time until an Ethernet port is ready at boot or on initial plug in. Finally, it increases the
time until a failover occurs when a master node is unreachable. The APT Timeout should be greater
than the APT Keepalive Interval.
9.13.28 Protocol Tunneling: APT Keepalive Interval (sec)
Every APT Keepalive Interval seconds, a BreadCrumb sends an APT ARP request out each Ethernet
port. It also sends an APT keepalive to each APT peer if no other data has been sent to that peer since
the last keepalive interval. The APT Keepalive Interval should be less than the APT Timeout.
9.13.29 Protocol Tunneling: APT Priority
The APT Priority is a field sent in the APT ARP messages. The BreadCrumb with the greatest APT
Priority becomes the APT master. If the APT priorities match, then the BreadCrumb with the greatest
Ethernet MAC address will become the APT master. Ethernet MAC addresses are compared byte by

78
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

byte. The MAC address with a greater value in the first byte that is different between the two addresses
is considered the greater MAC address.
In version 11, the default value of the APT Priority is 100. This allows you to configure a BreadCrumb
below the priority of the default.
9.13.30 Protocol Tunneling: Remote Protocol Tunneling Connection
Attempt Interval
The BreadCrumb will attempt each interval to connect to any Remote Protocol Tunneling hosts that
have not yet been connected to. "0" means no retries; the BreadCrumb will only try to connect to the
host once.
9.13.31 Protocol Tunneling: Remote Protocol Tunneling Host Names or
Addresses
A series of IPv4 addresses, IPv6 addresses or host names that are resolvable by a Dynamic Name
Service (DNS) server. The BreadCrumb will attempt to connect to each name simultaneously to form
Remote Protocol Tunneling connections. These connections use the APT timeout and keepalive
intervals. They are reliable and include retries. They can pass through routers / gateways and traverse
the Internet. Failed connection attempts or DNS resolution attempts are retried every RPT Connection
Attempt Interval.
9.13.32 Remote Protocol Tunneling Host Names or Addresses: Remove
All
The Remove All button removes all of the Groups from the Call Groups Slots table.
9.13.33 Remote Protocol Tunneling Host Names or Addresses: Add
The Add button creates a new Group in the Call Groups Slots table. A newly created Group is
automatically assigned the next available Group Number. Any field in the Call Groups Slots table can
be changed at any time.
9.13.34 Remote Protocol Tunneling Host Names or Addresses: Remove
The Remove button removes the currently selected Group from the Call Groups Slots table.
9.14 TRoIP
Tactical Radio over IP (TRoIP) is a BreadCrumb-headset combination for push-to-talk call groups. The
settings listed below allow the user to control the configuration and sound settings for each call group
member. Changes to these settings take effect immediately upon saving the configuration and do NOT
require the BreadCrumb to reboot.
9.14.1 TRoIP: Instance Count
The number of TRoIP sessions this BreadCrumb is capable of joining. Set to Left for a single session in
the left ear only, or Both for dual sessions (one in each ear).
9.14.2 TRoIP: Enable Local Audio Mixing
When checked, instead of going through a Mixmaster, all of the incoming audio streams of the
BreadCrumb's call group are mixed locally and played through the earpiece. All other BreadCrumbs in
the call group must also check Enable Local Audio Mixing.
9.14.3 TRoIP: Mixmaster Election Bias
Used to favor or handicap a BreadCrumb in Mixmaster elections. Positive numbers favor, negative
numbers handicap.
79
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.14.4 TRoIP: Enable Multicast Media Streaming

If Mixmaster is used, the Mixmaster sends the mixed RTP stream via multicast.
9.14.5 Audio: Enable Side Tone
Side tone allows the operator to hear their own voice in their earpiece while speaking.
9.14.6 Audio: Side Tone Gain
Controls the volume of the side-tone auditory feedback.
9.14.7 Audio: Enable Earpiece
Enables the TRoIP headset earpiece.
9.14.8 Audio: Earpiece Volume
Controls the earpiece volume.
9.14.9 Audio: Voice Activity Detection
If enabled, TRoIP will only transmit voice data when a voice is detected.
9.14.10 Audio: Voice Activity Threshold
Minimum volume of sound energy used in determining if voice data should be transmitted.
9.14.11 Audio: Enable Microphone
Enables the TRoIP headset microphone.
9.14.12 Audio: Direct Microphone to
When the Instance Count is set to Both, the microphone can be directed to either the Left Ear Session or
the Right Ear Session.
9.14.13 Audio: Microphone Gain
Control the gain on the microphone. Set to 1.0 for unity gain.
9.14.14 Audio: Auxiliary Audio Channel Available
If enabled, it assumes that audio from the aux device is being received on the right input channel.
9.14.15 Audio: Enable Auxiliary Audio Channel
Enables the Auxiliary Audio Channel. This can only be enabled when the Auxiliary Audio Channel
Available (see above) is enabled.
9.14.16 Audio: Direct Auxiliary Input to
When Enable Auxiliary Audio Channel is enabled, the auxiliary input can be directed to either the Left
Ear Session or the Right Ear Session.
9.14.17 Audio: Auxiliary Audio Gain
Sets the volume of the auxiliary audio input, when Enable Auxiliary Audio Channel is enabled.
9.14.18 Audio: Enable HID PTT Feature
If enabled, mic is muted unless the Human Interface Device signals a Push To Talk event
9.14.19 Audio: Raw HID PTT Protocol
If true, use the raw HID device, not the cooked input device
9.14.20 Audio: Double Tap Action
The Double Tap Action controls which action is performed on the microphone when the Push-To-Talk

80
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

button is tapped twice in rapid succession. There are three options:

● NONE: Double tapping the PTT button does nothing.
● SWITCH_MIC: The microphone input is toggled between the TRoIP sessions on the left and
right earpieces.
● STAY_LIVE: The microphone is set live and stays live without the user needing to hold the PTT
button. Tapping the PTT button again turns the microphone not live.
The Double Tap Action setting is only used if the headset configured for the BreadCrumb uses a
USB/HID PTT.
9.14.21 Audio: Audio Codec
The Audio Codec controls which audio encode/decode algorithm is used when transmitting TRoIP.
There are three supported options:
● PCM-µ (G.711 µ-law)
● PCM-A (G.711 A-law)
● G.729
9.14.22 Groups: Right Ear Call Group
Sets the slot number of the TRoIP call group to which the right ear is a member.
9.14.23 Groups: Left Ear Call Group
Sets the slot number of the TRoIP call group to which the left ear is a member.
9.14.24 Groups: Call Group Slots
Call groups can be defined and assigned to the left or right earpieces of the BreadCrumb's headset. The
microphone is directed to only one call group at a time. A default call group is created when a headset is
attached to a BreadCrumb.
9.14.25 Call Group Slots: Remove All
The Remove All button removes all of the Groups from the Call Groups Slots table.
9.14.26 Call Group Slots: Add
The Add button creates a new Group in the Call Groups Slots table. A newly created Group is
automatically assigned the next available Group Number. Any field in the Call Groups Slots table can
be changed at any time.
9.14.27 Call Group Slots: Remove
The Remove button removes the currently selected Group from the Call Groups Slots table.
9.14.28 Call Group Slots: Group Number
The number of the call group.
9.14.29 Call Group Slots: Group Name
The Group Name is an easily identifiable or readable name that you can give to the call group.
9.14.30 Call Group Slots: Join Group
Checking this will allow the call group to be assigned to the headset's left or right ear, and allow the
BreadCrumb to join the call group.

81
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

9.15 Industrial Applications

Modbus features are available on ME4 and LX4 BreadCrumb models and some newer models.
9.15.1 General: Modbus Mode
BreadCrumbs are capable of supporting MODBUS compliant industrial devices by proxying the
MODBUS/TCP protocol to a serial connected device.
9.15.2 Modbus: Modbus TCP port
TCP listening port on the BreadCrumb. Modbus controller connects to this port to receive capture data.
9.15.3 Modbus: Modbus Device Slave ID
Slave ID of the connected MODBUS/RTU device.
9.15.4 Modbus: Serial Port
Serial port device on the BreadCrumb connected to a MODBUS/RTU connected device.
9.15.5 Modbus: Serial Line Baud Rate
Serial line data rate for the BreadCrumb to communicate with connected MODBUS/RTU device.
9.15.6 Modbus: Serial Line Data Bits
Serial line data bits for the BreadCrumb to communicate with connected MODBUS/RTU device.
9.15.7 Modbus: Serial Line Parity Mode
Serial parity mode for the BreadCrumb to communicate with connected MODBUS/RTU device.
9.15.8 Modbus: Serial Line Stop Bits
Serial line stop bits for the BreadCrumb to communicate with connected MODBUS/RTU device.

82
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

10 Administrative Tasks
10.1 General Administration
10.1.1 Manually Adding BreadCrumbs
BC|Commander automatically discovers BreadCrumbs in a network, but also provides a manual
discovery process. This method is useful for configuring a BC|Commander session to administer
BreadCrumbs through a routed network that does not forward multicast discovery requests. Perform the
following steps to manually add a BreadCrumb to the network.
1. Open the Preferences dialog from the File menu and select Manual Discovery in the preferences
tree.
2. The Add button creates a new entry in the Manual BreadCrumb Discovery List. Enter the IP
address of the target BreadCrumb and check the Enable box.

As with automatically discovered BreadCrumbs, BC|Commander will use the Default

Note Login Credentials to try to connect to the target BreadCrumbs once they are discovered.

10.1.2 Upgrading BreadCrumb Firmware

There are two methods for upgrading BreadCrumb Firmware. The Over-The-Air (OTA) upgrade can be
performed from a remote location to multiple BreadCrumbs. The USB upgrade requires a properly
prepared USB flash drive to be connected directly to the BreadCrumb hardware. BC|Commander
provides command, control, and status updates for the upgrade process.
10.1.2.1 Over-the-Air (OTA) Firmware Upgrade
The OTA firmware update process is performed in two steps. The firmware is first uploaded to the
BreadCrumb, and then the firmware is installed on the BreadCrumb.

Figure 18: Image Upload Window

The following steps are required to perform the OTA firmware update:
● Select a BreadCrumb from either the Table View or the Topology View. Select multiple
BreadCrumbs to apply a firmware update to more than one BreadCrumb.
● Select Upgrade Firmware from the BreadCrumb Menu. A window will appear.

83
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

● Select Choose, and browse to the location of the firmware file.

● Select Upload to initiate the OTA update process.
Executing the previous steps will only transfer the firmware to the target BreadCrumb. There are two
methods to apply the new software to the BreadCrumb.
● Select the Automatically install firmware checkbox before selecting Upload.
● Select the Install Firmware option from the BreadCrumb menu.
A reboot is required to apply the new firmware to the selected BreadCrumbs.
10.1.2.2 USB Firmware Upgrade
BC|Commander is used to load BreadCrumb firmware onto a USB drive, and to configure the USB
drive for the Firmware update process.

Figure 19: USB Flash Manager

The following steps are required to prepare a blank USB drive for the BreadCrumb USB firmware
update process.
● Insert an empty USB drive into an available USB port.
A blank drive is recommended for this process. Having other information on the drive may or

84
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

may not cause a problem. For clarity, it is assumed that the USB drive is blank.
● From the File menu, select USB Flash Manager to open the USB Flash Manager window.
● Select choose, and browse to the path of the USB drive.
● Select Add File and browse to the path of the firmware file. This process can be repeated to
transfer multiple firmware files to the same USB drive.
● Files that have been transferred to the USB drive will be listed in the USB Flash Manager
window.
● Select the active checkbox for the firmware version that will be used for the USB firmware
update.
● Click the OK button to exit the USB Flash Manager.
● Safely eject the USB drive.

Important Only one firmware version can be active at a time.

10.1.2.3 USB Based Zeroize

The USB drive can also be used to initiate the zeroize command. To properly prepare a USB drive for
the USB-based zeroize feature, follow steps 1 through 3, listed above, skip to step 6 and choose "Zeroize
(Do Not Upgrade)" instead of choosing a firmware version.
10.2 Managing Clients
Features that are specific to managing wireless clients have been organized into a single menu. To
access this menu from the topology view, position the cursor over a wireless client and right click. This
menu can also be accessed by right clicking on a client listed in the Clients table of the Details panel.

10.2.1 Access Control

Use the Access Control feature to add a wireless client to either the Whitelist or the Blacklist ACL. This
feature does not change the active ACL mode. Only the ACL list is updated.
10.3 Troubleshooting Tasks
10.3.1 Taking Network Snapshots
A network snapshot is a data file used by Rajant support engineers to diagnose a BreadCrumb network.
The file contains detailed information about the peers, clients and connections of the network. Some of
the information in the file is not exposed to the user by BC|Commander. In native format, the network
snapshot file cannot be read by a text editor or spreadsheet program.
10.3.2 InstaMesh Trace
In v11.1.0, InstaMesh Trace has been integrated with the BreadCrumb table and the Topology View to
make tracing between BreadCrumbs easier. The InstaMesh Trace command is available from the main
BreadCrumb menu and from the BreadCrumb context menu. The user must select one or two
BreadCrumbs for the menu command to become enabled. The InstaMesh Trace command will open the
InstaMesh Trace dialog box.

85
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 20: InstaMesh Trace Dialog Box

In the InstaMesh Trace dialog box you can designate the following:
● Starting BreadCrumb: Where the trace will start. This dropdown list will contain all known
BreadCrumbs with the current BreadCrumb selected (in alphabetic order)
● Destination MAC/IP: Where the user is tracing to. If only one BreadCrumb was selected, the
dropdown list will be empty. If a second BreadCrumb is selected, its IP address will be
displayed. This field is editable and the user can provide an alternate IP address or a MAC. The
field will provide syntax validation when the user changes the value.
● Swap: If the user selected two BreadCrumbs, they can change the direction of the trace by
pressing the Swap button. This will swap the start and destination BreadCrumbs.
● Ping target before trace: Will cause the trace to issue a ping to the target. This will aid in route
discovery. The ping is only issued on the first hop.
● Start: Begins the trace.
● Cancel: Dismiss the dialog. No trace is performed.
10.3.2.1 Trace Result
Once a destination is chosen (or typed in), pressing Start will begin the trace. A trace tab will open at
the bottom of the screen. The tab will be named using the start and destination.

86
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 21: InstaMesh Trace Output

The trace output will be displayed as results are returned. The lower right corner of the trace window
contains two buttons.
● Trace Again: Will perform the same trace again.
● Cancel Trace: Will stop tracing after current hop completes.
10.3.2.2 Multiple Trace Tabs
You can execute and display multiple InstaMesh traces. Each unique trace will be shown in its own tab
at the bottom of the screen. Uniqueness is defined by the Name/Serial of the starting BreadCrumb and
the destination address. If you execute a trace for which there is an existing tab, the existing tab will be
reused. Duplicate trace tabs are NOT supported.
10.3.2.3 Trace Output
While the trace is running, output will be displayed in a text area in the trace tab. The text area should
automatically scroll when necessary to display the most recent results. If an existing tab is reused, the
tab should receive focus before results are displayed.
Unlike other tabs in the docking framework, when a trace tab is closed it cannot be reopened. When a
trace tab is closed, all information about the trace is discarded. Trace output can be copied to the
clipboard by highlighting the desired text and pressing CTRL-C.

87
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

The output of the trace has changed from BC|Commander v10 to reduce duplicate information and
enhance readability.
The first three lines of the trace output contain the following:
● Line 1: Start and destination provided by the user.
● Line 2: The Target IP computed by the first trace.
● Line 3: The Target MAC computed by the first trace.
Each Trace line contains:
● Hop Count
● Hop start BreadCrumb Name or Serial
● Hop destination MAC
● Hop destination BreadCrumb Serial and Name
● Connection information
10.3.2.4 Visual Trace
The Topology View will automatically display traced routes for the currently visible Trace tab. By
dragging a Trace tab to an alternate location, it is possible to display multiple traces at the same time.
The color button at the bottom of the Trace tab will allow you to color code each trace for easier
identification.

88
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

10.3.3 Compute v11 IP Addresses

In v11 firmware, default IP Addresses are computed based on the serial number of the BreadCrumb.
BC|Commander provides a utility allowing users to calculate IP Addresses based on serial number. The
Help | Compute v11 IP Address menu option will display a dialog where users can provide one or more
serial numbers and calculate the corresponding IP Addresses.

89
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

10.3.4 Create Memory Dump

A memory dump of a poorly running BC|Commander instance is invaluable to the development team for
tracking down excessive memory use, slow response times and high CPU usage. The Help → Rajant
Support → Create Memory Dump menu option will generate a file that can be analyzed by Rajant to
track down BC|Commander issues.

The generated file contains the entire memory space utilized by BC|Commander and
Important may be quite large.

10.4 Security-Related Tasks

10.4.1 Zeroize Keys / Restore Factory Defaults
The Zeroize Keys / Restore Factory Defaults option can be accessed from the BreadCrumb Menu only if
the user is logged in to the selected BreadCrumbs as Admin or Crypto Officer. Multiple BreadCrumbs
in a network can be zeroized simultaneously. Zeroizing will delete all security keys from the
BreadCrumb and restore all BreadCrumb setting to factory defaults.
A BreadCrumb can also be zeroized with a specially prepared USB disk. See USB Based Zeroize.
Most BreadCrumbs can also be zeroized via a button on the device. Please refer to your BreadCrumb
device manual for more information on this feature.

Do NOT turn off power or reboot a BreadCrumb that is being zeroized. An interruption
Warning to power during the zeroization process may result in the BreadCrumb being unable to
boot properly.

90
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

11 BC|Commander Analysis
As more BreadCrumbs are added to a mesh, maintaining an optimal configuration and detecting
incompatibilities and inefficiencies becomes more difficult. BC|Commander provides several analysis
tools to help detect problems with your configuration and mesh installation. The analysis tools generate
summary and detail data that can be viewed in BC|Commander and exported to PDF reports. The
exported PDFs also contain a snapshot of the analyzed data as an attachment. Unlike other portions of
BCC, analysis data is static and represents a "single point in time" view of the mesh. Updates received
by BCC after the analysis has started will not be captured in the resulting data.
To run or re-run all analysis tools, select Mesh | Analyze from the main menu. ( )
Each analysis panel provides a "Refresh" button in the lower right hand corner. Pressing "Refresh" will
re-run the displayed analysis using the current state of the mesh.
11.1 Configuration Settings
Configuration Settings analyzes all settings on all known BreadCrumbs. Settings which are the same
on all BreadCrumbs are added to the "Consistent Settings" table. Configuration values that differ are
added to the "Inconsistent Settings" table.
11.1.1 Inconsistent Settings Table
This table is comprised of three columns.
Setting Name – The fully qualified BCAPI name for the configuration setting
Value – The current value or <empty> if there is no value
BreadCrumbs – The count of BreadCrumbs where the setting has the specified value

Figure 22: Mesh Analysis: Inconsistent Settings

91
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

The table will contain one row for each unique name and value combination. To enhance readability the
setting name is only displayed once.
Selecting a cell in the "BreadCrumbs" column will expand the row and display all BreadCrumbs which
share the value in the "Value" column. Double clicking on the cell will allow you highlight and copy the
cell contents. Because of the ordered nature of the data, this table is not sortable.
In the following screenshot, 10 BreadCrumbs have a wireless interface set to channel 11, while 7
BreadCrumbs have an interface on channel 6, an so on.

Figure 23: Mesh Analysis: Inconsistent Settings w/ Selected Cell

11.1.2 Consistent Settings Table

This table contains columns for Setting Name and Value. These settings are the same for all known
BreadCrumbs. This table is sortable

92
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 24: Consistent Settings Table

11.2 Link Statistics

Link Statistics analyzes the quality of peer connections for all known BreadCrumbs. The display is
comprised of a Summary Table and a Detail table.

11.2.1 Link Statistics Summary Table

Summarizes and categorizes peer connections for each known BreadCrumb into 6 categories.
3. Signal High: Number of peer connection whose signal is considered high (default > -35 dBm)
4. SNR Good : SNR in a specific range (default 30 – 60 dB)
5. SNR Fair : SNR below the "Good" range (default < 30 dB)
6. SNR High: SNR at or above the "Good" range (default >= 60 dB)
7. Cost Good : Cost value at or below a specified value (default <= 10,000)
8. Cost Fair : Cost value above a specified value (default > 10,000)
Note: The parameters used to generate Link Statistics can be modified in User Preferences.

93
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 25: Link Statistics Summary Table

11.2.2 Link Statistics Detail Table

When you select a cell in one of the 6 category columns in the Summary Table, The detail information
for the selected category and selected BreadCrumb will appear in the Detail Table.
The first column in the table will contain the category values and the column header will change when
you select different categories.
A label identifying the BreadCrumb and the category will be displayed above the Detail Table.

Figure 26: Link Statistics Detail Table

94
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

11.3 Noise Analysis

Noise Analysis displays the noise for all frequencies in use by known BreadCrumbs. Noise can interfere
with the wireless signal leading to transmission errors and lowered performance. The causes of noise
include distance, obstructions, and various electronic devices.
Note: Lower (more negative) numbers are better. -95dBm is less noise than -90dBm
11.3.1 Noise Summary Table
Each row identifies an in-use frequency, it's channel, the number of radios/wireless interfaces which are
using the frequency and best/worst/average noise for all radios on that frequency.
Selecting a row will populate the detail table with information about each radio wireless interface

11.3.2 Noise Detail Table

For a given frequency shows all BreadCrumb interfaces which are using the frequency.

Figure 28: Noise Detail Table

Figure 27: Noise Summary Table

95
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

11.4 Frequency Overlap Analysis

Configuring radios to operate on different channels is not enough to ensure that they do not interfere
with one another. Depending upon a radio's bandwidth settings it may actually interfere with several
adjacent channels as well. This tool helps to ensure that BreadCrumbs are configured with sufficient
channel separation to ensure minimal self-interference.
The portion of the wireless spectrum used by a BreadCrumb's wireless interface is based on the
configured channel and bandwidth setting. To detect potential problems, "Frequency Overlap" analysis
computes the frequency range used by each wireless interface for all discovered BreadCrumbs and
compares the ranges. Each interface which overlaps another interface is listed in the resulting table.
Each row of the table represents a unique BreadCrumb/interface combination. The chart or charts on the
right display frequency ranges where overlap exists, allowing you to visualize the overlap and spectrum
spacing.

Figure 29: Frequency Overlap Analysis

Selecting a row (or rows) in the Overlap table will highlight the corresponding area in the appropriate
chart. Alternatively, clicking within a colored chart region will select all interfaces which are using the
selected frequency range. Clicking where frequency ranges overlap will select all interfaces where 2 or
more frequency ranges overlap. Selecting an empty space will remove all selections.

96
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Figure 30: Frequency Overlap - Selected

*Note: If one frequency range completely encapsulates another range, it is not possible to select the
encapsulated range by clicking on the chart.

A user defined amount of guard-band is displayed around the frequency ranges and is used in the
analysis to determine overlap. For instance if a 5 MHz guard band is defined, a minimum of 5 MHz
must separate two adjacent 20 Mhz wide channels for those interfaces to be considered as
non-overlapping (2.5 MHz is added to the upper and lower ends of each frequency range). The guard
band amount is configurable for a 20 MHz wide channel. For all other channel widths, the amount is
scaled proportionally. Therefore a 40 MHz wide channel will automatically be assigned a 10 MHz
guard band, while a 10 MHz wide channel will have 2.5 MHz of guard band. The guard-band area will
be displayed in a lighter shade of the color used to identify the frequency range.

The colors used to display frequency ranges are configurable and match the colors used to display peer
links in the Toplogy View. See Preferences | Toplogy View | Link Display | Colors for Frequency Ranges
to adjust.

97
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

12 BreadCrumb Network Security

12.1 Securing a BreadCrumb Network
A BreadCrumb network consists of two types of radio links: Mesh Links and Station Links. Mesh Links
are connections between BreadCrumbs. Station Links are links between a client device (such as a
laptop) and a BreadCrumb. In order for a BreadCrumb network to be secured against eavesdropping
and intrusion, it is necessary to configure both types of links properly.
12.2 Security Checklist
1. Are the Network Key, Network Key Sequence Number and Network Name configured properly on
all BreadCrumbs?
2. Are Packet Encryption, MAC Address Encryption, and Per Hop Authentication set correctly and
consistently across all BreadCrumbs?
3. If the mesh is not intended to have wireless clients, is access point functionality disabled on all
BreadCrumbs?
4. If access point is enabled, has the appropriate security level been applied for each ESSID on each
radio in each BreadCrumb?
5. Are there multiple access point security configurations on the same VLAN? (or on no VLAN at
all?)
6. Have MAC-based Access Control Lists been configured?
7. Have you prevented Network keys and any pre-shared keys from being transmitted over the air?
8. Have the Ethernet ports been disabled on all unattended BreadCrumbs?
12.3 Securing Mesh Links
Mesh Links are protected by the Network Key. This key is used to derive task-specific keys for various
operations within the BreadCrumb. One of the tasks is to ensure that all Mesh Link connections are
authorized. This check is always performed regardless of the various security settings available on the
BreadCrumb.
Other security tasks supported by the Network Key are:
● Packet Encryption encrypts all data sent between BreadCrumbs, providing privacy from
eavesdropping. Data is encrypted as it enters the mesh and is decrypted as it leaves the mesh.
No additional encryption/decryption is performed on a packet as it traverses intermediate
BreadCrumbs within a mesh.
● Per Hop Authentication cryptographically signs each packet sent between BreadCrumbs,
providing protection from data tampering, packet injection, and packet replay. This is performed
at each hop across a mesh.
● MAC Encryption encrypts the MAC addresses in the Ethernet headers of each packet. MAC
addresses are encrypted as packets enter the mesh and are decrypted at each hop in order to make
routing decisions, providing protection from traffic analysis attacks.
12.4 Securing Station Links
A variety of options is available for securing Station Links at varying levels of security. If your mesh
does not require wireless clients, the most secure option is to disable the access point functionality of the

98
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

BreadCrumbs altogether.
The security options for Station Links, approximately listed weakest to strongest, are:
● Open Network (no security)
● WEP (both 40-bit and 104-bit)
● WPA Personal (PSK and passphrase)
● WPA Enterprise
● WPA2 Personal Mixed (PSK and passphrase)
● WPA2 Enterprise Mixed
● WPA2 Personal (PSK and passphrase)
● WPA2 Enterprise
'Mixed' modes allow both WPA and WPA2 services to be provided simultaneously. These may be
desired when operating a network with older wireless devices that cannot be updated to WPA2 mixed
with newer devices capable of the stronger encryption.
Enterprise modes are provided by configuring BreadCrumbs to use an external Radius Server (not
provided by Rajant) for authentication. Up to three Radius Servers and three accounting servers may be
specified and assigned failover priority. The following EAP methods are supported:
● EAP-TLS
● EAP-PEAP/MSCHAPv2 (both PEAPv0 and PEAPv1)
● EAP-PEAP/TLS (both PEAPv0 and PEAPv1)
● EAP-PEAP/GTC (both PEAPv0 and PEAPv1)
● EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)
● EAP-TTLS/EAP-MD5-Challenge
● EAP-TTLS/EAP-GTC
● EAP-TTLS/EAP-MSCHAPv2
● EAP-TTLS/MSCHAPv2
● EAP-TTLS/EAP-TLS
● EAP-TLS
● EAP-PEAP/MSCHAPv2 (both PEAPv0 and PEAPv1)
● EAP-PEAP/TLS (both PEAPv0 and PEAPv1)
● EAP-PEAP/GTC (both PEAPv0 and PEAPv1)
● EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)
● EAP-TTLS/EAP-MD5-Challenge
● EAP-TTLS/EAP-GTC

99
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

● EAP-TTLS/EAP-MSCHAPv2
● EAP-TTLS/MSCHAPv2
● EAP-TTLS/EAP-TLS
12.5 Examples
The following examples illustrate some potential security problems created by bad configurations and
offer some solutions.
12.5.1 Unintended Transmission Of Cleartext
Suppose a mesh is configured by restoring all BreadCrumbs to their default settings and then enabling
Access Points and applying a WPA2 passphrase to each. A client associated to one BreadCrumb sends
data to another client associated to a different BreadCrumb.
Problem: Although the link from each client to its respective BreadCrumb is secure, the data
transmitted between BreadCrumbs in the mesh is completely unencrypted and easily visible to
eavesdroppers.
Solution: Set the Network Key, enable per hop authentication and packet encryption on each
BreadCrumb. This will ensure that the data is protected end-to-end between clients.
12.5.2 Unintended Admission To Network
Suppose a mesh is configured with WPA2-Enterprise authentication and CCMP encryption, and all
BreadCrumbs have a Network Key set properly and packet encryption and per hop authentication are
enabled. One BreadCrumb in the network has a second ESSID for guests configured on one of its radios
with no security applied. No VLANs are configured.
Problem: There is no barrier between the open "guest" ESSID and the otherwise secure network
protected by WPA2-Enterprise and Mesh link security. Anyone may associate as a guest and
communicate directly with any device available through the mesh. The resources intended to be
protected are not protected at all.
Solution: Disable the guest ESSID, or assign each ESSID to a different VLAN in order to isolate their
traffic from one another.
12.5.3 Unintentional Weakening Of Security
Suppose a mesh is configured with WPA2-Enterprise authentication and TKIP encryption, and all
BreadCrumbs have a Network Key set properly and packet encryption and per hop authentication are
enabled. A wireless camera is to be added to the network, but it only supports WEP encryption. A
second ESSID is added with WEP enabled so that the camera may provide encrypted video over the
network.
Problem: The WEP encryption on the second ESSID has become a weak link in the security scheme.
An attacker can ignore the strong TKIP encryption on the first ESSID and instead concentrate on the
easy-to-crack WEP encryption on the second ESSID. Cracking the WEP encryption would provide the
attacker with the same access as a WPA2-Enterprise client.
Solution: Don't run such a mixed network. If necessary, use an Ethernet-enabled camera connected to
the Ethernet port of any available BreadCrumb rather than a wireless camera that only supports WEP.
The per-packet encryption and per-packet authentication configured for the mesh will protect the video
from eavesdropping and tampering.

100
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

12.5.4 In Through The Ethernet

Suppose a mesh is configured with all access point functionality disabled, a Network Key properly set,
and packet encryption and per hop authentication enabled. The BreadCrumbs' settings are otherwise set
to factory defaults. The mesh in this scenario is used to connect multiple wired networks in several
locations. Many BreadCrumbs are left unattended in between these locations.
Problem: By default, a BreadCrumb's Ethernet ports are bridged into the mesh. An attacker needs only
to find an unattended BreadCrumb and connect to its Ethernet port for full access to the network.
Solution: Disable the Ethernet port on all BreadCrumbs left unattended.

101
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Appendix A: Radio Channels and Frequencies

Rajant's BreadCrumbs can contain up to four radios. 802.11g radios are used in the 900 MHz and 2.4
GHz bands, and 802.11a radios are used in the 4.8 GHz, 4.9 GHz and 5 GHz bands. The radios support
the channels and frequencies listed in the following tables for use in the United States and Canada.

Not all channels are allowed for use everywhere around the world. Check with the
Note corresponding wireless spectrum regulatory body to determine the subset of channels
authorized for use in your country.

Since the radios operate at different frequencies, you must be careful to use the correct
Caution type of antenna with each radio. As an example, a 2.4 GHz antenna will not work with
a 5 GHz radio and vice versa.

Table 4: 2.4 GHz Radio Channels and Frequencies

Channel Number Center Frequency (MHz)

1 2412

2 2417

3 2422

4 2427

5 2432

6 2437

7 2442

8 2447

9 2452

10 2457

11 2462

The default channel for a BreadCrumb 2.4 GHz radio is 11 (2462 MHz).

102
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Table 5: 5 GHz Radio Channels and Frequencies

Band Channel Number Center Frequency (MHz) Turbo Capability

149 5745 No

152 5760 Static Turbo

U-NII Upper Band
(5725 - 5825 MHz) 153 5765 No

/ 157 5785 No
ISM Band 160 5800 Static Turbo
(5725 - 5875 MHz)
161 5805 No

165 5825 No

The default channel for a BreadCrumb 5 GHz radio is 153 (5765 MHz). Some 5 GHz channels support
Static Turbo mode. In this mode, the radio binds two standard 20 MHz channels to obtain a wider
bandwidth 40 MHz channel. The end result is improved throughput and/or communication range for the
radio. Users should refer to the applicable compliance regulations in the intended region of deployment
for use of these frequencies.

Most 5 GHz antennas only support a subset of the 802.11a 5 GHz frequency channels
Caution the Rajant radio is capable of operating at. Before changing the channel of a 5 GHz
radio, verify that the channel is supported by the connected antenna.

103
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Table 6: 900 MHz Radio Channels and Frequencies

Channel Number Center Frequency (MHz) Channel Bandwidth

4 907 Half (10 Mhz)

5 912 Full (20 Mhz)

6 917 Full (20 Mhz)

7 922 Half (10 Mhz)

The default channel for a BreadCrumb 900 MHz radio is 5 (912 MHz). Half (10 MHz) and Quarter (5
MHz) bandwidth support is available on all 900MHz channels.

Channels 4 and 7, as well as Half (10 MHz) and Quarter (5 MHz) bandwidth may not be
Note supported on some BreadCrumbs with 900MHz radios.

104
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Table 7: 4.8 GHz Radio Channels and Frequencies

Channel Center Frequency Channel Center Frequency

Number (MHz) Number (MHz)

162 4810 175 4875

163 4815 176 4880

164 4820 177 4885

165 4825 178 4890

166 4830 179 4895

167 4835 180 4900

168 4840 181 4905

169 4845 182 4910

170 4850 183 4915

171 4855 184 4920

172 4860 185 4925

173 4865 186 4930

174 4870

The default channel for a BreadCrumb 4.8 GHz radio is 164 (4820 MHz). If a second 4.8 GHz radio is
present, it's default channel is 184 (4920 MHz). If a third 4.8 GHz radio is present, it's default channel is
174 (4870 MHz)

105
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Table 8: 4.9 GHz Radio Channels and Frequencies

Channel Number Center Frequency (MHz) Channel Bandwidth

5 4942.5 Quarter (5 Mhz)

10 4945.0 Half (10 Mhz)

15 4947.5 Quarter (5 Mhz)

20 4950.0 Full (20 Mhz)

25 4952.5 Quarter (5 Mhz)

30 4955.0 Full (20 Mhz)

35 4957.5 Quarter (5 Mhz)

40 4960.0 Full (20 Mhz)

45 4962.5 Quarter (5 Mhz)

50 4965.0 Full (20 Mhz)

55 4967.5 Quarter (5 Mhz)

60 4970.0 Full (20 Mhz)

65 4972.5 Quarter (5 Mhz)

70 4975.0 Full (20 Mhz)

75 4977.5 Quarter (5 Mhz)

80 4980.0 Full (20 Mhz)

85 4982.5 Quarter (5 Mhz)

90 4985.0 Half (10 Mhz)

95 4987.5 Quarter (5 Mhz)

The default channel for a BreadCrumb 4.9 GHz radio is 20 (4950.0 MHz).

106
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Appendix B: Error and Warning Codes

All possible BreadCrumb error and warning codes are listed below:
JR, JR2, LX, LX3, LX4, ME3, ME4 Firmware Upgrade Codes (1*)
11 Flash image file does not exist.
12 Current flash image version is greater than versions of files found on USB drive.
13 No flash image files found.
14 Unable to mount USB drive.
15 Unlocking of /dev/mtd0 failed.
16 fconfig for SetFailsafeBoot failed.
17 Unlocking of /dev/mtd0 failed.
18 fconfig for SetMainBoot failed.
19 Copying of zImage failed.
111 Copying of ramdisk failed.
112 FIS directory update of ramdisk failed.
113 Copying of etc failed.
114 FIS directory update of /etc failed.
115 Copying failed.
116 Flash unbundle failed.
117 Version information in flash file name and breadcrumb-buildinfo.conf do not match.
1171 Platform information in flash file name and breadcrumb-buildinfo.conf do not match.
118 Untar failed.
119 FIS directory update of kernel failed.
120 Failed to mount /etc.
121 Failed to unmount /etc.
122 In Failsafe mode, but no USB drive detected.
123 BreadCrumb will be in failsafe mode and unable to communicate with other BreadCrumbs after
next reboot.
124 Failed to suspend bcconfigd.
125 Failed to set boot path to next image.
126 Failed to erase end of next file system image.
127 Failed to copy file system image.
128 Failed to checksum file system image.
129 Failed to create directory for next file system image.

107
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

131 Failed to mount next file system image.

132 Failed to create directory for settings.
133 Failed to copy current settings to next file system image.
134 Failed to unmount next file system image.
135 Failed to copy Rajant init image.
136 Failed to copy bootloader image.
137 This flash image may not be installed onto this BreadCrumb.
138 Failed to copy failsafe file system.
141 Error retrieving flash file.
142 The version you are installing does not support the configured Packet cipher
143 The version you are installing does not support the configured MAC Address cipher
144 The version you are installing does not support the configured Per-hop Authentication algorithm

Self-Test Codes (3*)

31 Hardware configuration not set. Factory initialization required.
311 InstaMesh license update required.
32 BreadCrumb has been zeroized.
321 BreadCrumb is being zeroized.
33 Radio not detected. Turn the unit off, and then back on. If the problem persists, contact technical
support.
333 Low Battery.
334 Gas gauge not initialized. To initialize, please fully charge unit while turned off.
34 Cannot read /dev/nand6 information, or cannot resize or format /dev/nand6.
36 Hardware monitor missing.
37 Failed to configure ethernet port.
38 Resetting radio due to error.
381 Noise floor threshold exceeded.

FIPS Codes (4*)

41 FIPS power-on self-tests failed.
411 FIPS DRBG power-on self test failed.
412 FIPS DRBG continuous test failed.
413 FIPS DRBG health check failed.
414 Kernel integrity check failed.

108
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

415 Filesystem integrity check failed.

416 FIPS USB test vector data missing.
417 FIPS invalid configuration.
42 Mixed SecNet/Non-SecNet configuration.
43 Rekeying error.
44 Rekeying error.
45 Rekeying error.
46 Rekeying error.
47 Rekeying error.
48 Rekeying error.
49 Rekeying error.
431 Rekeying error.
432 Rekeying error.
433 Rekeying error.
434 Rekeying error.
435 Rekeying error.
436 Rekeying error.
441 Status override CPLD feature not available (wrong CPLD version).

Fatal Codes (5*)

51 InstaMesh fatal error.
52 Hostapd fatal error.
521 HT40 operation not permitted on channel
522 IEEE 802.11 TKIP countermeasures initiated
53 CVM fatal error.
54 Fatal error.
541 Software error
55 Low memory - automatic reboot scheduled.
56 APT peer bridge settings do not match

Battery Gas Gauge Codes (6*)

61 Battery gas gauge i2c device could not be found.
62 Incorrect gas gauge revision 1 EEPROM settings.
63 Incorrect gas gauge revision 2 EEPROM settings.

109
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

64 Incorrect gas gauge revision 3 EEPROM settings.

65 Unknown gas gauge revision.
66 Incorrect ME3 gas gauge revision 0 EEPROM settings.
67 Internal battery charger disabled.
Other Codes (7*, 8*, 9*)
71 Host flapping detected.
72 Critical I2C failure.
73 Invalid channel configured.
74 Bad factory configuration.
91 Invalid SSL Handshake Priority String:

110
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Appendix C: Ports and Protocols

Table 9: Ports and Protocols

Service From To Protocol

224.0.0.224, port 35057 (UDP IPv4 multicast);

Ephemeral port on IPv4 UDP
FF02::1, port 35057 (UDP IPv6 multicast);
BC|Commander
BreadCrumb IPv4 or IPv6 addresses, port 35057 IPV6 UDP
workstation
BreadCrumb (UDP IPv4 or IPv6 unicast)
Discovery
Ephemeral port on BC|Commander workstation IPv4 UDP
BreadCrumb IPv4 or
(UDP IPv4 or IPv6 unicast); FF02::1, port 35057
IPv6 address, port 35057 IPv6 UDP
(UDP IPv6 multicast) at BreadCrumb startup

Ephemeral port on IPv4 TCP

BCAPI BreadCrumb IPv4 or IPv6 addresses, port 2300
BC|Commander
(BC|Commander) workstation (default) IPv6 TCP

APT Discovery -
BreadCrumb ethernet ARP (see
v10 Compatibility interface, raw ethernet FF:FF:FF:FF:FF:FF (raw Ethernet broadcast)
note below)
Mode

BreadCrumb ethernet
APT Discovery -
interface's IPv6 link-local FF01::1, port 2210 (UDP/IPv6 multicast) IPv6 UDP
v11 address, UDP port 2210

APT - v10 BreadCrumb ethernet BreadCrumb ethernet interface IPv6 link-local

Compatibility interface IPv6 link-local address port 2210 for the service listener, IPv6 UDP
Mode address, ephemeral port ephemeral port for data flow

BreadCrumb ethernet BreadCrumb ethernet interface IPv6 link-local

APT - v11 interface IPv6 link-local address port 2210 for the service listener, IPv6 UDP
address, ephemeral port ephemeral port for data flow

BreadCrumb IPv4 or BreadCrumb IPv4 or IPv6 address, SCTP port

IPv4 or IPv6
RPT IPv6 address, ephemeral 2210 for the service listener, ephemeral port for
SCTP
port data flow

TRoIP Audio RTP BreadCrumb IPv4 IPv4 multicast address 225.0.0.1-225.0.2.255 port
IPv4 UDP
Traffic address, ephemeral port 24680

Remote Packet Remote Packet Capture

BreadCrumb configured TCP port (default:5825) IPv4 TCP
Capture Client (typically RRADS)

Note: APT Discovery in v10 Compatibility Mode may be truncated by some third-party equipment.

111
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Appendix D: BCAPI Query Language

Overview
BCAPI Query Language aka BQL is a custom expression language build in to BC|Commander for the
purpose of efficiently querying BreadCrumb state. Filtering BreadCrumbs in the BreadCrumb Table or
Topology View is possible using expressions that return true or false, and general expressions allow for
defining custom columns in the BreadCrumb Table. The data structures that the expressions operate on
are a subset of the Protocol Buffer definitions in the BCAPI Developer's Guide.
When a filter expression is entered above the BreadCrumb Table or Topology view, the filter will be
evaluated against each BreadCrumb that BC|Commander has discovered. The expression will "match"
if it evaluates to true for a particular BreadCrumb. By default, in full table or topology filtering,
BreadCrumbs that match the filter will remain visible, while those that don't will be hidden.
Alternatively, you can opt to highlight or hide matches. Custom column filters will instead display the
filter result for each visible BreadCrumb in the BreadCrumb Table.

Syntax
Let's start with an example:
config.general.name == "fry"

This specifies a simple filter that tests whether the BreadCrumb's configured name is exactly equal to
"fry".

Objects/Structures/Fields

The value "config" in the previous example is one of several top-level data objects to which you have
access. The complete set of top level objects is shown in the following table.

Table 10: BQL - Top-level Data Objects

Object Description
Active BreadCrumb configuration, as defined in Config.proto in the BCAPI Developer
config
Guide.
state Dynamic BreadCrumb state, as defined in State.proto in the BCAPI Developer Guide.
Static BreadCrumb model information, as defined in ModelDatabase.proto in the BCAPI
model
Developer Guide.
math A custom math object with operations usable on Repeated Fields

The structures exposed by config, state, and model objects are hierarchical in nature. The value
"general" in the preceding example is a structure defined within the "config" object, while the value

112
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

"name" is string field defined within the "general" structure.

Field Types

The following primitive types are recognized for API fields:

Table 11: BQL - Field Types

Field Type Description

boolean Can be one of true or false.

A homogenization of the various numeric types available in Java and Protocol
Buffers, on which the filter language is based. This includes integers, long integers,
number
and single/double-precision floating point values. The expression language will
automatically convert between numeric types as needed.
Character strings. When specifying string literals, they must always be quoted as in
string
the initial example of "fry".
Java arrays, Java collections (such as lists and sets), ans Protocol Buffer repeated
Repeated Field
fields

Logical Combinators

You can combine multiple filters using simple logical operators as shown here:

state.system.running && ( !model.gps || state.system.reboot )

Here; &&, ||, and ! map to logical AND, OR, and NOT respectively, as is commonly the case in
mainstream programming languages such as C or Java. By default, ! has highest priority, followed by
&&, and then ||. Precedence can be overridden with parentheses, as shown.

In this example, all fields being tested are booleans, so no == operator is required. The following two
examples are equivalent.

state.system.running
state.system.running == true

113
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Logical Comparators

The original example used == to test for exact equality. Other comparators are available:

Table 12: BQL – Logical Comparators

Comparator Description

== Is exactly equal to.

!= Is not exactly equal to.

~ ~= =~ Matches against a Java-compatible regular expression.

!~ !~= !=~ Negated regular expression match.
Case-insensitive match that works on strings (to find a substring) and Repeated
contains
Fields (to find an element). A contains B means look for B inside A
like A synonym for contains
Case-insensitive match that works on strings (to find a substring) and Repeated
in
Fields (to find an element). A in B means look for A inside B
Less than. For strings, this means "comes before" according to standard
<
case-insensitive lexicographic ordering.
<= Less than or equal to.
Greater than. For strings, this means "comes after" according to standard
>
case-insensitive lexicographic ordering.
>= Greater than or equal to.

Repeated Fields
In addition to Structures and Fields, the API supports the concept of lists, referred to as Repeated Fields.
A Repeated Field is simply a list of structures. The lists are homogeneous, meaning all items in a list
will be of the same structure type.

In the BCAPI, "state.wireless" is a repeated field of State.Wireless structures (as defined in State.proto).

By default, filters using repeated fields will be tested against every element present. The filter will match
as a whole if it matches any individual element. For example…

state.wireless.range > 1000

114
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

...is a valid filter. "state.wireless" is a repeated field since there can be several wireless interfaces
present on a single BreadCrumb. This expression will test whether the range is greater than 1000 for
each wireless interface in turn and succeeds if the test passes for at least one repeated field.

Controlling Repeated Field Behavior

You can change the way matches over repeated fields are combined into a final result. The following is
equivalent to the above…

state.wireless[any].range > 1000

…but now we explicitly specify "any" behavior, which is otherwise the default. Alternatives include…

state.wireless[all].range > 1000

…which says that all wireless interfaces must have range greater than 1000, and…

state.wireless[none].range > 1000

...which says that no wireless interfaces can have range greater than 1000.

Nested Filters

There may be cases where you want more control over which elements of a repeated field are considered
by the filter. The following only tests the range for interfaces with high noise, completely ignoring the
rest:

state.wireless[any : noise > -80].range > 1000

In this example, we've included a nested filter at the level of state.wireless. This filter excludes any
wireless entries that don't match, before applying the outer filter on range. The final result will be true if
any of the high-noise wireless entries have a range greater than 1000.

Within a nested filter, fields must be specified starting at the scope where the filter is defined. In the
example above, this is why we specified "noise" rather than "state.wireless.noise"... because the nested
filter is defined at the level of state.wireless, and is thus restricted to only access fields at that level or
below.

115
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Repeated Field Operations

The custom math object provides a group of operations that can be used on Repeated Fields. (including
lists, sets and arrays) and several standalone operations are also available.

Table 13: BQL – Repeated Fields Operations

Keyword Description

math.average Returns the average of the elements (numeric types only).

math.count Returns the count of elements.

math.min Returns the minimum element (numeric types only).

math.max Returns the maximum element (numeric types only).

math.sum Returns the sum of the elements (numeric types only).

math.unique Converts an existing repeated field into a set-based one.

list Builds a list

set Builds a set (unique and unordered)

Note: the Repeated Field operators contains, like and in were defined with Logical Comparators

Examples:

The average noise over wireless interfaces:

math.average(state.wireless.noise)
The number of wireless interfaces present
math.count(state.wireless)
The set of unique peer macs over all wireless interfaces
math.unique(state.wireless.peer.mac)
Build a list containing the elements shown in the parentheses
list("one", "two", "three")
Returns true if the platform is "lx4" or "me3"
state.system.platform in set("lx4", "me3")

116
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Built-In Filters

For convenience, a collection of common filters has been pre-defined and made available under
short-hand names. As a convention, pre-defined filters are named using a Noun.Verb format. The noun
defines what the filter pertains to, and the verb defines the action. These are as follows:

Table 14: BQL – Built-In Filters

Filter Description
Peers.hasAny Has any peers on all interfaces
Peers.hasAtLeast(count) Has at least 'count' number of wireless peers on all interfaces.
Groups.nameContains("text") Has at least one group that contains "text" in its name.
Reboot.isNeeded Needs reboot is active.
Reboot.inPastHour Has rebooted in the past hour.
Reboot.inPastDay Has rebooted in the past day.
Alerts.hasErrors Has any active error-level alerts.
Alerts.hasWarnings Has any active warning-level alerts.
APT.isMaster Is currently an APT master on any interface.
APT.isSlave Is currently an APT slave on any interface.
Clents.hasAny Has any connected AP clients.
Clients.hasAtLeast(count) Has at least 'count' number of connected AP clients.
Returns the number of connected AP clients. This is not a
Clients.count complete filter in and of itself, as it does not evaluate to a boolean,
but is instead meant to be used within a larger filter expression.
TRoIP.isActive TRoIP is active.
Network.idContains("hex") The Network ID contains hex (Example hex: "1C74").
Network.nameContains("text") The Network Name contains "text".
AP.essidContains("text") The ESSID of any AP contains "text".
AP.isActive At least one AP is enabled.

Note that some filters take arguments. For example, the following is valid:

Peers.hasMoreThan(10) && Alerts.hasErrors || Network.nameContains("bender")

In such cases, the parentheses around the arguments are required.

117
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Note that these built-in filters can be combined with user-defined filters, as in:

TRoIP.isActive && !system.state.reboot

Definitions

All of the built-in filters are defined internally as regular filters… they do not use any special
functionality. The following shows how each is defined (parameters have been replaced by specific
example values):

● Peers.hasAny
math.count(math.unique(state.wireless.peer[:enabled].mac)) >= 1

● Peers.hasAtLeast(10)
math.count(math.unique(state.wireless.peer[:enabled].mac)) >= 10

● Groups.nameContains("leela")
state.configuration.active.general.groups.name contains "leela"

● Reboot.isNeeded
state.system.reboot

● Reboot.inPastHour
state.system.uptime < 3600.0

● Reboot.inPastDay
state.system.uptime < 86400.0

● Alerts.hasErrors
state.alertSystem.alerts.type contains "ERROR"

● Alerts.hasWarnings
state.alertSystem.alerts.type contains "WARNING"

● APT.isMaster
state.wired.aptState contains "MASTER"

● APT.isSlave
state.wired.aptState contains "SLAVE"

● Clients.hasAny
math.count(math.unique(state.wireless.ap.client.mac)) >= 1

● Clients.hasAtLeast(5)
math.count(math.unique(state.wireless.ap.client.mac)) >= 5

118
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

● Clients.count
math.count(math.unique(state.wireless.ap.client.mac))

● TRoIP.isActive
state.troip.active

● Network.idContains("deadbeef")
state.system.networkId contains "deadbeef"

● Network.nameContains("zoidberg")
config.instamesh.networkName contains "zoidberg"

● AP.essidContains("hermes")
state.wireless.ap.essid contains "hermes"

● AP.isActive
config.wireless.ap[:enable].essid.length > 0

Extended Examples

Regular expressions:

● model.name ~ "^LX[34]"

Model begins with LX3 or LX4.

Specifying behavior for nested repeated fields:

● config.wireless[any].ap[all].enable

BreadCrumbs with any wireless interface where all APs are enabled.

Use of multiple nested filters:

● config.wireless[: ap[none].essid == "rajant"].ap[all : enable].security.mode

contains "wpa"

BreadCrumbs with any wireless interfaces lacking APs called "rajant" whose enabled APs are all
configured to use WPA.

Note here that the first nested filter starts with a colon. We left out the optional "any" specifier
because it's the default behavior.

119
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Grammar

For reference, the following language grammar rules apply:

● FILTER ::= DISJUNCTION

● DISJUNCTION ::= CONJUNCTION [ DISJUNCTION_TAIL ]
● DISJUNCTION_TAIL ::= OR CONJUNCTION [ DISJUNCTION_TAIL ]
● CONJUNCTION ::= EQUALITY [ CONJUNCTION_TAIL ]
● CONJUNCTION_TAIL ::= AND EQUALITY [ CONJUNCTION_TAIL ]
● EQUALITY ::= NEST_OR_TERM OP [ EQUALITY ]
● NEST_OR_TERM ::= '(' DISJUNCTION ')' | '!' NEST_OR_TERM | STRING | NUMBER |
BOOL | VAR | TERM
● VAR ::= '$' INTEGER
● TERM ::= IDENTIFIER [ ARGS ] [ '[' MODE [ ':' DISJUNCTION ] ']' ] [ '.' TERM ]
● ARGS ::= '(' ( DISJUNCTION ARG_SUFFIX | ')' )
● ARG_SUFFIX ::= ',' DISJUNCTION ARG_SUFFIX | ')'
● MODE ::= 'none' | 'any' | 'all'

Primitive rules such as BOOL are trivially defined and not specified here.

120
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Appendix E: Rajant End User License Agreement

IMPORTANT: PLEASE READ THIS END USER LICENSE AGREEMENT CAREFULLY. IT IS
ENCLOSED IN THE SOFTWARE PACKAGE AND /OR PRESENTED ELECTRONICALLY WHEN
ACCESSING THE SOFTWARE. BY CLICKING “I AGREE”, YOU ARE AGREEING TO BE
BOUND BY THE TERMS OF THIS LICENSE. IT IS VERY IMPORTANT THAT YOU CHECK
THAT YOU ARE PURCHASING RAJANT SOFTWARE OR EQUIPMENT FROM AN APPROVED
SOURCE AND THAT YOU, OR THE ENTITY YOU REPRESENT (COLLECTIVELY, THE
"CUSTOMER") HAVE BEEN REGISTERED AS THE END USER FOR THE PURPOSES OF THIS
RAJANT END USER LICENSE AGREEMENT. IF YOU ARE NOT REGISTERED AS THE END
USER YOU HAVE NO LICENSE TO USE THE SOFTWARE AND THE LIMITED WARRANTY IN
THIS END USER LICENSE AGREEMENT DOES NOT APPLY. ASSUMING YOU HAVE
PURCHASED FROM AN APPROVED SOURCE, DOWNLOADING, INSTALLING OR USING
RAJANT OR RAJANT-SUPPLIED SOFTWARE CONSTITUTES ACCEPTANCE OF THIS
AGREEMENT.
RAJANT CORPORATION OR ITS AFFILIATE LICENSING THE SOFTWARE ("RAJANT") IS
WILLING TO LICENSE THIS SOFTWARE TO YOU ONLY UPON THE CONDITION THAT YOU
PURCHASED THE SOFTWARE FROM AN APPROVED SOURCE AND THAT YOU ACCEPT ALL
OF THE TERMS CONTAINED IN THIS END USER LICENSE AGREEMENT PLUS ANY
ADDITIONAL LIMITATIONS ON THE LICENSE SET FORTH IN A SUPPLEMENTAL LICENSE
AGREEMENT ACCOMPANYING THE PRODUCT OR AVAILABLE AT THE TIME OF YOUR
ORDER (COLLECTIVELY THE "AGREEMENT"). TO THE EXTENT OF ANY CONFLICT
BETWEEN THE TERMS OF THIS END USER LICENSE AGREEMENT AND ANY
SUPPLEMENTAL LICENSE AGREEMENT, THE SUPPLEMENTAL LICENSE AGREEMENT
SHALL APPLY. BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE, YOU ARE
REPRESENTING THAT YOU PURCHASED THE SOFTWARE FROM AN APPROVED SOURCE
AND BINDING YOURSELF TO THE AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS OF THE AGREEMENT, THEN RAJANT IS UNWILLING TO LICENSE THE SOFTWARE
TO YOU AND (A) YOU MAY NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE, AND (B)
YOU MAY RETURN THE SOFTWARE (INCLUDING ANY UNOPENED PACKAGE AND ANY
WRITTEN MATERIALS) FOR A FULL REFUND, OR, IF THE SOFTWARE AND WRITTEN
MATERIALS ARE SUPPLIED AS PART OF ANOTHER PRODUCT, YOU MAY RETURN THE
ENTIRE PRODUCT FOR A FULL REFUND. YOUR RIGHT TO RETURN AND REFUND
EXPIRES 30 DAYS AFTER PURCHASE FROM AN APPROVED SOURCE, AND APPLIES ONLY
IF YOU ARE THE ORIGINAL AND REGISTERED END USER PURCHASER. FOR THE
PURPOSES OF THIS END USER LICENSE AGREEMENT, AN "APPROVED SOURCE" MEANS
(A) RAJANT; OR (B) A DISTRIBUTOR OR SYSTEMS INTEGRATOR AUTHORIZED BY RAJANT
TO DISTRIBUTE / SELL RAJANT EQUIPMENT, SOFTWARE AND SERVICES WITHIN YOUR
TERRITORY TO END USERS; OR (C) A RESELLER AUTHORIZED BY ANY SUCH
DISTRIBUTOR OR SYSTEMS INTEGRATOR IN ACCORDANCE WITH THE TERMS OF THE
DISTRIBUTOR'S AGREEMENT WITH RAJANT TO DISTRIBUTE / SELL THE RAJANT
EQUIPMENT, SOFTWARE AND SERVICES WITHIN YOUR TERRITORY TO END USERS.
THE FOLLOWING TERMS OF THE AGREEMENT GOVERN CUSTOMER'S USE OF THE
SOFTWARE (DEFINED BELOW), EXCEPT TO THE EXTENT: (A) THERE IS A SEPARATE SIGNED
CONTRACT BETWEEN CUSTOMER AND RAJANT GOVERNING CUSTOMER'S USE OF THE
SOFTWARE, OR (B) THE SOFTWARE INCLUDES A SEPARATE "CLICK-ACCEPT" LICENSE
AGREEMENT OR THIRD PARTY LICENSE AGREEMENT AS PART OF THE INSTALLATION OR
121
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

DOWNLOAD PROCESS GOVERNING CUSTOMER'S USE OF THE SOFTWARE. TO THE EXTENT

OF A CONFLICT BETWEEN THE PROVISIONS OF THE FOREGOING DOCUMENTS, THE ORDER
OF PRECEDENCE SHALL BE (1)THE SIGNED CONTRACT, (2) THE CLICK-ACCEPT
AGREEMENT OR THIRD PARTY LICENSE AGREEMENT, AND (3) THE AGREEMENT. FOR
PURPOSES OF THE AGREEMENT, "SOFTWARE" SHALL MEAN COMPUTER PROGRAMS,
INCLUDING FIRMWARE AND COMPUTER PROGRAMS EMBEDDED IN RAJANT EQUIPMENT,
AS PROVIDED TO CUSTOMER BY AN APPROVED SOURCE, AND ANY UPGRADES, UPDATES,
BUG FIXES OR MODIFIED VERSIONS THERETO (COLLECTIVELY, "UPGRADES"), ANY OF THE
SAME WHICH HAS BEEN RELICENSED UNDER THE RAJANT SOFTWARE TRANSFER AND
RE-LICENSING POLICY (AS MAY BE AMENDED BY RAJANT FROM TIME TO TIME) OR BACKUP
COPIES OF ANY OF THE FOREGOING.
License. Conditioned upon compliance with the terms and conditions of the Agreement, RAJANT
grants to Customer a nonexclusive and nontransferable license to use for Customer's internal business
purposes the Software and the Documentation for which Customer has paid the required license fees to
an Approved Source. "Documentation" means written information (whether contained in user or
technical manuals, training materials, specifications or otherwise) pertaining to the Software and made
available by an Approved Source with the Software in any manner (including on CD-Rom, or on-line).
In order to use the Software, Customer may be required to input a registration number or product
authorization key and register Customer's copy of the Software online at RAJANT’S website to obtain
the necessary license key or license file.
Customer's license to use the Software shall be limited to, and Customer shall not use the Software in
excess of, a single hardware chassis or card or such other limitations as are set forth in the applicable
Supplemental License Agreement or in the applicable purchase order which has been accepted by an
Approved Source and for which Customer has paid to an Approved Source the required license fee (the
"Purchase Order").
Unless otherwise expressly provided in the Documentation or any applicable Supplemental License
Agreement, Customer shall use the Software solely as embedded in, for execution on, or (where the
applicable Documentation permits installation on non- RAJANT equipment) for communication with
RAJANT equipment owned or leased by Customer and used for Customer's internal business purposes.
No other licenses are granted by implication, estoppel or otherwise.
For evaluation or beta copies for which Rajant does not charge a license fee, the above requirement to
pay license fees does not apply.
General Limitations. This is a license, not a transfer of title, to the Software and Documentation, and
Rajant retains ownership of all copies of the Software and Documentation. Customer acknowledges that
the Software and Documentation contain trade secrets of Rajant or its suppliers or licensors, including
but not limited to the specific internal design and structure of individual programs and associated
interface information. Except as otherwise expressly provided under the Agreement, Customer shall
only use the Software in connection with the use of Rajant equipment purchased by the Customer from
an Approved Source and Customer shall have no right, and Customer specifically agrees not to:
(i) transfer, assign or sublicense its license rights to any other person or entity (other than in
compliance with any Rajant relicensing/transfer policy then in force), or use the Software on
Rajant equipment not purchased by the Customer from an Approved Source or on secondhand
Rajant equipment, and Customer acknowledges that any attempted transfer, assignment,
sublicense or use shall be void;

122
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

(ii) make error corrections to or otherwise modify or adapt the Software or create derivative
works based upon the Software, or permit third parties to do the same;
(iii) reverse engineer or decompile, decrypt, disassemble or otherwise reduce the Software to
human-readable form, except to the extent otherwise expressly permitted under applicable law
notwithstanding this restriction or except to the extent that Rajant is legally required to permit
such specific activity pursuant to any applicable open source license;
(iv) publish any results of benchmark tests run on the Software;
(v) use or permit the Software to be used to perform services for third parties, whether on a
service bureau or time sharing basis or otherwise, without the express written authorization of
Rajant; or
(vi) disclose, provide, or otherwise make available trade secrets contained within the Software
and Documentation in any form to any third party without the prior written consent of Rajant.
Customer shall implement reasonable security measures to protect such trade secrets.
To the extent required by applicable law, and at Customer's written request, Rajant shall provide
Customer with the interface information needed to achieve interoperability between the Software and
another independently created program, on payment of Rajant’s applicable fee, if any. Customer shall
observe strict obligations of confidentiality with respect to such information and shall use such
information in compliance with any applicable terms and conditions upon which Rajant makes such
information available.
Software, Upgrades and Additional Copies. NOTWITHSTANDING ANY OTHER PROVISION OF
THE AGREEMENT: (1) CUSTOMER HAS NO LICENSE OR RIGHT TO MAKE OR USE ANY
ADDITIONAL COPIES OR UPGRADES UNLESS CUSTOMER, AT THE TIME OF MAKING OR
ACQUIRING SUCH COPY OR UPGRADE, ALREADY HOLDS A VALID LICENSE TO THE
ORIGINAL SOFTWARE AND HAS PAID THE APPLICABLE FEE TO AN APPROVED SOURCE
FOR THE UPGRADE OR ADDITIONAL COPIES; (2) USE OF UPGRADES IS LIMITED TO
RAJANT EQUIPMENT SUPPLIED BY AN APPROVED SOURCE FOR WHICH CUSTOMER IS
THE ORIGINAL END USER PURCHASER OR LESSEE OR OTHERWISE HOLDS A VALID
LICENSE TO USE THE SOFTWARE WHICH IS BEING UPGRADED; AND (3) THE MAKING
AND USE OF ADDITIONAL COPIES IS LIMITED TO NECESSARY BACKUP PURPOSES ONLY.
Proprietary Notices. Customer agrees to maintain and reproduce all copyright, proprietary, and other
notices on all copies, in any form, of the Software and Documentation in the same form and manner that
such copyright and other proprietary notices are included on the Software. Except as expressly
authorized in the Agreement, Customer shall not make any copies or duplicates of any Software without
the prior written permission of Rajant.
Term and Termination. The Agreement and the license granted herein shall remain effective until
terminated. Customer may terminate the Agreement and the license at any time by destroying all copies
of Software and any Documentation. Customer's rights under the Agreement will terminate immediately
without notice from RAJANT if Customer fails to comply with any provision of the Agreement. Upon
termination, Customer shall destroy or return to RAJANT all copies of Software and Documentation in
its possession or control. All confidentiality obligations of Customer, all restrictions and limitations
imposed on the Customer under the section titled "General Limitations" and all limitations of liability
and disclaimers and restrictions of warranty shall survive termination of this Agreement. In addition, the
provisions of the sections titled "U.S. Government End User Purchasers" and "General Terms Applicable
to the Limited Warranty Statement and End User License Agreement" shall survive termination of the

123
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Agreement.
Customer Records. Customer grants to RAJANT and its independent accountants the right to examine
Customer's books, records, accounts, and network configuration(s) during Customer's normal business
hours to verify compliance with this Agreement. In the event such audit discloses non-compliance with
this Agreement, Customer shall promptly pay to RAJANT the appropriate license fees, plus the
reasonable cost of conducting the audit.
Export, Re-Export, Transfer and Use Controls. The Software, Documentation and technology or direct
products thereof (hereafter referred to as Software and Technology), supplied by RAJANT under the
Agreement are subject to export controls under the laws and regulations of the United States ("U.S.")
and any other applicable countries' laws and regulations. Customer shall comply with such laws and
regulations governing export, re-export, import, transfer and use of RAJANT Software and Technology
and will obtain all required U.S. and local authorizations, permits, or licenses. RAJANT and Customer
each agree to provide the other information, support documents, and assistance as may reasonably be
required by the other in connection with securing authorizations or licenses. Information regarding
compliance with export, re-export, transfer and use.
U.S. Government End User Purchasers. The Software and Documentation qualify as "commercial
items," as that term is defined at Federal Acquisition Regulation ("FAR") (48 C.F.R.) 2.101, consisting
of "commercial computer software" and "commercial computer software documentation" as such terms
are used in FAR 12.212. Consistent with FAR 12.212 and DoD FAR Supp. 227.7202-1 through
227.7202-4, and notwithstanding any other FAR or other contractual clause to the contrary in any
agreement into which the Agreement may be incorporated, Customer may provide to Government end
user or, if the Agreement is direct, Government end user will acquire, the Software and Documentation
with only those rights set forth in the Agreement. Use of either the Software or Documentation or both
constitutes agreement by the Government that the Software and Documentation are "commercial
computer software" and "commercial computer software documentation," and constitutes acceptance of
the rights and restrictions herein.
Identified Components; Additional Terms. The Software may contain or be delivered with one or more
components, which may include third-party components, identified by RAJANT in the Documentation,
readme.txt file, third-party click-accept or elsewhere (e.g. on www.rajant.com) (the "Identified
Component(s)") as being subject to different license agreement terms, disclaimers of warranties, limited
warranties or other terms and conditions (collectively, "Additional Terms") than those set forth herein.
You agree to the applicable Additional Terms for any such Identified Component(s).
Limited Warranty
Subject to the limitations and conditions set forth herein, RAJANT warrants that commencing from the
date of shipment to Customer (but in case of resale by an Approved Source other than RAJANT,
commencing not more than ninety (90) days after original shipment by RAJANT), and continuing for a
period of the longer of (a) ninety (90) days or (b) the warranty period (if any) expressly set forth as
applicable specifically to software in the warranty card accompanying the product of which the Software
is a part (the "Product") (if any): (a) the media on which the Software is furnished will be free of defects
in materials and workmanship under normal use; and (b) the Software substantially conforms to the
Documentation. The date of shipment of a Product by RAJANT is set forth on the packaging material in
which the Product is shipped. Except for the foregoing, the Software is provided "AS IS". This limited
warranty extends only to the Software purchased from an Approved Source by a Customer who is the
first registered end user. Customer's sole and exclusive remedy and the entire liability of RAJANT and
its suppliers under this limited warranty will be (i) replacement of defective media and/or (ii) at

124
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

RAJANT’s option, repair, replacement, or refund of the purchase price of the Software, in both cases
subject to the condition that any error or defect constituting a breach of this limited warranty is reported
to the Approved Source supplying the Software to Customer, within the warranty period. RAJANT or
the Approved Source supplying the Software to Customer may, at its option, require return of the
Software and/or Documentation as a condition to the remedy. In no event does RAJANT warrant that
the Software is error free or that Customer will be able to operate the Software without problems or
interruptions. In addition, due to the continual development of new techniques for intruding upon and
attacking networks, RAJANT does not warrant that the Software or any equipment, system or network
on which the Software is used will be free of vulnerability to intrusion or attack.
No representation or other affirmation of fact, including but not limited to statements regarding capacity,
suitability for use or performance of Software, whether made by Rajant employees or otherwise, shall be
deemed to be a warranty for any purpose or give rise to any liability of Rajant whatsoever unless
contained in this Agreement.
Restrictions. This warranty does not apply if the Software, Product or any other equipment upon which
the Software is authorized to be used (a) has been altered, except by RAJANT or its authorized
representative, (b) has not been installed, operated, repaired, or maintained in accordance with
instructions supplied by RAJANT, (c) has been subjected to abnormal physical or electrical stress,
abnormal environmental conditions, misuse, negligence, or accident; or (d) is licensed for beta,
evaluation, testing or demonstration purposes. The Software warranty also does not apply to (e) any
temporary Software modules; (f) any Software not posted on RAJANT’s Software Center; (g) any
Software that RAJANT expressly provides on an "AS IS" basis on RAJANT’s Software Center; (h) any
Software for which an Approved Source does not receive a license fee; and (i) Software supplied by any
third party which is not an Approved Source.
Hardware Limited Warranty
THE BREADCRUMB WIRELESS LAN UNITS (“BREADCRUMB”), EXCLUSIVE OF THE JR-2
BREADCRUMB, PROVIDED UNDER THIS AGREEMENT ARE PROVIDED WITH A 1-YEAR
WARRANTY FROM THE DATE THE BREADCRUMB IS SHIPPED BY RAJANT AGAINST
DEFECTS IN WORKMANSHIP OR MATERIAL UNDER ORDINARY USE. SUCH WARRANTY
APPLIES ONLY TO THE BREADCRUMB DEVICE AND DOES NOT EXTEND TO ANY OTHER
PRODUCTS, PRODUCTS OR SERVICES, INCLUDING BUT NOT LIMITED TO POWER
SUPPLIES, CABLES, ANTENNAS, AND MOUNTING BRACKETS, EVEN IF PACKAGED OR
SOLD WITH THE BREADCRUMB.
JR-2 BREADCRUMBS ARE WARRANTED ONLY AGAINST DEFECTIVE WORKMANSHIP FOR
90 DAYS WHEN DELIVERED NEW. RAJANT MAKES NO WARRANTY, AND DISCLAIMS ANY
WARRANTY, EXPRESS OR IMPLIED AT LAW, ON JR-2 BREADCRUMBS' FITNESS FOR A
PARTICULAR PURPOSE OR MERCHANTABILITY. MANUFACTURER'S RMA POLICIES AND
PROCEDURES APPLY.
RAJANT PRODUCTS CLASSIFIED AS ACCESSORY ON MANUFACTURER'S PRICE LIST ARE
WARRANTED AGAINST DEFECTS FOR A PERIOD OF 90 DAYS FROM DATE OF DELIVERY.
Unless otherwise listed on this Warranty Schedule, Rajant warrants to the purchaser that the Products
will perform in all material respects in accordance with their written specifications for a period of ninety
(90) days from the date the Products are shipped by Rajant. Reseller and purchaser’s sole and exclusive
right and remedy, and Rajant’s sole and exclusive obligation and liability, with respect to any breach of
the foregoing warranty shall be that, upon receipt by Rajant from Reseller or purchasers of written
notice of the breach in reasonable detail so as to permit Rajant to duplicate the failure to so perform,

125
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

which notice is received by Rajant within thirty (30) days after Reseller or purchaser discovers the
failure, Rajant shall – after duplicating the failure – exercise its commercially reasonable efforts to
deliver to Reseller or purchaser a replacement or repaired Product at Rajant’s discretion. Rajant
replacement parts used in such replacement may be new or equivalent to new. Rajant's obligations
hereunder are conditioned upon the return of the affected Product in accordance with Rajant's
then-current Return Material Authorization (RMA) procedures.
This warranty shall not apply to any Product that has been subjected to unusual physical, environmental
or electrical stress. The warranty shall not apply to any problems or non-performance directly resulting
from Reseller or purchaser’s hardware, software, network(s) and/or host system(s) or the combination,
operation or use of the Product with such hardware, software, network(s) and/or host system(s), or
which results from any alteration or modification to the Product or its components by anyone other than
Rajant. The warranty also does not cover any (a) Product for which the serial number has been removed
or made illegible; (b) freight costs to the repair center; (c) scratches or other cosmetic damage to Product
surfaces that do not affect the operation of the Product; and (d) normal and customary wear and tear.
The date of shipment of a Product by Rajant is set forth on the packaging material in which the Product
is shipped. This limited warranty extends only to the original user of the Product.
Replacement, Repair or Refund Procedure for Products Covered by Warranty
Rajant will use commercially reasonable efforts to ship a repaired or replacement part within fifteen (15)
working days after receipt of the RMA request. Actual delivery times may vary depending on Reseller’s
or purchaser’s location.
To Receive a Return Materials Authorization (RMA) Number
Please contact the party from whom you purchased the Product. If you purchased the Product directly
from Rajant, contact your Rajant Sales and Service Representative or email [email protected].
DISCLAIMER OF WARRANTY
EXCEPT AS SPECIFIED IN THIS WARRANTY SECTION, ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT
LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, SATISFACTORY QUALITY,
NON-INTERFERENCE, ACCURACY OF INFORMATIONAL CONTENT, OR ARISING FROM A
COURSE OF DEALING, LAW, USAGE, OR TRADE PRACTICE, ARE HEREBY EXCLUDED TO
THE EXTENT ALLOWED BY APPLICABLE LAW AND ARE EXPRESSLY DISCLAIMED BY
RAJANT, ITS SUPPLIERS AND LICENSORS. TO THE EXTENT THAT ANY OF THE SAME
CANNOT BE EXCLUDED, SUCH IMPLIED CONDITION, REPRESENTATION AND/OR
WARRANTY IS LIMITED IN DURATION TO THE EXPRESS WARRANTY PERIOD REFERRED
TO IN THE "LIMITED WARRANTY" SECTION ABOVE. BECAUSE SOME STATES OR
JURISDICTIONS DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY
LASTS, THE ABOVE LIMITATION MAY NOT APPLY IN SUCH STATES. THIS WARRANTY
GIVES CUSTOMER SPECIFIC LEGAL RIGHTS, AND CUSTOMER MAY ALSO HAVE OTHER
RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION. This disclaimer and exclusion
shall apply even if the express warranty set forth above fails of its essential purpose.
Disclaimer of Liabilities—Limitation of Liability. IF YOU ACQUIRED THE SOFTWARE IN THE
UNITED STATES, LATIN AMERICA, CANADA, JAPAN OR THE CARIBBEAN,
NOTWITHSTANDING ANYTHING ELSE IN THE AGREEMENT TO THE CONTRARY, ALL
LIABILITY OF RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS,

126
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

SUPPLIERS AND LICENSORS COLLECTIVELY, TO CUSTOMER, WHETHER IN CONTRACT,

TORT (INCLUDING NEGLIGENCE), BREACH OF WARRANTY OR OTHERWISE, SHALL NOT
EXCEED THE PRICE PAID BY CUSTOMER TO ANY APPROVED SOURCE FOR THE
SOFTWARE THAT GAVE RISE TO THE CLAIM OR IF THE SOFTWARE IS PART OF ANOTHER
PRODUCT, THE PRICE PAID FOR SUCH OTHER PRODUCT. THIS LIMITATION OF LIABILITY
FOR SOFTWARE IS CUMULATIVE AND NOT PER INCIDENT (I.E. THE EXISTENCE OF TWO
OR MORE CLAIMS WILL NOT ENLARGE THIS LIMIT).
IF YOU ACQUIRED THE SOFTWARE IN EUROPE, THE MIDDLE EAST, AFRICA, ASIA OR
OCEANIA, NOTWITHSTANDING ANYTHING ELSE IN THE AGREEMENT TO THE
CONTRARY, ALL LIABILITY OF RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS,
EMPLOYEES, AGENTS, SUPPLIERS AND LICENSORS COLLECTIVELY, TO CUSTOMER,
WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), BREACH OF WARRANTY OR
OTHERWISE, SHALL NOT EXCEED THE PRICE PAID BY CUSTOMER TO RAJANT FOR THE
SOFTWARE THAT GAVE RISE TO THE CLAIM OR IF THE SOFTWARE IS PART OF ANOTHER
PRODUCT, THE PRICE PAID FOR SUCH OTHER PRODUCT. THIS LIMITATION OF LIABILITY
FOR SOFTWARE IS CUMULATIVE AND NOT PER INCIDENT (I.E. THE EXISTENCE OF TWO
OR MORE CLAIMS WILL NOT ENLARGE THIS LIMIT). NOTHING IN THE AGREEMENT
SHALL LIMIT (I) THE LIABILITY OF RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS,
EMPLOYEES, AGENTS, SUPPLIERS AND LICENSORS TO CUSTOMER FOR PERSONAL
INJURY OR DEATH CAUSED BY THEIR NEGLIGENCE, (II) RAJANT’s LIABILITY FOR
FRAUDULENT MISREPRESENTATION, OR (III) ANY LIABILITY OF RAJANT WHICH
CANNOT BE EXCLUDED UNDER APPLICABLE LAW.
Disclaimer of Liabilities—Waiver of Consequential Damages and Other Losses. IF YOU ACQUIRED
THE SOFTWARE IN THE UNITED STATES, LATIN AMERICA, THE CARIBBEAN OR CANADA,
REGARDLESS OF WHETHER ANY REMEDY SET FORTH HEREIN FAILS OF ITS ESSENTIAL
PURPOSE OR OTHERWISE, IN NO EVENT WILL RAJANT OR ITS SUPPLIERS BE LIABLE FOR
ANY LOST REVENUE, PROFIT, OR LOST OR DAMAGED DATA, BUSINESS INTERRUPTION,
LOSS OF CAPITAL, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL, OR
PUNITIVE DAMAGES HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF
LIABILITY OR WHETHER ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE
OR OTHERWISE AND EVEN IF RAJANT OR ITS SUPPLIERS OR LICENSORS HAVE BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES OR
JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR
INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
IF YOU ACQUIRED THE SOFTWARE IN JAPAN, EXCEPT FOR LIABILITY ARISING OUT OF
OR IN CONNECTION WITH DEATH OR PERSONAL INJURY, FRAUDULENT
MISREPRESENTATION, AND REGARDLESS OF WHETHER ANY REMEDY SET FORTH
HEREIN FAILS OF ITS ESSENTIAL PURPOSE OR OTHERWISE, IN NO EVENT WILL RAJANT,
ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIERS AND
LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT, OR LOST OR DAMAGED DATA,
BUSINESS INTERRUPTION, LOSS OF CAPITAL, OR FOR SPECIAL, INDIRECT,
CONSEQUENTIAL, INCIDENTAL, OR PUNITIVE DAMAGES HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY OR WHETHER ARISING OUT OF THE USE OF
OR INABILITY TO USE SOFTWARE OR OTHERWISE AND EVEN IF RAJANT OR ANY
APPROVED SOURCE OR THEIR SUPPLIERS OR LICENSORS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

127
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

IF YOU ACQUIRED THE SOFTWARE IN EUROPE, THE MIDDLE EAST, AFRICA, ASIA OR
OCEANIA, IN NO EVENT WILL RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS,
EMPLOYEES, AGENTS, SUPPLIERS AND LICENSORS, BE LIABLE FOR ANY LOST
REVENUE, LOST PROFIT, OR LOST OR DAMAGED DATA, BUSINESS INTERRUPTION, LOSS
OF CAPITAL, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL, OR PUNITIVE
DAMAGES, HOWSOEVER ARISING, INCLUDING, WITHOUT LIMITATION, IN CONTRACT,
TORT (INCLUDING NEGLIGENCE) OR WHETHER ARISING OUT OF THE USE OF OR
INABILITY TO USE THE SOFTWARE, EVEN IF, IN EACH CASE, RAJANT, ITS AFFILIATES,
OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIERS AND LICENSORS, HAVE BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES OR
JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR
INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT FULLY APPLY TO YOU. THE
FOREGOING EXCLUSION SHALL NOT APPLY TO ANY LIABILITY ARISING OUT OF OR IN
CONNECTION WITH: (I) DEATH OR PERSONAL INJURY, (II) FRAUDULENT
MISREPRESENTATION, OR (III) RAJANT’s LIABILITY IN CONNECTION WITH ANY TERMS
THAT CANNOT BE EXCLUDED UNDER APPLICABLE LAW.
Customer acknowledges and agrees that RAJANT has set its prices and entered into the Agreement in
reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same
reflect an allocation of risk between the parties (including the risk that a contract remedy may fail of its
essential purpose and cause consequential loss), and that the same form an essential basis of the bargain
between the parties.
Controlling Law, Jurisdiction. Customer agrees that all sales occurred, and contracts entered into at
Malvern, Pennsylvania, notwithstanding the location of any affiliate or Customer’s location or principal
place of business. All contracts for the license of software and/or purchase of hardware are deemed to
have occurred at Malvern, Pennsylvania and the Agreement and warranties ("Warranties") are controlled
by and construed under the laws of the Commonwealth of Pennsylvania, United States of America,
notwithstanding any conflicts of law provisions; and the state and federal courts of Pennsylvania shall
have exclusive jurisdiction over any claim arising under the Agreement or Warranties.
The parties specifically disclaim the application of the UN Convention on Contracts for the International
Sale of Goods. Notwithstanding the foregoing, either party may seek interim injunctive relief in any
court of appropriate jurisdiction with respect to any alleged breach of such party's intellectual property
or proprietary rights. If any portion hereof is found to be void or unenforceable, the remaining
provisions of the Agreement and Warranties shall remain in full force and effect. Except as expressly
provided herein, the Agreement constitutes the entire agreement between the parties with respect to the
license of the Software and Documentation and supersedes any conflicting or additional terms contained
in any Purchase Order or elsewhere, all of which terms are excluded. The Agreement has been written
in the English language, and the parties agree that the English version will govern.
Product warranty terms and other information applicable to RAJANT products are available at the
following URL: www.rajant.com
RAJANT and the RAJANT Logo are trademarks of RAJANT Corporation and/or its affiliates in the
U.S. and other countries. Third party trademarks mentioned are the property of their respective owners.
The use of the word partner does not imply a partnership relationship between RAJANT and any other
company.

128
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Appendix F: GNU General Public License

Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

PREAMBLE
The licenses for most software are designed to take away your freedom to share and change it. By
contrast, the GNU General Public License is intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users. This General Public License applies to
most of the Free Software Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by the GNU Library General Public
License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses
are designed to make sure that you have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it if you want it, that you can change
the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask
you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute
copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the
recipients all the rights that you have. You must make sure that they, too, receive or can get the source
code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which
gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there
is no warranty for this free software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so that any problems introduced by
others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that
redistributors of a free program will individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free
use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright
holder saying it may be distributed under the terms of this General Public License. The “Program”,
below, refers to any such program or work, and a “work based on the Program” means either the

129
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

Program or any derivative work under copyright law: that is to say, a work containing the Program or a
portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter,
translation is included without limitation in the term “modification”.) Each licensee is addressed as
“you”.
Activities other than copying, distribution and modification are not covered by this License; they are
outside its scope. The act of running the Program is not restricted, and the output from the Program is
covered only if its contents constitute a work based on the Program (independent of having been made
by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any
medium, provided that you conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to
the absence of any warranty; and give any other recipients of the Program a copy of this License along
with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer
warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based
on the Program, and copy and distribute such modifications or work under the terms of Section 1 above,
provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the
date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived
from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the
terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when
started running for such interactive use in the most ordinary way, to print or display an announcement
including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you
provide a warranty) and that users may redistribute the program under these conditions, and telling the
user how to view a copy of this License. (Exception: if the Program itself is interactive but does not
normally print such an announcement, your work based on the Program is not required to print an
announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not
derived from the Program, and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those sections when you distribute them as
separate works. But when you distribute the same sections as part of a whole which is a work based on
the Program, the distribution of the whole must be on the terms of this License, whose permissions for
other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by
you; rather, the intent is to exercise the right to control the distribution of derivative or collective works
based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a
work based on the Program) on a volume of a storage or distribution medium does not bring the other
work under the scope of this License.

130
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or
executable form under the terms of Sections 1 and 2 above provided that you also do one of the
following:
a) Accompany it with the complete corresponding machine-readable source code, which must be
distributed under the terms of Sections 1 and 2 above on a medium customarily used for software
interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge
no more than your cost of physically performing source distribution, a complete machine-readable copy
of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source
code. (This alternative is allowed only for noncommercial distribution and only if you received the
program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an
executable work, complete source code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to control compilation and installation of the
executable. However, as a special exception, the source code distributed need not include anything that
is normally distributed (in either source or binary form) with the major components (compiler, kernel,
and so on) of the operating system on which the executable runs, unless that component itself
accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place,
then offering equivalent access to copy the source code from the same place counts as distribution of the
source code, even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under
this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and
will automatically terminate your rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses terminated so long as such parties
remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else
grants you permission to modify or distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by modifying or distributing the
Program (or any work based on the Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify the Program
subject to these terms and conditions. You may not impose any further restrictions on the recipients'
exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason
(not limited to patent issues), conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of
this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License
and any other pertinent obligations, then as a consequence you may not distribute the Program at all.

131
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

For example, if a patent license would not permit royalty-free redistribution of the Program by all those
who receive copies directly or indirectly through you, then the only way you could satisfy both it and
this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the
balance of the section is intended to apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or
to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the
free software distribution system, which is implemented by public license practices. Many people have
made generous contributions to the wide range of software distributed through that system in reliance on
consistent application of that system; it is up to the author/donor to decide if he or she is willing to
distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this
License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by
copyrighted interfaces, the original copyright holder who places the Program under this License may
add an explicit geographical distribution limitation excluding those countries, so that distribution is
permitted only in or among countries not thus excluded. In such case, this License incorporates the
limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License
from time to time. Such new versions will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this
License which applies to it and "any later version", you have the option of following the terms and
conditions either of that version or of any later version published by the FreeSoftware Foundation. If the
Program does not specify a version number of this License, you may choose any version ever published
by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted by
the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions
for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of
our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING

132
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING
BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO
OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS

HOW TO APPLY THESE TERMS TO YOUR NEW PROGRAMS

If you develop a new program, and you want it to be of the greatest possible use to the public, the best
way to achieve this is to make it free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each
source file to most effectively convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
one line to give the program's name and an idea of what it does.
Copyright (C) yyyy name of author
This program is free software; you can redistribute it and/or modify it under the terms of the GNU
General Public License as published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not,
write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free
software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General
Public License. Of course, the commands you use may be called something other than `show w' and
`show c'; they could even be mouse-clicks or menu items--whatever suits your program.

133
Rajant Corporation BC|Commander® v11 User Guide
03-100115-011 Version 11.5.0

You should also get your employer (if you work as a programmer) or your school, if any, to sign a
"copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright
interest in the program `Gnomovision'
(which makes passes at compilers) written
by James Hacker.
signature of Ty Coon, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into proprietary programs. If
your program is a subroutine library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the GNU Lesser General Public License
instead of this License.

134