Router Model: Linksys E900
Status: Basic setup working. WPA2 access point. DHCP server.
Errors: So far no obvious problems. Did encounter a not so obvious WiFi issue. Communication via WiFi stops working occasionally, but the connection doesn't drop completely. The WiFi client (MacBook) stays connected to the access point and has 192.168.1.109 assigned as ip address (according to network preferences in MacOS). But the MacBook can't ping anything. Not even the router ip address at 192.168.1.1. This problem lasts for some minutes, or I can fix it by manually clicking the "Renew DHCP lease" button on my MacBook. Then I can ping the router again and also connect to the internet. After pressing the button the ip address remains 192.168.1.109.
Happend about 5 times (that I noticed) in two days. Didn't happen on stock firmware.
Router Model:Linksys WRT610N V2
Kernel:Linux 3.10.108-d4 #20244 Sat Jul 28 12:45:04 CEST 2018 mips
**Status:Gateway 2 local ap's
wl0 and wl1 using same SSID'S**
1 DHCP Server
*Netgear crap router with no krack patch for iot devices/plugged lan to wan
Alternate DHCP and SSID
*1 WRT300N V1.1 Repeater
Alternate DHCP Server
Broadcasting same main SSID
*Overclocked to 533 MHz* (Very reliable)
*DNSSEC VIA CLOUDFLARE IPV6+IPV4 SERVERS*
Status: working, repeater like an WISP
Errors: In some times, after the modification of some parameter, the wirelles does not work, i can connect though lan and see a thing different: Current Time Not available
and the date command shows a date:
Wed Dec 31 22:00:38 BRST 1969
I cant set the date throug comand line, and it needs restore router settings to default to work again
Joined: 08 May 2018 Posts: 6915 Location: Texas, USA
Posted: Wed Nov 07, 2018 4:29 Post subject:
@quarkysg, jwh7, slice1900:
The wlconf binary is built from source in DD-WRT, it is not a blob. I am not entirely sure if the actualy wl driver component is being compiled from the latest source code in DD-WRT or not, it does NOT appear as such. The ticket is referring to the wlconf binary, and after re-seeing your posts in this thread, seems my comment on the ticket may be completely wrong, but the VIF/VAP issue is a mess - and I am not entirely sure if it's the wlconf binary or DD-WRT's init or a combination of both.