I have a small Fritzbox 7312 and I installed OpenWRT onto it. I would like to use this Fritzbox 7312 as wifi repeater, by means of bridging the LAN port to the WLAN port (yes, LAN->WLAN). My main router provinding internet is a Fritzbox 7330 with stock firmware, onto which I cannot install openWRT, because I'm using the DECT functionality for telephones. As far as I read, openwrt has no support for it.
This Fritzbox 7330 router isn't able to cover all the house with the wifi signal and some devices cannot connect to internet at all. So, what I'm trying to do is to wire both routers to the LAN ports (LAN2 on 7330 and LAN1 on 7312) and create a bridge from the LAN port to the WLAN interface on the Fritzbox 7312. I would like the devices on the repeater side to be on the same subnet as the main router. I have read several tutorials (e.g: https://openwrt.org/docs/guide-user/network/wifi/dumbaphttps://openwrt.org/docs/guide-user/network/wifi/bridgedap relay_configuration etc), but I guess all of them are bridging the interfaces the other way around (WLAN->LAN).
I don't know exactly what you mean by owing the network. But the local network is on 22.3.7.x and the main router is located at 22.214.171.124.
I also tried to not use the wlan on the bridge config, but it doesn't work either.
I can ping the 126.96.36.199 (main router) only when I'm connected to the main router's wifi network. If I'm connected to the secondary router's wifi network is out of reach.
nmap doesn't report the second router is active, nor does it the Fritzbox 7330's stock web interface. Also, both routers have actually no lights on the LAN ports, so I can't really tell if something actually happens and I have to trust nmap and this web interface. On the 7312, the DSL/Power light stays on and the WLAN light blinks. That's all I can tell
Don't refer to wifi in /etc/config/network. In other words your option ifname eth0 wlan0 should just be option ifname eth0. The wifi will get connected by its option network in /etc/config/wireless. You can confirm this with brctl show which should show ethernet and wifi in the br-lan bridge.
If you shut down dnsmasq entirely the DNS will stop working. It is better to leave it running but set option ignore on the lan network so it does not attempt to issue DHCP on the LAN. Also you have to turn off the IPv6 options separately.
If there are link lights on the ethernet ports but they're not lighting up there is a problem with the link. You can also get connection status and byte counts with ip link show or swconfig dev switch0 show if there is a switch involved.
To ensure proper wifi operation be sure to set your country code in the wifi-device block.
Thanks for your answer. Yes, I have removed wlan0 from bridge configuration. Now it tries to get ip address but it doesn't connect to the network.
Both routers have no physical lights attached to the LAN ports, as many ethernet ports do actually have. The only existing lights on both routers only show general information (power on/off, internet, WLAN, DECT, etc.), but no traffic.
Im going to check if with the dnsmasquerade works.
->wlan0 removed from bridge config
->changed wifi name
None of these seem to work. Main router won't detect the second. I was wondering if the lan cable should be crossed or not. I guess it shouldn't be necessary since I can connect to the internet when I connect the main router with my laptop using the same cable.
The weirdest thing is, it won't connect to the wifi network. No matter if the name is the same or different than that of the main router. Could it be that the Fritzbox 7330 is blocking the openwrt router somehow?
In a dumb AP configuration, a device connecting to the AP negotiates its IP from the main router via DHCP, so if there is no link to the main router the device will give up at the "Obtaining IP address" stage (this is what Android shows to the user).
Modern equipment all will automatically swap TX and RX so crossing cable is almost never needed. But I really suggest you plug the dumb AP into a device that has a link light and that light does not come on something is wrong.
The 22.x addresses may exist on the Internet, so there is a potential conflict. What this means in practical terms is that if for example the US Army has hosted a public web page with a 22.3.7.x IP, users of your network won't be able to reach it, they will contact something within your LAN instead.
There is absolutely no reason not to use the designated "private" IP's on the private side of your network.