Had to downgrade. Clean install and did 2 full resets and clean setups, but something is wrong with DHCP and manual IP’s being assigned incorrectly.
Are you assigning the DHCP hosts in LAN/DHCP?
That's quite odd. Are they showing manual or static?My DHCP pool is limited to 192.168.50.1 - 127. I then manually assign a few IP assesses over .127 to a few devices. I do this for a number of reasons, but mainly to use a secondary WAN using routing rules.
There’s a couple of devices that for some reason are being assigned IP’s over .127, even though they haven’t been manually assigned IP’s (the network map also shows a incorrectly states they are Manual). They are alway given the same IP to, so they are basically acting like they have had manual assignments when they haven’t, it’s really odd. Also some devices are actually being assigned random IP’s below .127, even though they have been manually give IP’s.
The stock Asus firmware often had all sorts of errors in the network map, but the IP’s were correctly assigned and worked as they should.
Wireless performance is also worse, with devices on the edge of my network dropping off when they never did with stock.
So far there’s too many bugs for me to use Merlin. UI is better, might try some older builds.
(AX88U BTW).
That's quite odd. Are they showing manual or static?
Manual - You set the IP via DHCP on the router
Static - The IP came from someplace other than the router
I've never seen anything outside the DHCP Range that was assigned by the router. Check the host to see the IP of the DHCP server. It sounds like you may have another one on your network.All devices that regularly connect to my network on the AC86 have been assigned IPs outside the small range I set aside for automatic IPs. DHCP pool is primarily for visitors. (15 static IPs ) I use other guest networks for IoT wifi connected devices and again all IoT devices have assigned IPs.
When I look at the network MAP is lists all IPs as DHCP even though they are IPs I have assigned outside the pool.
I noticed this behavior (no static IPs ) going back several versions of Merlin's firmware on my router. Since it really doesn't have any impact on my network I have just ignored it since all devices with assigned IPs are getting the correct IP.
It sounds like there is junk in the DHCP table (internal database) You could try turning DHCP off, then back on and assign all the hosts again. If that does not work, A reset to factory and then enter the configuration over. You are the only person I've seen report these symptomsManual, which is why it’s so strange because they are definitely not manual. I’ve gone over it’s all night, checked and triple checked, thought I was going mad. Clearly a bug.
Network map often shows some incorrectly as static, but that’s a separate issue and most doesn’t cause any problems.
You were 100% correct in both the diagnosis and the fix. Thanks!This can likely happen when the accounts get "out-of-sequence" in nvram. If you look at the underlying nvram variable over ssh login:
You will probably find that user and its password is listed before admin and its password. You probably also have errors applying any settings on the Administration / System page.Code:nvram get acc_list
If you understand the "<" and ">" delimited field in the nvram output, you could reorder them correctly:
The last reboot command can be done when convenient. Otherwise just refresh the samba page and see if it works properly.Code:nvram set acc_list="admin>theencryptedpassword<user>theencrypteduserpassword" nvram commit service reboot
My supposition is that this non standard DHCP behavior could have resulted from implementing YazFi which uses its own DHCP serving function to assign IPs from different DHCP pools for guest networks. Currently I have removed YazFi and am testing the VPN Director's functionality. (Works great!) All devices that connect to my AC86 are connecting to a guest WiFI SSID.I've never seen anything outside the DHCP Range that was assigned by the router. Check the host to see the IP of the DHCP server. It sounds like you may have another one on your network.
I am actually getting this error with no guest network enabled. In the last FW, I got it when I used the Guest 1 networks (2.4 / 5 GH), but now even with all Guest Networks off, I still get this error many times per second. Enabling / disabling the Guest Network(s) seems to have no effectIt will only happen when you have a client connected to that band and actively using it. If you have clients on both bands, then you should move both of them.
I had my IP6 settings all gunked up. After I fixed those, the error messages stopped.I am actually getting this error with no guest network enabled. In the last FW, I got it when I used the Guest 1 networks (2.4 / 5 GH), but now even with all Guest Networks off, I still get this error many times per second. Enabling / disabling the Guest Network(s) seems to have no effect
Jun 23 12:56:45 syslog: wlceventd_proc_event(527): wl1.1: Auth ******************, status: Successful (0), rssi:0
Jun 23 12:56:45 syslog: wlceventd_proc_event(556): wl1.1: Assoc ******************, status: Successful (0), rssi:0
Jun 23 12:56:50 dnsmasq-dhcp[14132]: DHCPDISCOVER(br2) *****************
Jun 23 12:56:50 dnsmasq-dhcp[14132]: DHCPOFFER(br2) 192.168.102.242 ******************
Jun 23 12:56:50 dnsmasq-dhcp[14132]: DHCPREQUEST(br2) 192.168.102.242 ****************
Jun 23 12:56:50 dnsmasq-dhcp[14132]: Ignoring domain **************** for DHCP host name ***************
Jun 23 12:56:50 dnsmasq-dhcp[14132]: DHCPACK(br2) 192.168.102.242 ***************
Jun 23 12:57:19 WAN_Connection: ISP's DHCP did not function properly.
Jun 23 12:57:20 DualWAN: skip single wan wan_led_control - WANRED off
Try using Guest Network 2 instead, to see if maybe it might be a routing conflict, as GN1 uses the 192.168.101.0 and 192.168.102.0 subnets.This is a weird one. When a device joins the guest network, WAN will drop out until you manually cycle the WAN connection.
This is just for testing purposes, to determine if there is a link.GN2/3 aren't properly isolated from the LAN. I don't want my company-issued laptop on my LAN for privacy reasons.
I’ll try that tomorrow (it doesn’t drop unless the GN has been unused for hours, like overnight) but I have a feeling it won’t trigger a WAN drop. Because of the bridging bug, GN2/3 are basically like YazFi GNs on br0.This is just for testing purposes, to determine if there is a link.
admin@RT-AC66U_B1-0:/tmp/home/root# robocfg show
Switch: enabled
...
VLANs: BCM5301x enabled mac_check mac_hash
1: vlan1: 1 2 3 4 5t
2: vlan2: 0 5
502: vlan502: 0t 1t 2t 3t 4t 5t
admin@RT-AC66U_B1-0:/tmp/home/root# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.38d547dbe940 no vlan1
eth1
eth2
tap22
br2 8000.38d547dbe945 yes wl1.1
eth0.502
eth1.502
eth2.502
robocfg vlan 501 ports ""
robocfg vlan 502 ports ""
brctl delif br1 eth0.501
brctl delif br1 eth1.501
brctl delif br1 eth2.501
brctl delif br2 eth0.502
brctl delif br2 eth1.502
brctl delif br2 eth2.502
Thank you, appreciated.It will only happen when you have a client connected to that band and actively using it. If you have clients on both bands, then you should move both of them.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!