轩辕镜像 官方专业版
轩辕镜像
专业版
轩辕镜像 官方专业版
轩辕镜像
专业版
首页个人中心搜索镜像
交易
充值流量¥7起我的订单
文档
工具
提交工单页面收录
source-broadcast-proxy

boombatower/source-broadcast-proxy

boombatower
自动构建

下载次数: 0状态:自动构建维护者:boombatower仓库类型:镜像最近更新:7 年前
让 AI 帮你使用轩辕镜像? · 展开查看说明 · 点击收起说明

如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具,协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题,请先让 AI 阅读并遵守轩辕镜像的规则文档。

只需在 AI 对话中先发送下面这句话即可:

请先完整阅读并严格遵守以下文档中的全部规则与要求:

https://xuanyuan.cloud/agents.md

在未充分阅读并理解该文档前,不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。

查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式,不推荐豆包 AI;Cursor 等编辑器可在对话 @ 该链接,或加入 User Rules。 若 AI 无法访问外链,可 打开说明文档 复制全文粘贴。文档会随站点更新,复制内容可能过期,建议定期检查。

镜像简介
下载命令
镜像标签列表与下载命令
使用轩辕镜像,把时间还给真正重要的事。
点击查看

boombatower/source-broadcast-proxy

Forwards Valve's Source Engine LAN broadcast packets to non-default ports.

By proxying the broadcast packets more than the default 5 Source servers can be hosted on the same machine/IP while still being displayed in the LAN server browser. Great for LAN parties with powerful servers (such as large organized ones).

This implementation is designed to work with Source servers hosted in Docker containers that expose one of the default 5 ports. No configuration is necessary as the proxy will detect running containers and scan the exposed ports to determine which are potential Source servers.

Docker configuration

Docker must be configured to expose its API via a TCP interface. See the relevant http://docs.docker.com/installation/ for information on configuration location and such. It may already be configured to expose the API and there is no harm in just running the proxy and see if it blows up.

For most setups something like the following should be in the configuration file in addition to any other options.

DOCKER_OPTS="-H tcp://127.0.0.1:2375"

If a non-default port is used it must be communicated to the proxy during startup by adding the following to the command in the usage section (with the relevant port).

-e DOCKER_PORT=***

Usage

In general the following command should do the trick.

sh
$ docker run -d --net host --restart 'on-failure' boombatower/source-broadcast-proxy

-d Detaches since there should not be any need to watch the proxy.

The reason for --net host is to ensure easy access to Docker API port without having to setup forwarding rules and what not from the Docker network device to the host. It also simplifies forwarding to the Source servers since they can be accessed directly on the host ports instead of needing to be accessed via the Docker gateway.

--restart 'on-failure' does exactly what it says to ensure the proxy stays running.

Source server containers

Either build Docker images for the Source servers you are interested in hosting and/or search for existing images to start from. For example: Google docker tf2.

Since the port does not matter disregard any instructions about mapping ports using -p. For example mapping the default Source port to the host -p 27015:27015/udp. Instead use the upper-case -P to have Docker pick a free port on the host so one does not have to bother keeping track of ports since the proxy will do so.

Fakes servers

To test a setup ahead of time it is recommended launch a bunch of lightweight fake servers using https://github.com/boombatower/source-server-fake.

Result

Host as many Source servers in Docker containers as desired and have them all show up in the LAN server browser!

!Screenshot of Steam server browser LAN tab

Example of running Docker containers

