WiRSa

RetroDisks WiRSa v3 - WiFi RS232 Serial Modem Adapter

The WiRSa v3 is a WiFi-to-RS232 serial adapter designed for legacy computing systems. It allows vintage computers to connect to modern networks via WiFi, supporting telnet BBS connectivity, file transfers, and network gateway functionality.

Kits & assembled units available for sale

If you prefer to save yourself some time, I have some units (fully assembled or kit) available for sale. I had quite a few PCB's made up and I am trying to keep these as cheap as possible. You can purchase on SmallRun.

Features

Hardware

• Processor: ESP-WROOM-32D with WiFi and Bluetooth 4.2 BLE
• Display: 128x64 two-color OLED display for settings, commands, and real-time data
• Serial Port: Female DB9 (DE9) connector
• Full RS232 Breakout:
  • DSR/DTR (Data Set Ready / Data Terminal Ready)
  • RTS/CTS (Request to Send / Clear to Send)
  • DCD (Data Carrier Detect)
  • RI (Ring Indicator)
• Storage: Built-in micro SD card reader for file transfers and text playback
• Power:
  • USB-C power connector
  • Optional 2000mAh 3.7V Li-Po battery (~14 hours runtime)
• Navigation: Four physical buttons for menu navigation

Operating Modes

1. MODEM Mode - Hayes-compatible AT command modem emulation for telnet/BBS connectivity
2. Telnet Server - Built-in telnet server allows for remote terminal access
3. File Transfer - Binary file transfer directly from SD card via XModem, YModem, and ZModem protocols
4. Text Playback - Display text files from SD card through the serial port
5. PPP Gateway - Point-to-Point Protocol gateway for TCP/IP networking
6. SLIP Gateway - Serial Line Internet Protocol gateway
7. Utilities - Diagnostics and troubleshooting tools including signal monitoring and loopback testing
8. Config - Settings for baud rate, serial configuration, display orientation, and more

Software Features

• AT Command Set - Full Hayes-compatible modem commands
• Web Interface - Built-in web server for status monitoring, configuration and file management
• Flow Control - Hardware (RTS/CTS) and software (XON/XOFF) flow control
• Speed Dial - 10 programmable speed dial entries
• PETSCII Translation - Support for Commodore computers
• Telnet Protocol - Automatic Telnet IAC handling
• OTA Updates - Over-the-air firmware updates via HTTP

Getting Started

WiFi Configuration

1. Connect to your computer via serial port (default: 9600 baud, 8N1)
2. Enter your WiFi credentials using AT commands (2.4 GHz networks only):

   AT$SSID=YourNetworkName
   AT$PASS=YourPassword

3. Save settings: AT&W
4. Reboot or reconnect to apply

Connecting to a BBS

Use the dial command with the host and port:

ATDT bbs.example.com:23

Or configure speed dial entries:

AT&Z0=bbs.example.com:23
ATDS0

Useful AT Commands

File Transfers

The WiRSa supports binary file transfers directly from the SD card using industry-standard protocols:

• XModem - Basic 128-byte block transfer with checksum
• YModem - Batch file transfer with filename and size
• ZModem - Streaming protocol with CRC16/CRC32 and automatic resume

To transfer files:

1. Insert SD card with files
2. Select "File Transfer" from the main menu
3. Choose the transfer protocol
4. Select send or receive
5. Initiate the transfer from your terminal software

SLIP / PPP Gateway Modes

The WiRSa provides full TCP/IP networking capabilities for vintage computers through two standard protocols: SLIP (Serial Line Internet Protocol) and PPP (Point-to-Point Protocol). These modes turn the WiRSa into a dial-up internet gateway, allowing retro systems to browse the web, use email clients, FTP, and access other network services.

How It Works

Both modes operate as NAT (Network Address Translation) gateways:

1. The vintage computer connects via the serial port
2. The WiRSa performs NAT translation between the serial link and WiFi
3. Outbound traffic is routed to the internet via the ESP32's WiFi connection
4. The vintage computer appears to have full internet access

SLIP Mode

