Hi there. I cannot access my Starlink’s admin functions when connecting to it through my Pepwave Max Transit Duo. I can only access Starlink’s admin dashboard when I connect directly to the Starlink router’s wifi.
I have the latest firmware on my Pepwave and Starlink is fully up to date as well. I configured the Management IP of my Pepwave to 192.168.100.100. I also tried 192.168.100.2. This did not work.
I then tried adjusting my outbound policy to ensure that all traffic going to 192.168.100.1 is routed to the WAN port for Starlink. I also created a policy for dishy.starlink.com. This did not work.
I have a Pepwave MAX Transit Duo and Starlink (Square). The Starlink Router is connected via ethernet to my MAX Transit Duo’s WAN port. For internet traffic, everything is working great in conjunction with my cellular WAN services.
I intend to delete the Starlink Router from my setup, but before I do, I want to make sure I can access the admin interface without it as I’ve seen lots of other people do in the forums here and on Reddit.
I’m sure somebody will be along shortly to tell you how to do this on the Pepwave. I’m not familiar enough with it to be that one
But if your Pepwave device’s LAN IP address is 192.168.100.100 I’m going to assume the Peplink’s LAN network address is 192.168.100.0/24? If so: Nothing between 192.168.100.0 and 192.168.100.255 will be routed to the Pepwave device’s WAN port, because it will regard everything in that network range to be on its LAN side.
In order to persuade the Pepwave to route to the Starlink’s management interface, the Starlink’s interface IP will have to be in a netblock distinct from that of the Peplink’s LAN netblock, such as 192.168.200.0/24, with an IP address of 192.168.200.1, for example.
Ok, so it looks like the management interface on the Starlink should be available at 192.168.1.1?
And, since the Pepwave already knows where the 192.168.1.0/24 network is, and the Starlink knows the device to which it assigned 192.168.1.150, they can talk to one another.
If the Pepwave didn’t do it for you, you will have to add a NAT rule on the WAN interface, so traffic coming from your 192.168.100.0/24 LAN network all looks like it’s coming from 192.168.1.150. Otherwise the Starlink will need a route entry added to it so it knows how to get back to your LAN subnet.
E.g.: “network 192.168.100.0/24 gateway 192.168.1.150” or the like.
Are outbound policy rules called “Pep VPN / OSPF / BGP / RIPv2 Routes Speedfusion Cloud Routes” on the max transit?
Or is there another Outbound Policy section (under Network?) to put outbound rules for traffic that is routed before traffic is directed to the speedfusion wan?
Wondering if you solved it and if it was related to the outbound policy rule order needing to come before traffic gets routed to the speedfusion WAN?
(Not sure if this is on target or off base, but curious if you solved it.)
hmmm tried that … but still no success … I have put 192.168.100.100 as management IP … and tried 192.168.100.1 to reach dishy page without success
any other configs to make it peplink admin ?
cheerz
I appreciate you chiming into the other thread, and would REALLY appreciate any help - I don’t believe the solution posted here resolves my issue, but I could be wrong…
I am NOT using the Starlink router and therefore my dish is connected directly to the Pepwave router. It does NOT have an 192.168.xxx.xx IP address.
It has a 100.127.xxx.xx IP address with a 255.192.0.0 submask.
I have tried the solutions posted here to no avail (they used to work when I had the Starlink router and 192.168.xxx.xx IP address).
I have tried a few IP addresses in the 100.127.xxx.xx range with what I think is the correct submask, but can’t figure it out.
Even when connected to the dish directly and your device gets a public /CGNAT IP from starlink for internet access, you can still access the dish’s web interface by setting the management IP on the WAN to 192.168.100.x (where x is not 1) and then navigating to http://192.168.100.1
It has been reported that Starlink support is telling people that web access has been deprecated. so the Starlink LOGO at http://dishy.starlink.com/ is a final destination
… it was the wrong management IP subnet mask … it has to be 255.255.255.255/32 in my case … everything works now as expected