CONTAINER ID        IMAGE                                       COMMAND                CREATED              STATUS              PORTS                      NAMES
0b8bd698a033        boombatower/source-broadcast-proxy:latest   "/usr/***/php proxy.   About a minute ago   Up About a minute                              source-broadcast-proxy
9922fefab279        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49199->27015/udp   agitated_hoover
ebf2edaa5be1        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49198->27015/udp   sleepy_pare
be25aa3ead96        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49200->27015/udp   happy_curie
81de73a90d06        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49193->27015/udp   happy_darwin
1f6163b48d71        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49197->27015/udp   backstab***g_tesla
2aa213eb91e7        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49196->27015/udp   stupefied_shockley
271b17e7bbcb        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49195->27015/udp   drunk_hoover
06b4d4a1d7f7        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49194->27015/udp   grave_lalande
1e54128e39d7        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49190->27015/udp   high_sinoussi
9ecfaa7d9eda        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49192->27015/udp   jovial_bardeen
0263ed6168b9        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49191->27015/udp   stoic_babbage
aec1f91d7e03        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49189->27015/udp   stoic_shockley
25ebb8033f4b        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49187->27015/udp   elegant_poincare
85dbaa4ebca7        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49188->27015/udp   kickass_kirch
4dab148d160c        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49186->27015/udp   loving_bell
4b8033ecb57a        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49185->27015/udp   prickly_bohr
58d9a1fc3481        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49183->27015/udp   cranky_stallman
91c2eb23c7ef        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49184->27015/udp   boring_franklin
eb5a975ac308        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49182->27015/udp   dreamy_archimedes
efa55e1a37ce        boombatower/source-server-fake:latest       "/usr/***/php fake.p   About a minute ago   Up About a minute   0.0.0.0:49181->27015/udp   sleepy_turing

Example Proxy output

Received A2S_INFO request from 192.168.7.17:43781
-> Forwarding to Source server on port 49199
-> Forwarding to Source server on port 49198
-> Forwarding to Source server on port 49200
-> Forwarding to Source server on port 49193
-> Forwarding to Source server on port 49197
-> Forwarding to Source server on port 49196
-> Forwarding to Source server on port 49195
-> Forwarding to Source server on port 49194
-> Forwarding to Source server on port 49190
-> Forwarding to Source server on port 49192
-> Forwarding to Source server on port 49191
-> Forwarding to Source server on port 49189
-> Forwarding to Source server on port 49187
-> Forwarding to Source server on port 49188
-> Forwarding to Source server on port 49186
-> Forwarding to Source server on port 49185
-> Forwarding to Source server on port 49183
-> Forwarding to Source server on port 49184
-> Forwarding to Source server on port 49182
-> Forwarding to Source server on port 49181
Handled in 0.010501 seconds
Received A2S_INFO request from 192.168.7.17:34473
-> Sending 20 cached responses
Handled in 0.000104 seconds

镜像拉取方式

您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。

轩辕镜像加速拉取命令点我查看更多 source-broadcast-proxy 镜像标签

docker pull docker.xuanyuan.run/boombatower/source-broadcast-proxy:<标签>

使用方法:

  • 登录认证方式
  • 免认证方式

DockerHub 原生拉取命令

docker pull boombatower/source-broadcast-proxy:<标签>

轩辕镜像配置手册

按平台快速找到配置文档

一键安装

一键安装 Docker

Linux Docker 一键安装

AI

用 AI 使用轩辕镜像

agents.md · AI 对话 · 提示词

Docker

登录仓库拉取

登录认证 · 私有仓库

专属域名拉取

免登录 · 高速拉取

Linux

Docker 镜像配置

Windows / Mac

Docker Desktop 配置

MacOS OrbStack

OrbStack 容器

Apple Container

macOS 原生容器

Docker Compose

Compose 项目配置

NAS

群晖

Synology 配置

飞牛

fnOS 镜像配置

绿联

绿联 NAS

威联通

QNAP 配置

极空间

极空间 NAS

Unraid

Unraid NAS

企业仓库

其他仓库

ghcr · Quay · nvcr

Harbor 镜像源

Proxy Repository 对接

Portainer 镜像源

Registries 配置

Nexus 镜像源

Docker Proxy 缓存

开发工具

Dev Containers

VS Code 开发容器

Podman

Podman 配置指南

Singularity / Apptainer

HPC 科学计算容器

Kubernetes

K8s Containerd

Kubernetes · Containerd

K3s

