The problem
If you’re running Starlink behind a Peplink in Drop-In Mode, you’ll likely hit a wall: Starlink only gives you one public IPv4 address per line — no routed block, no spare address to split between the Peplink and your downstream firewall/router.
Worth knowing about that IP specifically: Starlink assigns it dynamically via DHCP, but with a reservation that keeps it stable across a dish reboot or brief power loss. It can still change due to network maintenance on Starlink’s end, a change in your Point of Presence (which can happen if the dish physically moves), or if the terminal stays powered off longer than the DHCP lease period (24 hours). Good to keep in mind if you’re publishing that IP anywhere external.
What Drop-In Mode normally expects
Drop-In Mode lets the Peplink sit transparently between your ISP and an existing router/firewall, bridging a public IP through so the downstream device can use it directly with no reconfiguration needed on that device. The catch: the standard setup wants two IPs, one for the Peplink itself, one for the device behind it. With a real routed block (say, a /30 from a fiber ISP) that’s no problem. With Starlink’s single IP, there’s nothing left over for the Peplink to use for itself and if you try anyway, you’ll get an IP address conflict, because you’re essentially trying to put two devices on the same address.
The fix: Share Drop-In IP + a link-local Management IP
Under Network > LAN > (your LAN) > Drop-In Mode Settings, there’s a Share Drop-In IP checkbox. Enabling this lets the Peplink and your downstream device share the same single IP, instead of requiring two.
That solves the addressing conflict — but it raises a new question: if the Peplink no longer has its own address on that public IP, how do you get into its admin page? This is where the Management IP Address field comes in. Peplink’s own guidance on this field is simply that it needs “a free IP/subnet that routes to the router” but when you genuinely have zero spare addresses anywhere (our case, and likely yours if you’re on Starlink), there’s nothing to route to it from your public side at all.
The fix: use a link-local address — 169.254.0.1/24 — for the Management IP field. This range (RFC 3927) is reserved specifically for local-segment-only communication; routers are required by the standard to never forward it anywhere. That means it can’t conflict with your public IP, your ISP, or anything else. It only has to work between the Peplink and whatever you plug directly into it. To use it: connect your laptop straight to the Peplink, manually set your NIC to something like 169.254.0.2/24, then browse to 169.254.0.1.
Step by step, matching the screenshots
- Screenshot 1: LAN settings before Drop-In is touched — normal IP address (
192.168.50.1/24), Inter-VLAN routing on.
- Screenshot 2: Enable Drop-In Mode, pick the WAN carrying your Starlink connection, and leave “Apply NAT on VLAN networks outgoing Internet traffic” checked unless you have a specific reason not to.
- Screenshot 3: This is the important one —
- Management IP Address:
169.254.0.1/24(see above for why) - Share Drop-In IP: checked
- Shared IP Address: your single Starlink public IP
- WAN Default Gateway: your Starlink WAN’s gateway IP
- Static Route: only needed if something behind your downstream router needs the Peplink to know how to reach it — leave blank otherwise
Related thread: there’s a 2018 thread that covers the same core issue from a cable-ISP angle (also a fully-consumed subnet with zero spare IPs). How do you access the Balance/MAX when using drop-in mode and only 1 Static IP?