SLIP is a simpler, older protocol with less overhead. It works well with:

• DOS with packet drivers (ETHERSLIP, SLIPPER, etc.)
• Early Windows 3.x with Trumpet Winsock
• Classic Mac OS with MacSLIP or InterSLIP
• Linux with slattach

Default Configuration:

• Gateway IP: 192.168.7.1 (WiRSa)
• Client IP: 192.168.7.2 (vintage computer)
• DNS: 8.8.8.8

PPP Mode

PPP is more robust with built-in negotiation, authentication support, and error detection. It's the standard for:

• Windows 95/98/ME Dial-Up Networking
• Windows 3.11 with Microsoft DUN
• Mac OS 8/9 with PPP/Remote Access
• Linux with pppd

Default Configuration:

• Gateway IP: 192.168.8.1 (WiRSa)
• Client IP: 192.168.8.2 (assigned to client)
• Primary DNS: 8.8.8.8
• Secondary DNS: 8.8.4.4

Entering SLIP/PPP Mode

From the WiRSa Menu: (if your host OS is expecting an "always on" connection)

1. Navigate to "PPP Gateway" or "SLIP Gateway" from the main menu
2. Select "Start Gateway"

Using AT Dial Commands: (must set the device to Modem Mode first)

ATDT SLIP      - Enter SLIP mode
ATDT 7547      - Enter SLIP mode (phone keypad for "SLIP")

ATDT PPP       - Enter PPP mode
ATDT 777       - Enter PPP mode (phone keypad for "PPP")

Using AT Commands: (must set the device to Modem Mode first)

AT$SLIP        - Enter SLIP mode directly
AT$PPP         - Enter PPP mode directly

Port Forwarding

Port forwarding allows incoming connections from the internet to reach services running on your vintage computer. This is useful for:

• Hosting a BBS - Run a BBS on your vintage computer accessible from the internet
• FTP Server - Share files from your retro machine
• Web Server - Host a vintage web server (Windows 95 Personal Web Server, etc.)
• Game Servers - Host multiplayer games on classic systems
• SSH/Telnet Access - Remote into your vintage computer

Configuring Port Forwards:

From the menu:

1. Enter SLIP or PPP Gateway menu
2. Select "Port Forwards"
3. Choose "Add Forward"
4. Enter protocol (TCP/UDP), external port, internal IP, and internal port

Using AT commands:

AT$SLIPFWD=TCP,80,80      - Forward TCP port 80 to client port 80
AT$SLIPFWD=UDP,53,53      - Forward UDP port 53 (DNS)
AT$SLIPFWDDEL=0           - Remove forward at index 0

AT$PPPFWD=TCP,23,23       - Forward TCP port 23 (telnet)
AT$PPPFWD=TCP,21,21       - Forward TCP port 21 (FTP)
AT$PPPFWDDEL=0            - Remove forward at index 0

Note: Port forwards are shared between SLIP and PPP modes and persist across reboots.

Setting Up SLIP Under DOS

Requirements:

• MS-DOS, DR-DOS, FreeDOS, etc
• A SLIP packet driver (ETHERSLIP, SLIPPER, or CSLIPPER)
• TCP/IP applications (mTCP suite, Arachne or MicroWeb browser, NCSA Telnet, etc.)

Step 1: Configure WiRSa

AT$SSID=YourWiFiNetwork
AT$PASS=YourPassword
AT&W

Step 2: Install Packet Driver

Create a batch file (e.g., SLIP.BAT):

@echo off
REM Load SLIP packet driver on COM1 at 115200 baud
ETHERSL 0x60 4 0x3F8 115200
REM Or for COM2: ETHERSL 0x60 3 0x2F8 115200

Step 3: Configure TCP/IP Stack

For mTCP, create MTCP.CFG:

PACKETINT 0x60
IPADDR 192.168.7.2
NETMASK 255.255.255.0
GATEWAY 192.168.7.1
NAMESERVER 8.8.8.8

Set environment variable:

SET MTCPCFG=C:\MTCP\MTCP.CFG

Step 4: Connect

