gdy666/lucky

软硬路由公网神器,ipv6/ipv4 端口转发,反向代理,DDNS,WOL,ipv4 stun内网穿透,cron,acme,rclone,ftp,webdav,filebrowser

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 8th, 2026
Created on July 13th, 2022
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 732
Total Stargazers: 8,127 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Lucky is a port forwarding and network utility tool that runs on Linux embedded devices and routers.

Lucky addresses the need for flexible network access and service exposure on resource-constrained devices. It originated as a personal tool to replace socat for exposing internal IPv4 services over public IPv6 on consumer routers. The tool is built entirely in Go for efficiency and cross-platform compatibility, with a Vue 3.2 frontend and a REST API that third-party developers can integrate with. Its core capabilities include IPv6 and IPv4 port forwarding, reverse proxying, dynamic DNS, network wake-on-LAN, scheduled tasks, automatic certificate management via ACME, and network storage access through FTP, WebDAV, and file browser interfaces. It also includes STUN-based NAT traversal for accessing services behind restrictive firewalls.

The tool suits users running custom firmware on routers or embedded Linux systems who need to expose internal services without complex infrastructure. It is designed to minimize setup complexity and learning overhead for non-technical users while maintaining network security awareness. The project maintains a web-based management interface for configuration and monitoring.

Development has been active with regular iteration based on user feedback and feature requests. The maintainer has stated that source code is published up to a specific version with no plans for continued open-source releases beyond that point. The project is no longer accepting contributions as free labor, with the developer prioritizing their own vision for the tool's direction over community-driven development.