What's new

RT-AC3100 to RT-BE88U DHCP Config file format

RiskyBusiness

Occasional Visitor
Finally time to upgrade the router again here since the RT-AC3100 is not longer supported. Still works great btw with excellent Wi-Fi coverage. Decided to go with the RT-BE88U for the CPU and the 2.5 Gb ports.

On the AC3100 I ran YazDHCP and YazFi to provide DHCP assigned IP addresses to the main LAN and 2 additional wireless networks (SSID) separated from the main. Before YazDHCP and YazFi were developed I recall setting up the networks via a script file, and later a config file to assign the IP addresses. It was easy to backup, maintain and restore the network quickly if/when a reset was ever required. I've been reading through the forums here, and see that the format of these files have changed with the 3006 Firmware, and of course the addition of the SDN/VLAN support. I currently have the BE-88U configured with my main LAN (wired plus separate SSID's for the 2.4/5 Wi-Fi), IoT (2.4 using same subnet) and 2 addional guest vlan's. I previously used dnsmasq.conf.add to handle the IP assignments for the main network, but I'm a little confused about the additional networks on the BE-88U. I've read the discussions about dnsmasq-X.conf.add (using X=1/2 for VLAN 52/53). When I ssh to /tmp/etc I see that the VLANS are configured using 5 and 6 (dnsmasq-5/6.conf). Is this something different than what everyone else is experiencing or is it specific to the BE88U. Also, when looking a the /var/lib/misc/dnsmasq-5/6.lease files created, the format looks a little different. The line looks like [ ##### (pid-?)] [mac] [IP] [Hostname] [ and on some lines what appears to be another/different mac ]. Does this change what has to go into the config file on this router? Previous format was as simple as [MAC,IP,HOSTNAME]. Just trying to wrap my head around this before I start plugging in cofig files.

tia
 
If you haven't done so already, see YazDHCP. It has been updated to work with assigning manual IP reservations to Guest Network Pro clients. So one no longer needs to use external files like /jffs/configs/dnsmasq*.conf.add to set manual IP reservations. Any questions about YazDHCP should be asked in it's discussion topic in the Addons subforum.

PS: The YazDHCP links above have examples of how to manually transfer the IP address assignments directly into the YazDHCP internal CSV-formatted client list.
 
Last edited:
If you haven't done so already, see YazDHCP. It has been updated to work with assigning manual IP reservations to Guest Network Pro clients. So one no longer needs to use external files like /jffs/configs/dnsmasq*.conf.add to set manual IP reservations. Any questions about YazDHCP should be asked in it's discussion topic in the Addons subforum.

PS: The YazDHCP links above have examples of how to manually transfer the IP address assignments directly into the YazDHCP internal CSV-formatted client list.
That must be a new update. The last I looked, it would handle the main network fine, but wouldn't work with the new GNP SDN's
 
That must be a new update. The last I looked, it would handle the main network fine, but wouldn't work with the new GNP SDN's
Not really new, Guest Network manual IP reservation support was added October of last year with release v1.2.0.
 
Not really new, Guest Network manual IP reservation support was added October of last year with release v1.2.0.
Appreciate it. I'm reading through that in the forum now. Will probably give it a go this afternoon once the grand daughter finishes school
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top