Recent content by CoyoteDen

The vlan 56-62 entries make no sense. They’re bridging LAN directly to WAN in like 3 places. factory reset time. Do not restore a backup.

Those VLANs looks very different than my AC66_B1. I didn’t think ports 7 and 8 were even connected in these models, but it seems to be using them for something. Does your ISP have IPTV requirements, and did you change the IPTV settings? If so, and you can’t get a WAN IP, you probably don’t have...

I have an AC66_B1 (AC68). The AC86 might be different. My GN2/GN3 acts just like the non-guest wifi. YazFi does isolate better, you can set rules for each guest network. But you have learned one very important thing about VPN: VPNs are not always considered LAN. TAP VPNs are layer 2, and sit...

Not reported to ASUS. Not even sure how, I was gonna let Merlin do that :) Ok, so... I want to keep switch port 4 from accessing my LAN. To do this I manually create a VLAN, put switch port 4 in it, and put it on the same bridge as GN1. YazFi doesn't use a bridge to isolate the GNs, it uses...

Not sure. I was using YazFi for a while, and it does the guest networks differently. I recently stopped using YazFi for other reasons, and that's when the GN1 bug bit me.

That I do not know. It’s possible the VLAN 501/502 is used to backhaul guest traffic over the mesh. If you use aimesh, you might want to modify the script to leave the VLANs on the bridge but take the WAN port off: robocfg vlan 501 ports “1t 2t 3t 4t 5t” robocfg vlan 502 ports “1t 2t 3t 4t 5t”...

Yep. It works for me.

I figured out the root cause and a fix for GN1 killing WAN: http://www.snbforums.com/threads/asuswrt-merlin-386-2_6-is-now-available.72962/post-696360 Yes, that's right. GN1 leaks DHCP from the guest network straight through to the WAN port!

Ok, I'm pretty sure I've figured out the problem with guest network 1 killing the WAN, and it's dumb. Really dumb. 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...

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.

GN2/3 aren't properly isolated from the LAN. I don't want my company-issued laptop on my LAN for privacy reasons. see here: http://www.snbforums.com/threads/rt-ac68p-fios-wan-dropouts-on-386-x.73214/post-696303 ASUS *could* put them on br1/br2 for isolation, but they didn't. Might be a bug...

Guest networks 2 and 3 have a pretty bad bug too. They can access your LAN no matter how you set the "Access Intranet" option. They aren't safe to use if you are trying to keep guests out of your LAN. This is the bridging configuration with 5G guest 1 and 2 on. Both are set to access intranet...

This is a weird one. When a device joins the guest network, WAN will drop out until you manually cycle the WAN connection. I thought it was coincidence too, but nope. Three days in a row now when I boot my work laptop, it connects to the guest network and my WAN drops. Syslog is not very...

It's the guest network! Turn it back on and have something join it. WAN will drop out until you manually cycle the WAN connection. I thought it was coincidence too, but nope. Three days in a row now when I turn on my work laptop, it connects to the guest network and my WAN drops. Syslog is not...

They're working fine after copying the firmware over and writing it locally. It's possible the web UI was timing out on uploading it, I have to update these via VPN or SSH tunnel (yes, I know...)