轻量级集群

面板 / 网络

爱快路由

iKuai 镜像加速

宝塔面板

一键配置镜像源

需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单

镜像拉取常见问题

功能

版本功能对比

功能对比 · 版本选择

支持的镜像仓库

Docker Hub · GCR · GHCR

新手拉取配置

登录 · 专属域名 · 配置

docker search 限制

专属域名 · Hub 搜索

不支持 push

仅支持 pull · 不支持

拉取速度原因

带宽 · 缓存 · 冷热镜像

错误码

402 与流量用尽

402 · 流量包 · 充值

401 认证失败

401 · docker login

manifest unknown

标签错误 · 镜像不存在

410 Gone 排查

410 · Docker 升级

429 限流

免费版 · 专业版 · 企业版 · 请求频率

其他报错

DNS 超时

DNS 解析 · 网络超时

TLS 证书失败

no matching manifest(架构)

账号

失败是否计费

manifest · blob · 计费

申请开发票(企业 / 个人)

企业 · 个人 · 工单

修改登录密码

网站 · 仓库 · 重置

注销账户

工单 · 数据 · 注销

原理

mirrors 不生效

daemon.json · 重启

去掉域名前缀

docker tag · 重命名

指定架构拉取

ARM64 · AMD64 · 多架构

latest 与「最新」

digest · 版本号 · 标签

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
boombatower/source-broadcast-proxy
教程轩辕镜像功能与使用教程
定价查看流量套餐与价格
热门查看热门 Docker 镜像推荐
博客Docker 镜像公告与技术博客
专业版 · 高速稳定拉取镜像
高速镜像下载·在线技术支持·99.95% SLA 保障·付费会员免广告
50GB 仅 ¥7/年
专业版 · 高速稳定拉取镜像
50GB 仅 ¥7/年
高速镜像下载·在线技术支持·99.95% SLA 保障·付费会员免广告
用户协议·隐私政策·增值电信业务经营许可证:浙B2-20261007·©2024-2026 源码跳动©2024-2026 杭州源码跳动科技有限公司·商务合作:点击复制邮箱

更多 source-broadcast-proxy 镜像推荐

haproxytech/haproxy-debian logo

haproxytech/haproxy-debian

haproxytech
HAProxy社区版Docker Debian镜像,提供高性能的开源负载均衡和应用交付控制功能,支持TCP/HTTP代理、SSL终止、健康检查等特性,适用于构建可靠的流量管理解决方案。
9 次收藏1000万+ 次下载
1 天前更新
haproxytech/haproxy-alpine logo

haproxytech/haproxy-alpine

haproxytech
HAProxy社区版Docker镜像,基于Alpine Linux构建,提供高性能负载均衡与反向代理功能,适用于构建轻量级、高可用的Web服务或应用集群。
19 次收藏500万+ 次下载
2 天前更新
haproxytech/haproxy-ubuntu logo

haproxytech/haproxy-ubuntu

haproxytech
HAProxy社区版Docker Ubuntu镜像
6 次收藏100万+ 次下载
2 天前更新
haproxytech/haproxy-qns logo

haproxytech/haproxy-qns

haproxytech
该Docker镜像包含用于HAProxy的QUIC互操作性测试文件
2 次收藏10万+ 次下载
2 天前更新
haproxy logo

library/haproxy

Docker 官方镜像
HAProxy是一款可靠的高性能负载均衡器,主要用于TCP和HTTP协议的流量分发,能够有效均衡服务器负载、提高系统可用性与响应速度,广泛应用于Web服务、数据库集群等场景,通过智能流量调度确保服务稳定运行,是构建高可用、高性能网络架构的关键工具。
2.0千 次收藏10亿+ 次下载
8 天前更新
envoyproxy/envoy logo

envoyproxy/envoy

envoyproxy
云原生高性能边缘/中间层/服务代理
181 次收藏10亿+ 次下载
23 小时前更新

查看更多 source-broadcast-proxy 相关镜像