On the WiRSa, start SLIP Gateway by enabling from the buttons/screen menu, from the serial menu (exit terminal after Starting Gateway, it starts immediately), or by dialing

ATDT SLIP

Step 5: Test Connection

PING 8.8.8.8
TELNET bbs.example.com

Setting Up PPP Under Windows 95/98 Dial-Up Networking

Step 1: Create a New Connection

1. Open "My Computer" → "Dial-Up Networking"
2. Click "Make New Connection"
3. Name it "WiRSa Internet" (or any name)
4. Select your serial port modem (or "Standard Modem" on the COM port)
5. For phone number, enter: PPP (or 777)

Step 2: Configure the Connection

1. Right-click the new connection → "Properties"
2. General tab: Ensure correct modem/port is selected
3. Server Types tab:
   • Type of Dial-Up Server: "PPP: Internet, Windows NT Server, Windows 98"
   • Uncheck "Log on to network" (unless needed)
   • Check "Enable software compression" (optional)
   • Check "TCP/IP" under Allowed network protocols
   • Uncheck NetBEUI and IPX/SPX unless needed
4. Click "TCP/IP Settings":
   • Select "Server assigned IP address"
   • Select "Server assigned name server addresses"
   • Click OK

Step 3: Modem Settings

1. Go to Control Panel → Modems → Properties
2. Set maximum speed to match WiRSa baud rate (115200 recommended, plus Flow Control enabled [AT&K1])
3. Under "Connection" tab, set 8 data bits, No parity, 1 stop bit
4. Make sure to put the WiRSa into Modem mode before proceeding

Step 4: Connect

1. Double-click the connection
2. Leave username/password blank (or enter any values - WiRSa ignores auth)
3. Click "Connect"
4. The WiRSa will respond "CONNECT PPP" and negotiate the link

Step 5: Verify Connection

• Open a command prompt: ping 8.8.8.8
• Open Internet Explorer and browse!

Setting Up PPP Under Windows 3.11

Requirements:

• Windows 3.11 for Workgroups
• Microsoft TCP/IP-32 or Trumpet Winsock
• Dial-Up Networking 1.0 for Windows 3.11

Step 1: Install TCP/IP-32

1. Run Network Setup
2. Add "Microsoft TCP/IP-32"
3. Configure with DHCP or manual IP (the WiRSa will assign IPs)

Step 2: Configure RAS (Remote Access Service)

1. Install RAS if not present
2. Add your modem on the appropriate COM port
3. Create a new phonebook entry with phone number "PPP" or "777"

Step 3: Connect

1. Open Remote Access
2. Select your WiRSa entry
3. Make sure WiRSa is in Modem Mode
4. Click "Dial"

Setting Up SLIP Under Linux

Linux has built-in SLIP support via the slattach utility. This guide covers configuring the serial port, enabling SLIP, and testing connectivity.

Requirements:

• Linux system with a physical serial port (directly connected to WiRSa)
• Root/sudo access
• slattach utility (usually included in net-tools or slip package)

Step 1: Identify Your Serial Port

First, identify the serial device. Physical serial ports are typically:

# First serial port (COM1 equivalent)
/dev/ttyS0

# Second serial port (COM2 equivalent)
/dev/ttyS1

# List available serial ports
ls -la /dev/ttyS*

# Check which serial ports are available
dmesg | grep -i ttyS

Step 2: Configure the Serial Port

Before starting SLIP, configure the serial port to match your WiRSa settings. Use stty to set the baud rate and other parameters:

# Set baud rate to 115200, 8N1, no flow control
sudo stty -F /dev/ttyS0 115200 cs8 -cstopb -parenb raw -echo

# For hardware flow control (if WiRSa has AT&K1 enabled), add crtscts:
sudo stty -F /dev/ttyS0 115200 cs8 -cstopb -parenb raw -echo crtscts

# Verify settings
stty -F /dev/ttyS0 -a

Key stty options:

Step 3: Test Serial Communication

Before enabling SLIP, verify you can communicate with the WiRSa:

