[ottawa_craig1]

I have configured a remote router over wifi (ddwrt Firmware: DD-WRT v3.0-r47925 std (12/28/21)) the attached windows clients work fine.
The remote router itself (an r7450) can't resolve hostnames, and as such can't set it's time with ntpd.

root@cottage_client:~# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
192.168.0.0 * 255.255.255.0 U 0 0 0 br0
root@cottage_client:~# ip show route
root@cottage_client:~# ip route show
127.0.0.0/8 dev lo scope link
192.168.0.0/24 dev br0 scope link src 192.168.0.253
root@cottage_client:~# ip route show table 0
default via 192.168.0.1 dev wlan0 table 16800 src 192.168.0.253
192.168.0.1 dev wlan0 table 16800 scope link src 192.168.0.253
192.168.0.2 dev wlan0 table 16800 scope link src 192.168.0.253
192.168.0.4 dev br0 table 16800 scope link src 192.168.0.253
192.168.0.5 dev br0 table 16800 scope link src 192.168.0.253
192.168.0.252 dev wlan0 table 16800 scope link src 192.168.0.253
192.168.0.4 dev br0 table 16801 scope link
192.168.0.5 dev br0 table 16801 scope link
default via 192.168.0.1 dev wlan0 table 16802
192.168.0.1 dev wlan0 table 16802 scope link
192.168.0.2 dev wlan0 table 16802 scope link
192.168.0.252 dev wlan0 table 16802 scope link
127.0.0.0/8 dev lo scope link
192.168.0.0/24 dev br0 scope link src 192.168.0.253
broadcast 127.0.0.0 dev lo table local scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local scope host src 127.0.0.1
local 127.0.0.1 dev lo table local scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local scope link src 127.0.0.1
broadcast 192.168.0.0 dev br0 table local scope link src 192.168.0.253
local 192.168.0.253 dev br0 table local scope host src 192.168.0.253


connection type disabled
local ip address 192.168.0.253
gateway 192.168.0.1 # this is the up of the main wifi AP.
NTP enable
timezone Canada/eastern
time.google.com
------------------------
wireless mode client Bridge (Routed)
Default GW 192.168.0.1
Network mode NG - mixed
---------------------------
wireless security wpa2 and ccmp-128 for all 3 interfaces
-------------------------
services DNSMASQ enabled
no DNS rebind enbled
no additional dnsmasq options
Security tab SPI firewall disabled
-----------------------------------
virtual Interface wlan0.1 AP with ssid enabled
wlan1 AP ac/N-mixed with ssid broadcast enabled
------------------
syslog follows with time out of date.
Jan 1 00:02:33 cottage_client daemon.err process_monitor[1985]: cyclic NTP Update failed (servers time.google.com)
Jan 1 00:03:08 cottage_client daemon.err ntpclient[6038]: Failed resolving address to hostname time.google.com: Try again
Jan 1 00:03:08 cottage_client daemon.err ntpclient[6038]: Failed resolving server time.google.com: Network is down
Jan 1 00:03:08 cottage_client daemon.err process_monitor[1985]: cyclic NTP Update failed (servers time.google.com)
----------------------------


NOTE! if I add time.google.com to etc hosts, it works!
root@cottage_client:/etc# cat /etc/hosts
127.0.0.1 localhost
192.168.0.253 cottage_client
216.239.35.4 time.google.com

[egc]

Try setting the Local DNS to the primary router

In the Time settings leave the "Server IP/Name" empty

[kernel-panic69]

The upstream gateway address has to be set in two places: Setup -> Basic Setup and on the wireless bridge interface itself, if it's like Atheros. Did I miss something in the last wiki edit when I split Broadcom back to it's own Client Bridge tutorial?

[ottawa_craig1]

yes.
I have 192.168.0.1 set in both, but I still can't resolve names from the root login on the router.
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
192.168.0.0 * 255.255.255.0 U 0 0 0 br0
root@cottage_client:~#

it is like there is no default route to an actual cateway.

[ottawa_craig1]

when I look at ip route show table 0 (see above post)
there is a default route via wan0 which of course is disabled.. I think that is odd.

[ottawa_craig1]

sorry I jumped the gun.. wlano is not disabled, I was thinking that was the wan port, but of course it is the wifi port that is running the uplink to 192.168.0.1 main router.

[kernel-panic69]

There is always a chance of dns lookup failures, which is why there are also hard-coded hostname/IP address(es) for NTP to resolve and update the time on the router. Without screenshots of your actual applicable configurations, I / we can only take shots in the dark guesses as to what the problem is. From a hard reset, configuration using wiki should work without a problem. Keep in mind, the more issues with these fake bridge modes people have, the quicker the option will disappear from DD-WRT. BrainSlayer has stated at least once in the forum and numerous times in our email banter that he has considered removing these options.

[ottawa_craig1]

happy to upload screen shots.
regarding; "which is why there are also hard-coded hostname/IP address(es) for NTP to resolve"

internaly the secondary router can not resolve ANY names (putty to root, nslookup fails steady)
I would like to setup a vpn afer I get this to work, and that will require time and name resolution to work

the upstream router is an arris 1670a (which is an intel puma chipset, so I thought WDS would be out of the question)

If not client bridged mode, what mode would you suggest.

I followed a tutorial, can you point me to "the configuration using wiki" that you refer to, so that I can follow it. There are a few different ones and I want to make sure we are on the same page.
Thanks for your help on this.
I can ping the default gateway from the client router, and it makes no diffenence to my symptoms if dnsmasq is enabled or not.

[ottawa_craig1]

add attachment

[ottawa_craig1]

add attachment

[kernel-panic69]

I presume wireguard is enabled:

[egc]

No that is always shown even if WireGuard is not enabled.

In a future update it will be hidden

[ottawa_craig1]

wiregaurd is not enabled.
some of the oddity, may be because my main router seems to be publishing ip6 dns names.
I put 8.8.8.8 in the setup panel for 'local dns' and now I can resolve names from the router.
odd thing now is that time.google.com although it can be resolved, the ntp derived time is wrong at boot. I think that is likely do the the wifi link not being up in time for the ntp resolver at boot.
but I am much closer now.

[egc]

You should leave that field (Server IP/Name) empty

[ottawa_craig1]

I put 192.168.0.1 in that field, because of this problem, thinking it might help having a dns address to go to. Now that it is in there, it doesn't seem like I can take it out, only modify it. Wich leads me to having 8.8.8.8 in there.