Merlin, will there be another beta build or is this the final version?
Will depend on whether any FW-specific issues get reported and require fixing or not.
Merlin, will there be another beta build or is this the final version?
dhcp logging in the system log seems to
be broken, I even removed static IP addresses
and I still don't see them in the log.
Oddly, after I initially flashed it was
working properly. However after I read about
wiping your settings I did this and that's
when the dhcp requests in the log stopped
I've checked all my settings and they should
work
I suspect there's an issue with the RT-N66U and the Centrino 6230 with the new driver. While it works fine with my RT-AC66U, my laptop is totally unable to connect to the RT-N66U on the 5 GHz band with the Centrino 6230. I'll contact Asus about it, see if they can reproduce the issue on their end.
UPDATE: the issue seems to only occur while the 5 GHz band is set to 40 MHz width. That might mean it's not specific to the Centrino 6230, but to 40 MHz width in general.
Anyone could test this for me on an RT-N66U? Have the 5 GHz band set to 40 MHz, and let me know if you are able to connect, and at what rate. Also specify which network card you have, so I can tell if it's a single, dual or triple stream card.
I suspect there's an issue with the RT-N66U and the Centrino 6230 with the new driver. While it works fine with my RT-AC66U, my laptop is totally unable to connect to the RT-N66U on the 5 GHz band with the Centrino 6230. I'll contact Asus about it, see if they can reproduce the issue on their end.
UPDATE: the issue seems to only occur while the 5 GHz band is set to 40 MHz width. That might mean it's not specific to the Centrino 6230, but to 40 MHz width in general.
Anyone could test this for me on an RT-N66U? Have the 5 GHz band set to 40 MHz, and let me know if you are able to connect, and at what rate. Also specify which network card you have, so I can tell if it's a single, dual or triple stream card.
Yeah I can tell you on my N66U it's not logging either. Hell nothing has been recorded in the log for over a day, and I can tell you using previous firmware version's. It's almost like spam to me seeing DHCP stuff being logged. I have multiple thing's with assigned IP's, and yes the option is set to "Yes", which if I am correct is "Yes" by default anyway's.LAN -> DHCP Server page - what do you have "Log DHCP queries" set to?
Logging is working normally here.
I had 2 discomects in 48 hours on 5 ghz band and could not see the band until I rebooted router then 5 ghz band was visible again . All 5 ghz ssid were missing from inssider and windows
intel 5300 on chan 153 40mhz
I'm running my laptop with a Intel T8100 processor and Intel Wifi Link 4965. 5ghz is working fine for me with 40mhz
Yeah I can tell you on my N66U it's not logging either. Hell nothing has been recorded in the log for over a day, and I can tell you using previous firmware version's. It's almost like spam to me seeing DHCP stuff being logged. I have multiple thing's with assigned IP's, and yes the option is set to "Yes", which if I am correct is "Yes" by default anyway's.
Apr 1 02:50:27 login[1828]: root login on 'pts/0' admin@Stargate:/tmp/home/root#
Wireless mode -N only
Channel bandwith - 40mhz
Control channel - 36
Extension channel - Auto
Hi,I'll try to see if I can reproduce the DHCP logging issues here, but so far my log gets a healthy dose of DHCP log entries from my various devices.
Mar 31 22:38:17 login[5723]: root login on 'pts/0'
Apr 1 10:34:43 rc_service: httpd 509:notify_rc restart_dnsmasq
Apr 1 10:34:43 dnsmasq[507]: exiting on receipt of SIGTERM
Apr 1 10:34:43 dnsmasq[7876]: started, version 2.65 cachesize 1500
Apr 1 10:34:43 dnsmasq[7876]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
Apr 1 10:34:43 dnsmasq[7876]: asynchronous logging enabled, queue limit is 5 messages
Apr 1 10:34:43 dnsmasq-dhcp[7876]: DHCP, IP range 192.168.0.2 -- 192.168.0.251, lease time 1d
Apr 1 10:34:43 dnsmasq[7876]: read /etc/hosts - 36 addresses
Apr 1 10:34:43 dnsmasq[7876]: read /etc/hosts.dnsmasq - 26 addresses
Apr 1 10:34:43 dnsmasq-dhcp[7876]: read /etc/ethers - 26 addresses
Apr 1 10:36:05 dnsmasq-dhcp[7876]: DHCPREQUEST(br0) 192.168.0.10 [MAC-Address]
Apr 1 10:36:05 dnsmasq-dhcp[7876]: DHCPACK(br0) 192.168.0.10 [MAC-Address] josi-pc
Apr 1 10:36:08 dnsmasq-dhcp[7876]: DHCPINFORM(br0) 192.168.0.10 [MAC-Address]
Apr 1 10:36:08 dnsmasq-dhcp[7876]: DHCPACK(br0) 192.168.0.10 [MAC-Address] Josi-PC
Makes me wonder if the issue wouldn't be with syslog itself them, and not DHCP events. Log to your router over SSH, then see if there's a new entry in syslog looking like this:
Code:Apr 1 02:50:27 login[1828]: root login on 'pts/0' admin@Stargate:/tmp/home/root#
Apr 1 11:37:23 dropbear[10737]: Child connection from 192.168.2.172:50904
Apr 1 11:37:36 dropbear[10737]: Password auth succeeded for 'admin' from 192.168.2.172:50904
Apr 1 08:51:39 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 09:04:10 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 09:19:49 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 09:21:04 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 09:31:39 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 09:58:48 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 10:00:42 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 10:04:54 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 10:05:03 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 10:13:10 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Apr 1 10:17:09 dnsmasq-dhcp[5798]: not giving name RT-N66U to the DHCP lease of 192.168.2.160 because the name exists in /etc/hosts with address 192.168.2.1
Hi,
Yes, this due to wrong DST (daylight saving time) implementaion in the firmware.
Go for manual daylight saving time!
These settings switched today like a charm to DST...Code:Manual daylight saving time settings for 2013 (in Europe): DST start time: M3 month / 5 week / 0 weekday / 2 hour DST end time: M10 / 4 week / 0 weekday / 2 hour
With kind regards
Joe
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!