derekperrin / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

N56U: ntpd can't resolve domain names when AP Mode = AP Client Only #1449

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Asus N56U
Firmware 3.4.3.9-091
Syslog: http://mdmower.cmphys.com/stikked/view/456f55e3

When the wireless 2.4GHz network is set to 'AP Client Only' mode, ntpd appears 
unable to resolve domain names. I have the router set to "Access Point Mode 
(AP)" and wireless 5GHz is disabled.

What steps will reproduce the problem?
1. Remove WAN ethernet cable
2. Connect n56u to another wireless network using 'AP Client Only' mode
3. Set n56u to 'Access Point Mode (AP)'
4. Verify ethernet clients on n56u have internet access
5. ssh/telnet into the router
6. Type: ntpd -q -p 0.us.pool.ntp.org
Output: ntpd: bad address '0.us.pool.ntp.org'

I setup an ntp server on a client in the same subnet and verified that ntpd 
successfully synchronizes time with that server. Example: ntpd -q -p 
192.168.0.50

Original issue reported on code.google.com by mow...@gmail.com on 17 Mar 2015 at 9:10

GoogleCodeExporter commented 8 years ago
Maybe user error?

After upgrading from 091-base to 095-base, the issue described above persisted. 
So I took a closer look at settings and notice that the gateway I had set for 
LAN was in the wrong subnet. I honestly don't understand how my devices were 
working fine with the wrong gateway set, but indeed, setting the correct 
gateway also allowed ntpd to start working:

# ntpd -w -p us.pool.ntp.org
ntpd: reply from 208.75.89.4: offset:-0.025932 delay:0.076130 status:0x24 
strat:2 refid:0xcac0dad8 rootdelay:0.017487 reach:0x01
ntpd: reply from 208.75.89.4: offset:-0.025401 delay:0.078273 status:0x24 
strat:2 refid:0xcac0dad8 rootdelay:0.017487 reach:0x03
ntpd: reply from 208.75.89.4: offset:-0.026406 delay:0.078555 status:0x24 
strat:2 refid:0xcac0dad8 rootdelay:0.017487 reach:0x07

I believe this issue can be closed.

Original comment by mow...@gmail.com on 2 Jun 2015 at 12:47