#I did not Can we pm about it
narrow hamlet
Let's do it in a thread, so other people can see. They may help, or learn something too.
clear whale
sure.
So you're starlink is in bypass mode, and you use the starlink integration to get stats?
narrow hamlet
Just remind me where you're add. You did a (starlink) router-delete, and want to get the stats from dishy? You should be able to access it yourself from browser, since HA is fundamentally the same.
Sec, logging into my box, to get the real IPs etc
clear whale
I can't http or https or ping 192.168.100.1
I don't recall doing anything called a router-delete.
narrow hamlet
Are you using the starlink router, as well as dishy?
clear whale
but I have my own router, eth cable to Starlink modem
I would characterise the starlink modem/router device to be in bridge mode. Or some may say L2 or transparent mode. They call it bypass.
narrow hamlet
Unless you need it, you can get rid of it completely.
But principal for access is probably the same...
Defaultroute is not enough. Because IIRC the router doesn't know how/where to respond. Sec, will look at my config
clear whale
Seems like a tangent, but how would I get rid of it entirely? They plugs are proprietary anyway right, certainly nothing like an Eth RJ45
narrow hamlet
You still need the power brick, just not the other thing. Sorry I can't go photograph it, it's on a tall shelf, need a latter
ladder
will find the article, sec
Ah I have v1 dishy, which has it's own power injector, separate from router. Are you v2?
clear whale
It's less than a year old, so I guess I am. It's a square dish if that helps.
narrow hamlet
Yeah mine is round. You might need the router. Anyway, problem is the same...
I added virtual IP on the WAN side of my router, with 192.168.100.2
And told the router to use that to talk to dishy interface.
So it's kindof like there's two subnets on that interface. 192.168.100.*
And 100.64.x which is the dhcp that dishy gives you
clear whale
ah okay, yeah like a secondary ip address on the same interface where you're running the dhcp client (starlink is the dhcp server)
narrow hamlet
the reason you can't access 192.168.100.1 without it is because you're being NATd to the 100.64 address
yes, a secondary IP. I use opnsense, it's pretty easy there. WHich router are you using?
clear whale
I've got an SRX from Juniper Networks
I know how to drive the router. I'll give this a crack when I get some more time.
narrow hamlet
On opnsense I add a virtual IP 192.168.100.2/24 to the WAN interface, and..
Maybe a static route, sec will chekc that.
narrow hamlet
Yup, looks like no static route needed. If the virtual ip is /24 it'll handle it
clear whale
yes, got it. thanks, let me take a look when I have more time.
narrow hamlet
nw
clear whale
appreciate it... cheers
narrow hamlet
Unfortunately it's all cgnat which is a pain for VPN etc. But I think the ipv6 is real
clear whale
oh. do they give v6 address by default? I mean obviously I need to configure it on end, but from their side, it just works outta the box?
narrow hamlet
Yup
narrow hamlet
Sorted?