# Open a simple terminal session
# Press Ctrl+C to exit when done
sudo cat /dev/ttyS0 &
echo "AT" | sudo tee /dev/ttyS0

# You should see "OK" response from WiRSa
# Kill the background cat process
kill %1

# Alternative: use screen or minicom
screen /dev/ttyS0 115200
# (Press Ctrl+A then K to exit screen)

Step 4: Start SLIP Gateway on WiRSa

From your terminal session with WiRSa, enter SLIP mode:

AT$SLIP

Or dial into SLIP mode:

ATDT SLIP

You should see "CONNECT SLIP" response. Now exit your terminal program (the serial port must be free for slattach).

Step 5: Enable SLIP on Linux

Attach the SLIP interface using slattach:

# Start slattach in the background
# -p slip = SLIP protocol
# -s 115200 = baud rate
sudo slattach -p slip -s 115200 /dev/ttyS0 &

# Note the PID for later cleanup
SLATTACH_PID=$!

Step 6: Configure the Network Interface

Once slattach is running, a sl0 interface will be created. Configure it:

# Bring up the interface with the client IP
sudo ifconfig sl0 192.168.7.2 pointopoint 192.168.7.1 up

# Or using ip command (modern systems)
sudo ip addr add 192.168.7.2 peer 192.168.7.1 dev sl0
sudo ip link set sl0 up

# Add default route through the SLIP gateway (optional - routes all traffic through WiRSa)
sudo ip route add default via 192.168.7.1 dev sl0

# Or add only specific routes
sudo ip route add 8.8.8.8 via 192.168.7.1 dev sl0

Step 7: Configure DNS

Add the DNS server to your resolver configuration:

# Temporary - add to /etc/resolv.conf
echo "nameserver 8.8.8.8" | sudo tee -a /etc/resolv.conf

# For systems using systemd-resolved
sudo resolvectl dns sl0 8.8.8.8

Step 8: Test the Connection

Verify connectivity through the SLIP link:

# Ping the WiRSa gateway
ping -c 3 192.168.7.1

# Ping an external IP (Google DNS)
ping -c 3 8.8.8.8

# Test DNS resolution
ping -c 3 google.com

# Check routing
ip route show

Expected output for successful ping:

PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
64 bytes from 192.168.7.1: icmp_seq=1 ttl=64 time=5.23 ms
64 bytes from 192.168.7.1: icmp_seq=2 ttl=64 time=4.89 ms
64 bytes from 192.168.7.1: icmp_seq=3 ttl=64 time=5.01 ms

Step 9: Cleanup (When Done)

To disconnect and clean up:

# Bring down the interface
sudo ip link set sl0 down

# Kill slattach
sudo kill $SLATTACH_PID
# Or find and kill by name
sudo killall slattach

Complete Setup Script

Here's a complete script to automate the Linux SLIP setup:

#!/bin/bash
# slip-connect.sh - Connect to WiRSa via SLIP

DEVICE="/dev/ttyS0"
BAUD="115200"
LOCAL_IP="192.168.7.2"
GATEWAY_IP="192.168.7.1"
DNS="8.8.8.8"

# Configure serial port
sudo stty -F $DEVICE $BAUD cs8 -cstopb -parenb raw -echo

# Start slattach
sudo slattach -p slip -s $BAUD $DEVICE &
sleep 2

# Configure interface
sudo ip addr add $LOCAL_IP peer $GATEWAY_IP dev sl0
sudo ip link set sl0 up

# Add route for external traffic
sudo ip route add default via $GATEWAY_IP dev sl0

# Configure DNS

Troubleshooting

Configuration AT Commands

SLIP Configuration:

PPP Configuration:

Exiting SLIP/PPP Mode

• Press the BACK button on the WiRSa
• Send +++ escape sequence (USB serial only in SLIP mode)
• Disconnect from the client side (PPP will detect link termination)

Telnet Server Mode

The WiRSa includes a built-in Telnet server that allows remote access to devices connected via the serial port. This is useful for:

