The `bpq32.cfg` file is the heart of your BPQ32 configuration, outlining how your node operates. This guide walks you through the essential sections of the `bpq32.cfg` file, excluding detailed port configurations. For port-specific settings, please refer to our Port Configuration Guide.

Your `bpq32.cfg` file contains several key sections, each crucial for defining your node's behavior:

• Comments: Use `/*` and `*/` to enclose multi-line comments for your own notes or to disable sections without deleting them. You can also use `;` for single-line comments.

• Node Identification:

    NODECALL=KD5LPB-7       ; Your node's callsign.
    NODEALIAS=LPBNOD        ; A 6-character alias for your node.
    LOCATOR=DM79po          ; Your grid locator.
    

• Map Comment:

    MAPCOMMENT=Your node details and contact information.
    This appears on the BPQ map, providing details about your node and its services.
    

• Passwords:

    PASSWORD=YourSysopPassword
    Sets the sysop password for administrative access.
    

• Broadcast Texts (`IDMSG`, `BTEXT`, `INFOMSG`, `CTEXT`):

These sections allow you to customize messages for identification, information, and connection text. Indicate the end of each message section with three asterisks (without spaces between them) as a marker. e.g.:

  BTEXT:				; UI broadcast text from BCALL to destination UNPROTO=
  KD5LPB BPQ NODE in Aurora, CO DM79
  KD5LPB-1 BBS
  KD5LPB-11 Chat
  KD5LPB-7 Node
  ***	

• Network System Parameters:

Adjustments here affect how your node interacts with others, including obsolescence, intervals for node broadcasts, and hop limits.

The configuration of TNC and Level 2 parameters plays an important role in the operation of your node, affecting everything from packet transmission to how connections are managed and maintained. Here's a closer look at these settings:

TNC Parameters:

• PACLEN (Packet Length): Defines the maximum size for a packet, including headers and data. Optimal settings depend on your operational environment—shorter packets for noisy or busy channels, and longer packets for clear channels to enhance efficiency.

PACLEN=128 ; Adjust based on your specific network conditions

• TRANSDELAY (Transmission Delay): The pre-transmission delay, giving receivers a brief moment to prepare for incoming data. This setting is crucial in preventing packet collision in simplex systems.

TRANSDELAY=1 ; Delay in seconds before the transmission begins

Level 2 Parameters:

These parameters govern the AX.25 protocol's link layer behavior, managing how packet acknowledgements, retries, and timeouts are handled.

• FRACK: The frame acknowledgment time, setting how long the node waits for an ACK before considering a frame as lost and initiating a retry.

FRACK=5000 ; Level 2 timout in milliseconds

• RESPTIME: The time before a response frame is sent, used in adjusting the flow of communication to match network conditions.

RESPTIME=1000 ; Level 2 delayed ack timer in milliseconds

• T3 (LINK VALIDATION TIMER): Determines the interval for sending test frames to keep a link active, preventing timeouts on idle connections.

T3=120 ; Time in seconds

• RETRIES: The maximum number of transmission attempts for a frame before the connection is dropped. Adjusting this can affect network traffic and reliability.

RETRIES=10 ; Level 2 maximum retry value

• IDLETIME: The duration a link can remain idle before being automatically disconnected, freeing up resources for other connections.

IDLETIME=720 ; Idle time in seconds before automatic disconnect

• FULL_CTEXT:

```

  FULL_CTEXT=1
  ```
  Determines whether connection text is sent to all connecting stations or just those connecting to the NODEALIAS.

• Application Definitions:

Define applications such as BBS, Chat, or Node services. Each application is designated an application number, callsign, and optional command prefix.

• Port Definitions:

For an in-depth look at configuring ports, visit our Port Configuration Guide. Each port configuration block defines a communication method, such as RF, Telnet, or AXIP links.

• Routes:

```

  ROUTES:
  Locked routes configurations.
  ***
  ```
  Locked routes ensure specific quality and hop settings for designated stations.

For Raspberry Pi users, the `bpq-config` script offers an automated setup process, ideal for initial configurations. Access the script and instructions at https://www.prinmath.com/ham/howto/quickstart/. This tool simplifies generating a baseline `bpq32.cfg` file, which you can then customize as needed.

Return to the Homepage