NBNetworkBridgeMerged Project View Merged

PROJECT UPDATE • IDEA CREDIT

NetworkBridge has been merged into Bow's MiniNet

Bow has taken the NetworkBridge idea suggested by u/TheBigNeku and felt the best direction was to merge this idea into Bow's existing MiniNet project instead of maintaining two projects growing toward the same goal.

Development is now continuing as Bow's MiniNet. The active project can be found at mininet.potterservice.com.

This NetworkBridge site will stay active as a reference to where the idea came from and, most importantly, to show thanks and give credit to u/TheBigNeku for the suggestion that helped shape MiniNet.

Please note: This reference site does not provide a download. Downloads and current project information belong on the active MiniNet website.

Visit Bow's MiniNet

MERGED IDEA • NOT YET A FINISHED PRODUCTCentralized network service management

One place for DNS,
service routing, and host access.

NetworkBridge is a self-hosted concept for managing DNS records and application/service routing together—without losing normal access to the host on other ports such as SSH.

How it could workSee architecture concept
DNSReverse ProxyPort MappingLAN ServicesSSH PreservedSelf-Hosted

Built and developed by Bow of Potter Service.

NetworkBridgeLAN Services
media-server
192.168.1.25
Online
jellyfin.home→8096 → HTTPS
ssh→22 remains direct
app-server
192.168.1.31
Online
app.home→3001 → 443
admin.home→8080 → 443
Inspired by Reddit

Project idea from u/TheBigNeku

They described being tired of managing DNS and reverse-proxy configuration in separate places. Their goal is a simpler central tool that understands both host-level DNS and service-level routing while preserving access to ports like SSH.

The problem

DNS knows the host. Reverse proxies know web services. The two are often disconnected.

A DNS record can point to the server, but users still have to remember service ports. A reverse proxy can hide web ports, but it does not replace direct host access for other protocols.

🌐

DNS Only

server.home resolves correctly, but users still type ports like :3001, :8096, or :8080.

↪

Proxy Only

Web traffic can be routed cleanly to 80/443, but SSH and other non-HTTP services still need normal host connectivity.

🔗

NetworkBridge

Manage host identity and service routes in one place so application names and direct host access coexist.

Example

One server. Multiple services. No lost SSH.

The same host can keep direct access on port 22 while friendly service names route web traffic to internal ports.

NameTargetService PortBehavior
server.home192.168.1.3122Direct SSH
app.home192.168.1.313001HTTPS route
admin.home192.168.1.318080HTTPS route
api.home192.168.1.315000HTTPS route
What makes it different

Not a full IPAM. Not a proxy on every machine.

The request specifically calls for something simpler than an IPAM and less cumbersome than installing a separate reverse proxy on each host.

Central DNS

Manage local hostnames and records from one interface.

Central Service Routes

Define friendly names for HTTP/HTTPS apps running on internal ports.

Direct Host Access

Keep SSH and other non-web ports reachable normally.

Simple Inventory

Show hosts, IPs, services, and routes without becoming a heavyweight IPAM suite.

Networking complexity: This is a concept, and the exact design needs careful research. DNS, HTTP reverse proxying, TCP/UDP forwarding, TLS, local certificates, port conflicts, firewall rules, and network topology all affect what can be centralized safely.
More projects from Bow

See other Potter Service projects.

NetworkBridge is a merged project being built and developed by Bow of Potter Service.

View Bow's Projects