@rydah805
Not sure if it's related, but for the very first time today with dd-wrt (used since 2008) I experienced something I never saw before: currently playing with various settings on wireless guest I'm often disconnected which is normal because the wl devices are restarted. Only playing, I only use telnet, and what I saw at a moment is that I didn't get the dd-wrt prompt. I got the banner, but not the prompt for user name. Typed Enter and got the prompt. Exit/telnet, banner but no prompt. Ctrl+C, telnet, no prompt. Enter, prompt OK, login OK, exit, and exit again to close the pc terminal, relaunch, telnet, prompt OK.
On the pc I have for years a customed black background & colored prompt (from .bashrc), and I noticed since some release the dd-wrt prompt is coloured.
On pc:
me@lap:~$ echo $PS1
I also have a setting somewhere that tells terminal no to wipe screen from previous session when I disconnect telnet/ssh (maybe in terminal settings or ssh client) _________________ ): FoReVeR nEwB
After a couple of days uptime, today the "guest" Wifi on 2.4GHz was not accepting connections.
Primary Wifi was still okay, but the "guest" Wifi is essential here as well.
Rebooted, works again.
EDIT: I suspect be this might have been due to dnsmasq crashing and not being restarted.
There are more than a few reports here of dnsmasq causing trouble, and of routers behaving better with it disabled. On my R6400, I have dnsmasq disabled for everything except the "guest" Wifi, which would explain why only the "guest" wifi had issues today.
Next time it happens, I'll check to see if dnsmasq is still running or not before rebooting.
I found something : just add a #dummy line in the firewall script and Save Firewall : then you can connect to guest without rebooting the router. Maybe just Save Firewall with no change would do the job. I believe that for devs, it is a big tradeoff headache to balance when reload/not reload the rules. _________________ ): FoReVeR nEwB
Posted: Fri Oct 21, 2016 20:51 Post subject: Guest vaps 2G & 5G in the same subnet with desipro tuto
Now, my question
I followed the Kong's tuto @ desipro and want to use it to make the guests network bi-band.
As I'd like to have guests in the same say 192.168.2.0/24 net, I get puzzled and stuck at Networking.asp dhcp settings because I wonder if there are 2 dnsmasq-dhcp instances that could allocate twice the same IP? If there is a single instance, will it be clever enough to not fall into the trap ? I see all options in dnsmasq.conf duplicated for wl1.1, as well as the firewall rules.
My setup works for a single vap, but not when I set the 2 vaps at 2.1 (same exact duplicated lines below, even the 2 last ip rules). Only setting the 5G vap @ 3.1 I get it work, but the 2 vaps aren't in te same net.
Maybe this is not the more elegant way to do. Coming from old single band r14896 where I did the job by keeping the vap bridged, then manually create its own bridge and tweak dns options and firewall rules, I just discovered the huge wonderful job that was done in this guest vap matter (thanks to the kong's tuto and this new wiki one).
Wouldn't a lighter way for me be to bridge the 2 vaps (single net & dhcp-dns conf, single set of ip rules), like are the 2 AP on the private lan side?
Or maybe it's a bad idea to put vaps for guests ?
Create a new bridge br1 and give it the ip address 192.168.2.1
Assign wl0.1 and wl1.1 to br1
Assign a dhcp server for 192.168.2.0 to br1
Thanks man
I just did it, but although dnsmasq.conf is now nicer slim, I still get the ip rules set for wl0.x plus br1
Did I say in the previous post I was afraid to loose rules when using bridging then having again to loose more hair to recreate good ones ?
This build for R7k asks for a MAC for br1
I already have 84:52 for br0 (LAN), 84:53 for WAN and 84:54 & 84:55 for WLAN.
Do I have to use any of these 3 for br1 or do I have to invent 84:5f, 84:50, 84:00 or 84:ff or anything different I want?
[EDIT]
I got it clean by unbridging the vaps, resetting to no things like net isolation and force-dns-redirection, saving, rebridging.
Now I just have a clean bunch of br1 rules
Just have to check they are ok.
PS: I put 84:52 for br1 (same as br0). brctl show displays for both the same id.
Thanks _________________ ): FoReVeR nEwB
Last edited by Bib on Mon Oct 24, 2016 10:21; edited 1 time in total
Create a new bridge br1 and give it the ip address 192.168.2.1
Assign wl0.1 and wl1.1 to br1
Assign a dhcp server for 192.168.2.0 to br1
Thanks man
I just did it, but although dnsmasq.conf is now nicer slim, I still get the ip rules set for wl0.x plus br1
Did I say in the previous post I was afraid to loose rules when using bridging then having again to loose more hair to recreate good ones ?
This build for R7k asks for a MAC for br1
I already have 84:52 for br0 (LAN), 84:53 for WAN and 84:55 for WLAN.
Do I have to use any of these 3 for br1 or do I have to invent 84:54, 84:5f, 84:50, 84:00 or 84:ff or what I want?
[EDIT]
I got it clean by unbridging the vaps, resetting to no things like net isolation and force-dns-redirection, saving, rebridging.
Now I just have a clean bunch of br1 rules
Just have to check they are ok.
PS: I put 84:52 for br1 (same as br0). brctl show displays for both the same id.
Thanks
Can you tell me the value of br1_bridged in your nvram (nvram get br1_bridged)? _________________ R7000 Nighthawk - DD-WRT v3.0-r50308
R7000 Nighthawk - DD-WRT v3.0-r50308
~~~~~~~~~~Dismantled for learning opportunities~~~~~~~~~~
WRT54Gv2
WRT54Gv8.2
~~~~~~~~~~Other Settings~~~~~~~~~
https://nextdns.io/?from=2d3sq39x https://pi-hole.net/ https://github.com/DNSCrypt/dnscrypt-proxy
This bridged setup won't do Net Isolation.
I continue on the "Advanced Networking" section of the forum, because this may not be broadcom nor kong's 30700 specific issue. _________________ ): FoReVeR nEwB
Posted: Sun Oct 23, 2016 12:58 Post subject: Asus AC68U Crashes after 12 hours 47 minutes
Reporting my findings. I have two Asus AC68U
Asus 1 is HW Rev A2
Running all things needed on my network:
WAN, DHCP, DNS, QoS, VLANs, DDNS, multiple SSID
Code:
root@hamster-net-1:~# nvram get clkfreq
800,666
root@hamster-net-1:~# cat /proc/cpuinfo
model name : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1594.16
Features : half fastmult edsp tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
model name : ARMv7 Processor rev 0 (v7l)
processor : 1
BogoMIPS : 1594.16
Features : half fastmult edsp tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
Asus 2 is HW Rev C1
Simply for extending my network elsewhere in the house:
VLANs, multiple SSID
Code:
root@hamster-net-2:~# nvram get clkfreq
1000,666
root@hamster-net-2:~# cat /proc/cpuinfo
model name : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1987.37
Features : half fastmult edsp tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
model name : ARMv7 Processor rev 0 (v7l)
processor : 1
BogoMIPS : 1993.93
Features : half fastmult edsp tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
Asus 1 crashed at 2:15 AM EDT after having been up for 12 hours and 47 minutes. Load was stable. The only thing that changed significantly before the crash was memory which started to take a dive for 55 minutes prior to the crash.
Asus 2 remains stable. Not sure if this is due to the hardware differences
I am going to have a read of the thread to see what others have found.
Did you erase nvram?
This is highly recommended especially when switching between builds
I did yes, using the CLI. BUT I then restored a backup, which might be counter-intuitive. Not sure what the backup contains and if this is a supported method.
Joined: 18 Mar 2014 Posts: 12885 Location: Netherlands
Posted: Sun Oct 23, 2016 13:35 Post subject:
jjwatmyself wrote:
egc wrote:
Did you erase nvram?
This is highly recommended especially when switching between builds
I did yes, using the CLI. BUT I then restored a backup, which might be counter-intuitive. Not sure what the backup contains and if this is a supported method.
I have now enabled syslog on both pointing at a Synology NAS. If it happens again (which I am expecting it will) I may have more info to report back with.
Last edited by jjwatmyself on Sun Oct 23, 2016 13:57; edited 1 time in total
have now enabled syslog on both pointing at a Synology NAS. If it happens again (which I am expecting it will) I may have more info to report back with.
Oh boy, that's quite a bit of work. I don't disagree though. Maybe what I'll do is erase the other one, do a side-by-side compare in order to manually move all the config over. The config on the other is a subset of functionality, pretty much VLANs and SSIDs. There is the added benefit that the primary will then be the newer HW rev with higher CPU clock speed.
?
