Recent content by schmerg

The fact INTERNAL was working but not GUEST looks consistent with the fact that the brctl command to add interface 4 to bridge 0 hadn't been run. Now that "brctl addif br0 vlan4" only needs to be executed once as it seems to persist the setting across reboots. So now that it's been run, I'd...

When I asked, others recommended I get the AC86U instead (to replace my aging N66U) - mainstream support from Merlin, fast recent CPU, plenty of RAM, in practical day-to-day use about matches the 5300 etc, but about 2/3rds the price (here in the UK). I'm just waiting for the next special offer...

I wrote up my notes on doing this, VLAN tagging on an AP precisely for having an extended guest (and "Normal") wifi. I tried using a managed switch at first, but that didn't work out for me so now I do it entire within the router. See scripts and configs and explanations etc here Regards Tim

My thread about how I set up a tagged VLAN for a wireless access point (ie the AP broadcast 2 SSIDs, traffic from each SSID gets a different VLAN tag - one is a guest SSID, the other is "normal") may be of some use as to configuring dnsmasq etc (in the 1st few posts I tried doing the VLANs with...

Ah, precisely the sort of nugget of knowledge I was hoping for.. thanks. One day the ASUS naming convention will make sense to me... one day... Cheers Tim

Hey all, I've been very happy with my RT-N66U running Merlin's build, but now that it's dropped off the active support list and is (understandably) being left at v380, I suppose it's time to get a new router (and 802.11ac support, and maybe a stronger signal, and unicorns etc). I'm not so...

If your AP can tag the packets with a VLAN identifier, then I wrote up my process for doing this here. My extra access point supports multiple SSIDs (TPLink 801ND) and can tag each SSID with a different VLAN, so I have it broadcast my "home" wifi (it puts those on the wire with no VLAN tag)...

Ah sorry, I'll pull my head in :) Cheers Tim

VLANs can be configured from the command line, if you know what to do, and of course Merlin's builds with support for /jffs/scripts makes it much easier to have scripts than run as required. In this thread I explain (by the 3rd message) how I configured my RT-N66U to understand clients tagged...

I moved this list out of nvram by putting the static list into a jffs maintained config file admin@RT-N66U-25A0:/jffs/configs# cat dnsmasq.conf.add # Appended to dnsmasq.conf automatically, or if done by hand, restart the service with # $ service restart_dnsmasq # # generated from GUI settings...

My guess is you're seeing connectivity is fine, but name resolution isn't up to date. If you reboot the router, devices which already received DHCP leases (and then will be in the local DNS as resolvable names) will still keep the same IP address, and won't re-register until the lease expires...

Wow.. that looks pretty... comprehensive. Might take a while for to digest all that, but it definitely looks useful.. thank you for posting it -- Tim

So after 75 minutes it was showing the same problem? Sounds like a problem with wifi on that device.. you could try tweaking the various settings on the router under "Professional" (or hmmm... "Network Key Rotation Interval" defaults to 3600 seconds.. try setting that to 0 and see what happens...

Which should work tho... what happens if the client joins the normal wifi (ie forgetting all the VLAN stuff)? Does it re-request at 20 minutes? Does the request get granted? What encryption/other options have you got turned on for the two SSIDs ?

You should be able to do so... I think the script excludes a line about adding the interface to the bridge brctl addif br0 vlan4 as this only has to be done once and then persists across reboots.. but my memory here is a little hazy. The clause at the top of the script checks if the VLAN...