[Background]
If you connect the Starlink dish to Peplink router WAN ports in DHCP/NAT mode, with an automatic DNS, and would like to use the management app (as LAN client) to manage the dish via IP: 192.168.100.1.
We have a new feature introduced in the special firmware (8.1.1s118) to allow you to do so.
Topology:
[Starlink Dish (Bridge Mode)] === [WAN | Peplink | LAN] === [LAN Client Device]
[Special Firmware]
Here are the download links:
Go to the WAN Connection Settings, check the “Connection Method” = “DHCP”, click on the (?) beside the “Hostname (Optional)”, then click on the “here” to proceed.
Enter the “Management IP Address”, which can be range from 192.168.100.2 - .254 (eg. 192.168.100.100), leave the subnet mask as it is. Then save the settings and click the Apply Changes to activate the feature.
You should able to access the Starlink Dish via 192.168.100.1.
[Relevant threads]
Starlink and Peplink Balance
Starlink app fix
[Update - Firmware 8.4.0 onwards]
A new detection mechanism was added to the router firmware to recognize the upstream Starlink Dish once the [Starlink Support,
#30479
] feature is enabled.
LAN client at the Peplink router can access the Starlink Dish via IP: 192.168.100.1 without adding the “Management IP Address”, in both Router and Bypass Mode.
The Starlink Dish management Web Portal depends on the Starlink devices, which we found it is not available since a few months back, eg. from this
3rd party article
.
Works great on my old Balance 50. (Side note, no obstructions! That goofy mast mount on the roof that the wife hates proved itself.)
Thanks for this fix.
Update: I initially tried to update via wifi using a Mac, and was unsuccessful, twice. I later download the firmware to a Windows machine connected to the router via ethernet and was successful.
Have tried to update my Balance 30 LTE using the appropriate download link (the one above the group that includes the B30 LTE , HW3) and I keep getting a message that the firmware image is invalid. It downloads, and then uploads to the router, but when it try to use it, that message appears. I tried it first without unzipping the file (twice, no good) and then I tried unzipping the file first, but my Mac’s utility says it’s an unrecognized format. So, unable to proceed. Any ideas?
@sbi108
I checked the management option for my Balance One device (LAN as WAN enabled) and I’m able to enable the management IP address option. Just to confirm do you follow the steps as given above ?
@Madcodger
Please open a ticket for support team to check if you confirmed your device is B30 LTE HW3 and failed to use the firmware.
https://ticket.peplink.com/ticket/new/public
Hi Sitloongs,
Oops, I did not follow the instructions properly the first time. After your email below I tried again and followed the instructions carefully. Everything works. Please forgive my mistake and thank you for helping me!
Please close this ticket and thank the Peplink staff for adding this feature.
best to all, Steve
@WeiMing
thanks for this revision! I was able to connect to the management GUI of a non-Starlink LTE-modem in DHCP mode. Could the Management IP config also be enabled this feature for Static IP mode as well? I have a DSL modem with static IP and would love to be able to access its management GUI as well. Thanks again!
I could also use that feature, I have DSL modems to manage with static IP WAN interface assignments.
Currently I have to deploy an additional Juniper SRX to be able to manage the modem.
https://www.reddit.com/r/Starlink/comments/msfy4k/dhcp_option_121_no_more_need_to_add_a_static/
Looks like they are going to push the management routes over option 121 if the DHCP client supports/requests routes via 121 instead of 3
