I wonder how can I disable DHCP on Starlink bridged because I can't connect with DHCP on my local network (OpenWRT).
When I try to connect, the router gives the WAN IP that was used for the router itself.
Plus I can't connect Apple devices with static IPs (192.168.1.X) because the address IP entered is used. I suspect it's related to IPV6 DHCP enabled by default on Mac devices.
My actual configuration:
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0'
list ports 'eth0.1'
list ports 'eth0.2'
config interface 'lan'
option device 'br-lan'
option proto 'static'
list ipaddr '192.168.0.1/24'
option gateway '100.64.100.1'
config device
option name 'eth0.2'
option macaddr 'd8:47:32:59:b2:08'
config interface 'wan'
option device 'br-lan'
option proto 'dhcp'
option hostname '*'
config interface 'wan6'
option device 'br-lan'
option proto 'dhcpv6'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0t 1 2 3 4 5'
option vid '1'
config device
option type 'bridge'
option name 'br-wan'
list ports 'eth0'
list ports 'eth0.1'
list ports 'eth0.2'
config interface 'wwan'
option proto 'dhcp'
option hostname '*'
config device
option name 'eth0'
config switch_vlan
option device 'switch0'
option vlan '2'
option vid '2'
config device
option name 'eth0.1'
option type '8021q'
option ifname 'eth0'
option vid '1'
config device
option name 'phy0-ap0'
config device
option name 'phy1-ap0'
Well, it is the case of "format your router"
The router has to be first dhcp client to connect freshly started starlink. With all openwrt defaults in regard to wan and wan6.
You can save configuration backup before reset, then unzip it to recover likes of wifi passwords etc
To be clear, the two other contributors are not just saying that as some generic thing... your configuration is legitimately entirely nonsensical. If you don't want to reset your router to defaults, you'll end up spending way more time trying to correct the issues that are present.
To be blunt, it reminds me of the line in Apollo 13 where Gene says "What do we have on the spacecraft that's good?" and nobody can answer. So, if you really think we're just telling you to reset for no reason, I'd recommend that you go through the config, line by line, and tell us why you changed each thing.
If the Starlink is bridged, it will only issue one "public" (actually CGNAT) IPv4 address, so you need to configure your OpenWrt router for lan->wan routing. This is the default configuration so you should start there. If you connect a router in default configuration with WAN to the Starlink and LAN to your endpoint devices, it should provide DHCP local addresses and Internet access.
This is one in the same. Resetting your router to defaults is the same as "formatting" it.
I'm honestly not sure how. The config is borked.
Then please explain every change you have made, why you have made it, and your intent for this device on your network (what you want it to do, what services it provides). The existing configuration does not make either of these things apparent.
Nothing could be farther from the truth. I have helped in literally thousands of threads. And Iām willing to help you, too.
Posts, sure. Config, no. Your config is very messed up. Iām not saying that to insult you, but rather to impress upon you that you need to take the advice of those on the forum who are trying to help. After all, you have come here for help because this config is not working, right?
That configuration is faulty but since it basically bridges everything together making a layer 2 "dumb AP". That would technically work if connected to a typical home gateway which does routing instead of being a bridge to the Internet.
What you have done vs. a default configuration seems to be:
All the Ethernet ports are in the same hardware switch VLAN. This is appropriate for a dumb AP but you need to go back to multiple VLANs to implement lan->wan routing.
A plain eth0 is referred to in the config even though in swconfig, the CPU side is always tagged. This is simply wrong. In default settings with two VLANs in the switch, the eth port is eth0.1 for lan and eth0.2 for wan.
The same ports are in two bridges. This is not workable but fortunately br-wan never gets instantiated because...
The wan interface has been deleted. You need one of proto dhcp in order to link to the Starlink and obtain an IP (v4) address and gateway. Also you'd want a dhcpv6 wan6 interface (which is in the default configuration) since Starlink does support IPv6.
You have been given a very good (although possibly not 100% complete) description of the major issues in your config by @mk24 .
Your task now is to fix all of those things, one by one, and make sure you don't make any further mistakes in syntax and/or function. Or... you can do as we have advised -- reset to defaults. You will likely only need a few very small changes from the default state, although you have not stated the purpose of this device (AP vs router), and that will affect some of the changes you may want to make.
You cannot set the Starlink router in bridge mode. OOB the system only provides wireless services to local wifi enabled devices. You have only app capabilities to set SSID and split the two wifi bands. Anything else is controlled exclusively by Spacex.
The Starlink bridge mode is enabled as @brada4 said by bypassing the Starlink router entirely. The only roll the Starlink router plays in bypass mode is to provide POE PD to the Starlink terminal.
Just add the Starlink or after market bypass adapter and set your Archer up to use OpenWrt default config.
What additional applications are you running on the router? If you're not going to start from defaults you still need to at least temporarily disable anything that might cause problems. Get plain old lan->wan routing working properly first.
