Meteobridge is authoritative DHCP server. **solved**

[pehon]

Hello!
I got some network issue with a fresh installation of meteobridge-rpi3-v1.3
meteobridge does answer dhcp requests on the network and after a couple of minutes some devices in my network become unusable (including my laptop). You can force that if you stop your home router beeing a dhcp server.

after checking the installed image (/var/etc/dnsmasq.conf.cfg01411c):
dnsmasq ins configured with "dhcp-authoritative", most options are not necessary and there is no "no-dhcp-interface=eth0" or similar. Thats from my point of view wrong (there is also a overlapping dhcp range... a bit strange..)

Steps to reproduce:
- meteobridge-rpi3-v1.3 flash (in my case a raspberry pi 3 with a standard sdhc card (no SLC, still waiting))
- set static ip address (IP, Mask, DNS, Gateway)
- save apply and reboot
- wait a couple of minutes and you will see answered dhcp requests in /var/dhcp.leases. At this time you have two dhcp server and the first wins.

Why is metebrige acting as as DHCP Server in my network?

How do i alter /var/etc/dnsmasq.conf.cfg01411c without loosing my changes after reboot?

Furthermore, I'm not able to login at luci (tried root/meteobridge or meteobridge/meteobridge) "Invalid username and/or password! Please try again."

Thanks,
Peter

[galfert]

The Meteobridge has the capability to form a separate LAN subnet if you enable it to make a LAN bridge. For this it feature it needs to be DHCP server in that instance for that subnet I believe. If you have incorrectly configured your Meteobridge then it will cause problems. In a normal and proper configuration there should be no issue.

The Meteobridge in some versions also needs the DHCP server function for initial pairing using its MiFi function. Once paired though this should no longer be an issue.

The not being able to log into Luci has been touched on before. I had the same thing happen but it was resolved. Others have noted it too. Did you try a blank password? I forget or didn't notice what occurred to clear this situation after attempting a few things.

[Andyk1]

After the first boot find the Rpi3 IP address on your main router.
set the new MB to Set the IP manually.
Choose an IP address not being used by a device.
Set subnet to same as your original router.
Set the gateway to the router it is on.
DNS the same as the router.
The Rpi 3 can use both 2.4 and 5G wireless networks.
The Rpi 4 only 2.4 for now.
All this of course is while plugged into an ethernet cable.
REBOOT.

[AlaskaWX]

Why is metebrige acting as as DHCP Server in my network?

See this post on how to disable the DNS and DHCP server on Meteobridge RPI that survives reboots:

viewtopic.php?p=37579#p37579

Worked for me.

[AlaskaWX]

...
Furthermore, I'm not able to login at luci (tried root/meteobridge or meteobridge/meteobridge) "Invalid username and/or password! Please try again."
...

The key is to login to the Meteobridge web interface initially with the root account using the root password. After you do that you'll automatically be logged into the openwrt luci interface when selecting "Expert Mode" on the Meteobridge Network page.

If you initially login to the Meteobridge web interface with the meteobridge account you'll never be able to run openwrt luci pages.

If you have a cached login using the meteobridge account, you'll have to clear the browser data/cache to be able to login with the root account.

[pehon]

Gorgeous, thanks for all those quick answers!

I got rid of dnsmasq (stop/disable) and luci is no ok as well!

For future releases of meteobrige I would disabled dnsmasq, I’m sure that will confuse some users.

[jpouyaud]

Gorgeous, thanks for all those quick answers!

I got rid of dnsmasq (stop/disable) and luci is no ok as well!

For future releases of meteobrige I would disabled dnsmasq, I’m sure that will confuse some users.

fully agree

I've spent 4h with a PI3 not able to boot on a static IP...