Share Surge Proxy Across the LAN
·
2 min read
·
301
Words
·
-Views
-Comments
Surge handles per-device proxying nicely, but what about other hardware—smart TVs, Nintendo Switch, etc.? Here are two approaches I use so those devices can hop the firewall without installing Surge.
Use case: the Switch needs a proxy to post to Twitter.
Option 1: Manual Wi-Fi Proxy
- Ensure iPhone and Switch are on the same Wi-Fi network.
- On the iPhone running Surge, enable Allow Wi-Fi Access.
- On the Switch, set Wi-Fi proxy to the IP/port shown in Surge.
- Post on Twitter—if it succeeds, you’re done.
macOS Surge works similarly; iPhone is just the example here.
Option 2: macOS DHCP Gateway
Only available on macOS. Treat your MacBook Pro as a bypass gateway.
- Disable DHCP on the router (e.g., router IP
192.168.31.1
). - Assign a static IP to the Mac (e.g.,
192.168.31.2
). - In Surge for Mac, enable DHCP. Surge checks the router’s DHCP status and proceeds if it’s off. Recommended IP range:
100-200
. Devices that should bypass Surge can stick to addresses outside the range (e.g.,3-99
). - Restart the router. As devices reconnect, Surge will list them. By default they do not use Surge as a gateway; right-click each device and select Use Surge as Gateway. Reconnect the device to apply.
Disabling DHCP
- In Surge → Devices, turn off DHCP Server.
- Re-enable DHCP on the router and reconnect devices.
Practical Notes
- Using a primary Mac as a soft router is heavy-handed. I only route select devices through Surge and leave others on the router gateway for stability.
- Devices already running Surge (iPhone/iPad) can still use the router gateway (
192.168.31.1
) to avoid double proxying. - Non-Apple devices get
Use Surge as Gateway
so they benefit from Surge rules/ad blocking.
Final Thoughts
I’m a Surge fan, so these solutions revolve around it. Each approach has trade-offs, but together they let non-Surge devices enjoy an open internet quickly.