nemunaire/repeater
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
36 commits 1 branch 0 tags 637 KiB
  • Go 73.7%
  • JavaScript 14.8%
  • CSS 7.9%
  • HTML 3.4%
  • Makefile 0.2%
Find a file
Exact
Pierre-Olivier Mercier 310cce2a45 app: Detect Ethernet uplink via default route, not address flags 
probeEthernet looked for a "DHCP-assigned" address using the `dynamic`
flag or a finite `valid_lft`. udhcpc (BusyBox) installs the leased
address with a plain `ip addr add` and no lease lifetime, so the address
shows `valid_lft forever` and no `dynamic` flag — indistinguishable from
a static LAN/hotspot address on the same interface. The uplink was never
recognized and wpa_supplicant was started despite working connectivity.

Detect the uplink via the interface's default route instead, which is
reliable across udhcpc and full iproute2, and report the uplink source
address from `ip route get` so the UI shows the DHCP address rather than
a co-located static one.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-05 09:51:44 +08:00
cmd/repeater app: Show pulsing loading dots until first status fetch 2026-06-10 18:08:27 +09:00
internal app: Detect Ethernet uplink via default route, not address flags 2026-07-05 09:51:44 +08:00
.gitignore Migrate to a better architectured project 2026-01-01 23:31:01 +07:00
generate.go Add OpenAPI specs 2025-10-28 18:25:45 +07:00
go.mod Migrate to a better architectured project 2026-01-01 23:31:01 +07:00
go.sum Add OpenAPI specs 2025-10-28 18:25:45 +07:00
Makefile Migrate to a better architectured project 2026-01-01 23:31:01 +07:00
oapi-gin.cfg.yaml Add OpenAPI specs 2025-10-28 18:25:45 +07:00
oapi-types.cfg.yaml Add OpenAPI specs 2025-10-28 18:25:45 +07:00
openapi.yaml app: Surface Ethernet uplink in the UI and gate wpa_supplicant access 2026-05-02 11:24:36 +08:00
README.md Migrate to a better architectured project 2026-01-01 23:31:01 +07:00

README.md

Travel Router Control

A Go application for controlling a mini travel router with dual WiFi interfaces and Ethernet connectivity. The router can operate as a WiFi repeater, connecting to upstream networks while providing a hotspot for client devices.

Features

  • WiFi network scanning and connection management
  • Hotspot (access point) configuration and control
  • Connected device monitoring
  • Real-time system logs via WebSocket
  • RESTful API following OpenAPI 3.0 specification
  • Web interface for easy management

Architecture

The application follows a clean architecture pattern:

.
├── cmd/
│   └── repeater/          # Application entry point
│       ├── main.go
│       └── static/        # Embedded web assets
├── internal/
│   ├── api/              # HTTP API layer
│   │   ├── router.go     # Gin router setup
│   │   └── handlers/     # HTTP handlers
│   ├── app/              # Application logic & lifecycle
│   ├── device/           # Device management
│   ├── hotspot/          # Hotspot control
│   ├── logging/          # Logging system
│   ├── models/           # Data structures
│   └── wifi/             # WiFi operations (wpa_supplicant via D-Bus)
├── openapi.yaml          # API specification
└── go.mod

Building

go build -o repeater ./cmd/repeater

Running

sudo ./repeater

The application requires root privileges to:

  • Access D-Bus system bus for wpa_supplicant
  • Control systemd services (hostapd)
  • Read DHCP leases and ARP tables

The server will start on port 8080.

API Endpoints

WiFi Operations

  • GET /api/wifi/scan - Scan for available networks
  • POST /api/wifi/connect - Connect to a network
  • POST /api/wifi/disconnect - Disconnect from current network

Hotspot Operations

  • POST /api/hotspot/config - Configure hotspot settings
  • POST /api/hotspot/toggle - Enable/disable hotspot

Device Management

  • GET /api/devices - Get connected devices

System

  • GET /api/status - Get system status
  • GET /api/logs - Get system logs
  • DELETE /api/logs - Clear logs

WebSocket

  • GET /ws/logs - Real-time log streaming

See openapi.yaml for complete API documentation.

Configuration

The application uses the following system resources:

  • WiFi Interface: wlan0 (for upstream connection)
  • AP Interface: wlan1 (for hotspot)
  • Hostapd Config: /etc/hostapd/hostapd.conf
  • WPA Supplicant Config: /etc/wpa_supplicant/wpa_supplicant.conf

These can be modified in the respective package constants.

Dependencies

  • Gin: HTTP web framework
  • godbus: D-Bus client for wpa_supplicant control
  • gorilla/websocket: WebSocket support
  • wpa_supplicant: WiFi connection management
  • hostapd: Hotspot functionality

License

MIT