• Vintage terminals and computers - Access systems that originally connected to serial terminals (mainframes, minicomputers, Unix systems)
• Serial console access - Remotely manage routers, switches, or embedded devices with serial management ports
• Headless systems - Access single-board computers or systems without displays
• BBS hosting - Run a BBS on a vintage computer and accept telnet connections

How It Works

1. The WiRSa listens for incoming TCP connections on a configurable port (default: 23)
2. When a connection is made, data is bridged bidirectionally between the telnet client and the serial port
3. The remote user interacts with whatever is connected to the WiRSa's serial port as if they were locally connected

Configuration

Set the listening port:

AT$SP=23        - Set server port to 23 (default telnet port)
AT$SP=2323      - Use alternate port 2323
AT$SP?          - Query current port

Configure auto-answer:

ATS0=1          - Enable auto-answer (automatically connect incoming calls)
ATS0=0          - Disable auto-answer (ring and wait for manual answer)
ATS0?           - Query current setting

Telnet protocol handling:

ATNET1          - Enable telnet IAC sequence handling (recommended for telnet clients)
ATNET0          - Disable telnet handling (raw TCP mode)
ATNET?          - Query current setting

Connecting to the WiRSa

From any computer on the same network:

telnet <wirsa-ip-address> 23

Or with a custom port:

telnet <wirsa-ip-address> 2323

Console Mode vs Call Mode

The WiRSa supports two types of incoming connections:

Console Connection (First Connection):

• The first telnet connection becomes a "console" session
• Stays in AT command mode - you can type AT commands
• Use ATDT <host:port> to dial out to BBSes
• Full modem emulation available

Call Connection (With Auto-Answer):

• When ATS0=1 is set, subsequent connections bridge directly to serial
• Data passes transparently between telnet and serial
• Use +++ to escape back to command mode
• Use ATH to hang up

Example: Remote Terminal Access

Scenario: You have a vintage Unix system with a serial console, and you want to access it remotely via telnet.

1. Connect the WiRSa to the Unix system's serial port
2. Configure WiRSa to match the system's serial settings:

   AT$SB=9600      - Set baud rate (match your system)
   ATS0=1          - Enable auto-answer
   ATNET1          - Enable telnet handling
   AT&W            - Save settings

3. From a remote computer, telnet to the WiRSa's IP address
4. You'll be connected directly to the Unix system's serial console

Example: Hosting a BBS

Scenario: Run a BBS on a vintage computer and accept incoming telnet connections.

1. Connect WiRSa to the vintage computer running BBS software
2. Configure WiRSa:

   AT$SP=23        - Listen on port 23
   ATS0=1          - Auto-answer incoming connections
   ATNET1          - Handle telnet protocol
   AT&W            - Save settings

3. Configure your router to forward port 23 to the WiRSa's IP address
4. Users can now telnet to your public IP to access the BBS

Manual Answer Mode

When auto-answer is disabled (ATS0=0), incoming connections trigger a "RING" message:

RING
RING
RING

To answer manually, type:

ATA             - Answer the incoming call

This is useful when you want to screen incoming connections or when the connected device needs preparation before accepting a connection.

Diagnostics

The Utilities menu provides diagnostic tools for troubleshooting:

• Signal Monitor - Real-time display of RS232 signal states (DCD, RTS, CTS, DTR, DSR, RI)
• Loopback Test - Test serial communication integrity
• Statistics - View connection counts and byte transfer statistics

Hardware Connections

Pin Assignments

Navigation Buttons

Building the Firmware

This is a PlatformIO project. See README-PLATFORMIO.md for detailed build instructions.

Quick start:

# Build firmware
platformio run

# Upload to ESP32
platformio run --target upload

# Monitor serial output
platformio device monitor

Origin Story

The WiRSa originated as a film prop for Apple TV's "The Shining Girls," where it simulated realistic computer interaction by playing back pre-recorded text files while actors typed on vintage terminals.

Resources

• Source Code: Complete firmware, schematics (KiCAD), Gerber files, and enclosure designs (OpenSCAD) available in this repository
• Contact: nullvalue@gmail.com

License

MIT License - See source code header for full license text.

Copyright (C) 2026 Aron Hoekstra