I have a Flint 2 set up as my primary router. I'd like to add a second Flint 2 to create a separate network for my Tesla, located near the garage.
Stupidly I thought it would be as simple as plugging the second routers WAN into the primary router's LAN.
They are on separate subnets
The second router never gets an ip address from the first via DHCP.
What am I missing?
Thanks!
So when you plug the 2nd router into the first one. It's WAN address should get a 192.168.1.x IP address from the Primary Router. What does it show in Internet - Ethernet 1 of the 2nd router ?
It doesn't get an address. It just spins on "Connecting".
The primary router never see the secondary router.
Your implying it should be this simple, yeah?
Try 2nd router as access point mode and you can different SSID and password or same SSID as primary router.
Just trying to help…
Have you used a different cable ? If so have you tried to reset the 2nd router and start again ?
Other ideas… are they both using latest firmwares ? Anything out of ordinary in system / kernel logs of the routers pointing to errors or crashes ?
It sounds like you're trying to add a second Flint 2 router to create a separate network for your Tesla, but you're running into trouble with the DHCP not assigning an IP.
Here’s the issue: When you connect the WAN port of Router 2 to the LAN port of Router 1, they are on different subnets (192.168.1.x vs. 192.168.8.x), so Router 1’s DHCP won’t assign an IP to Router 2.
Use Router 2 as an Access Point:
Keep the networks separate:
Both options should solve your problem depending on whether you want one unified network or two separate ones. Let me know if you need more details!
Not need to turn off DHCP in 2nd router, just change network mode
That works often on non openwrt routers, however for openwrt you need to use wan port for the second router.
But when you do there will be another issue, you will have two firewalls and two dhcp servers, depending of your use case and reachability you may choose to let it be as is.
But if you really need to extend lan and reach devices, then you want to search for dumbap type of setup, from what i know this cannot be easily done from the gl ui, i wish they will add support for it in a form of 'bridge' mode, you need to navigate to the advanced settings in luci.
this means you want to add wan eth1 into br-lan, remove wan interface, turn protocol of lan from static to dhcp client or unmanaged, and remove all firewall zones, you could reserve one port with its own network for maintenance.
to add devices or removing ports from bridge br-lan you navigate to:
Luci -> network -> interfaces -> devices (tab) click on edit, you can add eth1, and uncheck lan5 or lan4 (the last port), click save but not save and apply.
If you click back on tab interfaces next where devices are, you delete wan.
Then edit lan and change protocol to dhcp, on the firewall tab you select none.
again don't apply yet only save, you want a safety maintenance network.
now create a new network interface, call it maintenance and choose lan4 or lan5 the one you previously deleted from br-lan.
Select static protocol, under address you can type:
192.168.32.1
subnet: 255.255.255.0
gateway: leave empty
Navigate to firewall tab create a new zone maintenance.
On dhcp you click on create.
Now navigatie to luci -> network -> firewall and navigate to the maintenance zone, change input to accept.
Now ensure you are connected to maintenance port and click save and apply.
Note that alot of logic will break within the gl ui, but yea... this is a very legitimate setup not advanced perse but in the time present the ui was not made with these intentions back then, hopefully in the future it will be a function on its own 
What happens if you change the 2nd router to 192.168.3.1 for example?
Thanks for the help @sharmaineleonia
Your second solution seemed like the most straightforward for what I'm looking for.
After giving it a shot, this is what's happening on the WAN port.
It goes from
I just don't understand how something this seemingly simple is making me pull my hair out. 
Today I decided to update the 2nd router to 4.7 and try AP Mode.
SAME problem. Router 2 never gets an IP from router 1.
I can connect to Router 2's wifi network but it has no gateway and doesn't hand out an IP address.
At this point I'm happy to get this working as a regular AP on the network and then I will use the new AP Isolation whitelist feature to only allow the Tesla to have access.
Any ideas?
@slesar It seems like maybe you have this setup working based on your prior responses?
Never connect LAN -> LAN, always connect LAN -> WAN
Thanks for the reply @admon.
Per the conversation above, I've tried
primary router LAN -> secondary router WAN in router mode and AP mode.
I even bought a 3rd Flint 2 just to be sure I didn't have a dud.
It seems the primary router will not hand an address to the secondary router no matter what I do.
Is it possible it's because I have the 4.6.6-op24 firmware on the primary router?
Can it be downgraded to 4.7 inline, or do I have to factory reset to go to the op21 line?
Thanks again for the help!
Make sure that your Flints are using different networks as well. You can't connect Flints out of the box to each other because they all uses 192.168.8.1
Change every router to it's own network line 192.168.21.1, 192.168.81.1 and so on
What I am thinking that you used ip6?
Second question how so far cable length? Over 100m?
First router I changed LAN IP address - 192.168.20.1/255 . Because there will be conflict default router first time.
Second router plugged to pc (LAN to LAN) and change network mode to access point mode . Unplug cables.
Finally first router 2nd LAN to second router WAN.
Next first router find clients IP address for 2nd router and copy address to open web page 2nd router. (You could make static IP address like 2nd router is 192.168.20.3 in DHCP 1st router).
Then 2nd router I could add WiFi with same SSID from primary router. You could change SSID for Tesla.
So that my 2nd router Flint2 working and bigger coverage WiFi in my house and garden.
