DD-WRT :: View topic - Station Bridge (Routed) dir878a1 and dir882a1

Station Bridge (Routed) dir878a1 and dir882a1

DD-WRT Forum Index -> Ralink SoC based Hardware

View previous topic :: View next topic

Author

Message

dir882_mi
DD-WRT Novice

Joined: 06 Nov 2022
Posts: 42

Posted: Tue Jan 16, 2024 16:47 Post subject: Station Bridge (Routed) dir878a1 and dir882a1

Hello.
DD-WRT is amazing.

I have some routers ( dlink-dir632a , dlink-dir878-a1 , dlink-dir882-a1 , tplink_tl-wr741ndv4 ).
I followed this instaruction https://wiki.dd-wrt.com/wiki/index.php/Client_Bridged

dlink-dir632a and tplink_tl-wr741ndv4 work like repeaters(Station Bridge + VAP).
That is good.

But 878 and 882 can not do that.
Station Bridge (Routed) works (connects to main router via 2.4GHz) on r54079, but VAP not visible for devices (or not works). Devices tried connect via 5GHz, can not to receive ip adress.
Only via lan works for my PC. But without wifi connections.

Station Bridge (Routed) causes to cyclic reboot on r54914. Connects to main router for a few second and reboot.

Who have the ideas?
Maybe more information?

Sponsor

dale_gribble39
DD-WRT Guru

Joined: 11 Jun 2022
Posts: 1958

Posted: Wed Jan 17, 2024 15:37 Post subject:

Screenshots of your configuration, and system logs would help understand what is going on. Did you save each page and then reboot?
_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.
--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5

dir882_mi
DD-WRT Novice

Joined: 06 Nov 2022
Posts: 42

Posted: Wed Jan 17, 2024 18:30 Post subject:

dale_gribble39 wrote:

Screenshots of your configuration, and system logs would help understand what is going on. Did you save each page and then reboot?

Yes, I save every page and reboot.

I grab the log from usb flash:

Code:

killall syslogd
syslogd -L -s 8192 -O /mnt/sda1/messages

Because, I don't know how to grab the log by other way.

Code:

Jan 1 00:00:44 882 kern.warn kernel: [ 45.191425] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan 1 00:00:45 882 user.info : [cron] : daemon successfully stopped
Jan 1 00:00:45 882 user.info : [cron] : successfully started
Jan 1 00:00:45 882 cron.info cron[2267]: (CRON) STARTUP (fork ok)
Jan 1 00:00:45 882 daemon.err ntpclient[2004]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:00:45 882 daemon.err ntpclient[2004]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:00:45 882 daemon.notice ntpclient[2004]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:00:45 882 daemon.debug ntpclient[2004]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:00:48 882 daemon.debug ntpclient[2004]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:00:48 882 daemon.debug ntpclient[2004]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:00:51 882 daemon.debug ntpclient[2004]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:00:51 882 daemon.err process_monitor[2003]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:51 882 daemon.err process_monitor[2003]: Last update failed, we need to re-update after 30 seconds
Jan 1 00:00:51 882 daemon.debug process_monitor[2003]: We need to re-update after 3600 seconds
Jan 1 00:00:51 882 daemon.info process_monitor[2003]: [process_monitor] : set timer: 3600 seconds, callback: ntp_main()
Jan 1 00:01:26 882 daemon.err ntpclient[2284]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:01:26 882 daemon.err ntpclient[2284]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:01:26 882 daemon.notice ntpclient[2284]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:01:26 882 daemon.debug ntpclient[2284]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:01:29 882 daemon.debug ntpclient[2284]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:01:29 882 daemon.debug ntpclient[2284]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:01:32 882 daemon.debug ntpclient[2284]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:01:32 882 daemon.err process_monitor[2003]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:02:07 882 daemon.err ntpclient[2297]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:02:07 882 daemon.err ntpclient[2297]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:02:07 882 daemon.notice ntpclient[2297]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:02:07 882 daemon.debug ntpclient[2297]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:02:10 882 daemon.debug ntpclient[2297]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:02:10 882 daemon.debug ntpclient[2297]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:02:13 882 daemon.debug ntpclient[2297]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:02:13 882 daemon.err process_monitor[2003]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:45 882 kern.warn kernel: [ 45.682775] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan 1 00:00:45 882 user.info : [cron] : daemon successfully stopped
Jan 1 00:00:45 882 user.info : [cron] : successfully started
Jan 1 00:00:45 882 cron.info cron[2269]: (CRON) STARTUP (fork ok)
Jan 1 00:00:45 882 daemon.err ntpclient[2005]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:00:45 882 daemon.err ntpclient[2005]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:00:45 882 daemon.notice ntpclient[2005]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:00:45 882 daemon.debug ntpclient[2005]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:00:48 882 daemon.debug ntpclient[2005]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:00:48 882 daemon.debug ntpclient[2005]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:00:51 882 daemon.debug ntpclient[2005]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:00:51 882 daemon.err process_monitor[2004]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:51 882 daemon.err process_monitor[2004]: Last update failed, we need to re-update after 30 seconds
Jan 1 00:00:51 882 daemon.debug process_monitor[2004]: We need to re-update after 3600 seconds
Jan 1 00:00:51 882 daemon.info process_monitor[2004]: [process_monitor] : set timer: 3600 seconds, callback: ntp_main()
Jan 1 00:00:44 882 kern.warn kernel: [ 45.077809] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Jan 1 00:00:44 882 kern.warn kernel: [ 45.105873] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan 1 00:00:44 882 user.info : [cron] : daemon successfully stopped
Jan 1 00:00:45 882 user.info : [cron] : successfully started
Jan 1 00:00:45 882 cron.info cron[2267]: (CRON) STARTUP (fork ok)
Jan 1 00:00:45 882 daemon.err ntpclient[2004]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:00:45 882 daemon.err ntpclient[2004]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:00:45 882 daemon.notice ntpclient[2004]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:00:45 882 daemon.debug ntpclient[2004]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:00:48 882 daemon.debug ntpclient[2004]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:00:48 882 daemon.debug ntpclient[2004]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:00:51 882 daemon.debug ntpclient[2004]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:00:51 882 daemon.err process_monitor[2003]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:51 882 daemon.err process_monitor[2003]: Last update failed, we need to re-update after 30 seconds
Jan 1 00:00:51 882 daemon.debug process_monitor[2003]: We need to re-update after 3600 seconds
Jan 1 00:00:51 882 daemon.info process_monitor[2003]: [process_monitor] : set timer: 3600 seconds, callback: ntp_main()
Jan 1 00:01:26 882 daemon.err ntpclient[2284]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:01:26 882 daemon.err ntpclient[2284]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:01:26 882 daemon.notice ntpclient[2284]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:01:26 882 daemon.debug ntpclient[2284]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:01:29 882 daemon.debug ntpclient[2284]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:01:29 882 daemon.debug ntpclient[2284]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:01:32 882 daemon.debug ntpclient[2284]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:01:32 882 daemon.err process_monitor[2003]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:48 882 daemon.debug ntpclient[2005]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:00:48 882 daemon.debug ntpclient[2005]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:00:51 882 daemon.debug ntpclient[2005]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:00:51 882 daemon.err process_monitor[2004]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:51 882 daemon.err process_monitor[2004]: Last update failed, we need to re-update after 30 seconds
Jan 1 00:00:51 882 daemon.debug process_monitor[2004]: We need to re-update after 3600 seconds
Jan 1 00:00:51 882 daemon.info process_monitor[2004]: [process_monitor] : set timer: 3600 seconds, callback: ntp_main()
Jan 1 00:01:26 882 daemon.err ntpclient[2286]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:01:26 882 daemon.err ntpclient[2286]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:01:26 882 daemon.notice ntpclient[2286]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:01:26 882 daemon.debug ntpclient[2286]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:01:29 882 daemon.debug ntpclient[2286]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:01:29 882 daemon.debug ntpclient[2286]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:01:32 882 daemon.debug ntpclient[2286]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:01:32 882 daemon.err process_monitor[2004]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)

There was 1 self-reboot, 1 press to power button, 1 self-reboot

Last edited by dir882_mi on Wed Jan 17, 2024 18:40; edited 2 times in total

dir882_mi
DD-WRT Novice

Joined: 06 Nov 2022
Posts: 42

Posted: Wed Jan 17, 2024 18:36 Post subject:
first part

dir882_mi
DD-WRT Novice

Joined: 06 Nov 2022
Posts: 42

Posted: Wed Jan 17, 2024 18:36 Post subject:
Second part

dale_gribble39
DD-WRT Guru

Joined: 11 Jun 2022
Posts: 1958

Posted: Wed Jan 17, 2024 18:44 Post subject:

Try using Auto (DHCP) Default GW Mode on the Station interface. Ensure that the output of nvram show | grep block_multicast is 1. Don't know why you're using FAT for filesystem on USB, but it appears to be dirty. Using EXT4 is probably better.
_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.
--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5

dir882_mi
DD-WRT Novice

Joined: 06 Nov 2022
Posts: 42

Posted: Wed Jan 17, 2024 20:25 Post subject:

dale_gribble39 wrote:

Use Auto (DHCP) Default GW Mode on the Station interface don't help, also cyclic reboot.
When my main router off, "Station Bridge" router boots.

New log , chenged to auto DHCP, and manual reboot.
And again cyclic reboot.

Code:

Jan 1 00:00:44 882 kern.warn kernel: [ 44.801734] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan 1 00:00:44 882 daemon.err ntpclient[1992]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:00:44 882 daemon.err ntpclient[1992]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:00:44 882 daemon.notice ntpclient[1992]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:00:44 882 daemon.debug ntpclient[1992]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:00:44 882 user.info : [cron] : daemon successfully stopped
Jan 1 00:00:44 882 user.info : [cron] : successfully started
Jan 1 00:00:44 882 cron.info cron[2256]: (CRON) STARTUP (fork ok)
Jan 1 00:00:47 882 daemon.debug ntpclient[1992]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:00:47 882 daemon.debug ntpclient[1992]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:00:50 882 daemon.debug ntpclient[1992]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:00:50 882 daemon.err process_monitor[1991]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:50 882 daemon.err process_monitor[1991]: Last update failed, we need to re-update after 30 seconds
Jan 1 00:00:50 882 daemon.debug process_monitor[1991]: We need to re-update after 3600 seconds
Jan 1 00:00:50 882 daemon.info process_monitor[1991]: [process_monitor] : set timer: 3600 seconds, callback: ntp_main()
Jan 1 00:01:25 882 daemon.err ntpclient[2272]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:01:25 882 daemon.err ntpclient[2272]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:01:25 882 daemon.notice ntpclient[2272]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:01:25 882 daemon.debug ntpclient[2272]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:01:28 882 daemon.debug ntpclient[2272]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:01:28 882 daemon.debug ntpclient[2272]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:01:31 882 daemon.debug ntpclient[2272]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:01:31 882 daemon.err process_monitor[1991]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:02:06 882 daemon.err ntpclient[2285]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:02:06 882 daemon.err ntpclient[2285]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:02:06 882 daemon.notice ntpclient[2285]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:02:06 882 daemon.debug ntpclient[2285]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:02:09 882 daemon.debug ntpclient[2285]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:02:09 882 daemon.debug ntpclient[2285]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:02:12 882 daemon.debug ntpclient[2285]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:02:12 882 daemon.err process_monitor[1991]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:02:21 882 daemon.info httpd[2004]: [httpd] : Authentication fail
Jan 1 00:02:40 882 user.info : [servicemanager] : waiting for services to finish (3)...
Jan 1 00:02:40 882 user.info : [relayd] : Client Bridge Relay Daemon successfully stopped
Jan 1 00:02:41 882 kern.info kernel: [ 161.613801] br0: port 3(wlan1) entered disabled state
Jan 1 00:02:41 882 kern.info kernel: [ 161.624015] br0: port 2(vlan2) entered disabled state
Jan 1 00:02:41 882 kern.info kernel: [ 161.634179] br0: port 1(vlan1) entered disabled state
Jan 1 00:02:41 882 user.info : [bridge] : interface vlan1 successfully deleted from bridge br0
Jan 1 00:02:41 882 kern.info kernel: [ 161.765778] device vlan1 left promiscuous mode
Jan 1 00:02:41 882 kern.info kernel: [ 161.776029] br0: port 1(vlan1) entered disabled state
Jan 1 00:02:41 882 user.info : [bridge] : interface vlan2 successfully deleted from bridge br0
Jan 1 00:02:41 882 kern.info kernel: [ 161.794760] device vlan2 left promiscuous mode
Jan 1 00:02:41 882 kern.info kernel: [ 161.804043] device eth0 left promiscuous mode
Jan 1 00:02:41 882 kern.info kernel: [ 161.815639] br0: port 2(vlan2) entered disabled state
Jan 1 00:02:41 882 user.info : [bridge] : bridge br0 successfully deleted
Jan 1 00:02:41 882 kern.info kernel: [ 161.834530] device wlan1 left promiscuous mode
Jan 1 00:02:41 882 kern.info kernel: [ 161.844872] br0: port 3(wlan1) entered disabled state
Jan 1 00:02:41 882 user.info : [ubusd] : daemon successfully stopped
Jan 1 00:02:42 882 user.info : [hostapd] : hostapd daemon successfully stopped
Jan 1 00:02:42 882 user.info : [wpa_supplicant] : wpa_supplicant daemon successfully stopped
Jan 1 00:02:42 882 user.debug : mac80211: start deconfigure_single_ath9k
Jan 1 00:02:42 882 user.debug : mac80211: start delete_ath9k_devices
Jan 1 00:02:42 882 user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Jan 1 00:02:42 882 user.debug : mac80211: leave delete_ath9k_devices
Jan 1 00:02:42 882 user.debug : mac80211: leave deconfigure_single_ath9k
Jan 1 00:02:42 882 user.debug : mac80211: start deconfigure_single_ath9k
Jan 1 00:02:42 882 user.debug : mac80211: start delete_ath9k_devices
Jan 1 00:02:42 882 user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Jan 1 00:02:42 882 user.debug : mac80211: leave delete_ath9k_devices
Jan 1 00:02:42 882 user.debug : mac80211: leave deconfigure_single_ath9k
Jan 1 00:02:42 882 user.info : [bridge] : bridge br0 successfully added
Jan 1 00:02:42 882 kern.info kernel: [ 162.983225] device br0 entered promiscuous mode
Jan 1 00:02:42 882 user.info : [bridge] : interface vlan1 successfully added to bridge br0
Jan 1 00:02:42 882 kern.info kernel: [ 163.058411] br0: port 1(vlan1) entered blocking state
Jan 1 00:02:42 882 kern.info kernel: [ 163.069871] br0: port 1(vlan1) entered disabled state
Jan 1 00:02:42 882 kern.info kernel: [ 163.082954] device vlan1 entered promiscuous mode
Jan 1 00:02:42 882 kern.info kernel: [ 163.094753] device eth0 entered promiscuous mode
Jan 1 00:02:42 882 user.info : [bridge] : interface vlan2 successfully added to bridge br0
Jan 1 00:02:42 882 kern.info kernel: [ 163.167576] br0: port 2(vlan2) entered blocking state
Jan 1 00:02:42 882 kern.info kernel: [ 163.178994] br0: port 2(vlan2) entered disabled state
Jan 1 00:02:42 882 kern.info kernel: [ 163.192103] device vlan2 entered promiscuous mode
Jan 1 00:02:42 882 kern.info kernel: [ 163.210895] br0: port 2(vlan2) entered blocking state
Jan 1 00:02:42 882 kern.info kernel: [ 163.220978] br0: port 2(vlan2) entered forwarding state
Jan 1 00:02:42 882 kern.info kernel: [ 163.231468] br0: port 1(vlan1) entered blocking state
Jan 1 00:02:43 882 kern.info kernel: [ 163.241525] br0: port 1(vlan1) entered forwarding state
Jan 1 00:02:43 882 kern.info kernel: [ 163.252095] device br0 left promiscuous mode
Jan 1 00:02:43 882 kern.info kernel: [ 163.266262] device br0 entered promiscuous mode
Jan 1 00:02:43 882 kern.info kernel: [ 163.287879] device br0 left promiscuous mode
Jan 1 00:02:43 882 user.debug : mac80211: start deconfigure_single_ath9k
Jan 1 00:02:43 882 user.debug : mac80211: start delete_ath9k_devices
Jan 1 00:02:43 882 user.debug : mac80211: leave delete_ath9k_devices
Jan 1 00:02:43 882 user.debug : mac80211: leave deconfigure_single_ath9k
Jan 1 00:02:43 882 user.debug : mac80211: start deconfigure_single_ath9k
Jan 1 00:02:43 882 user.debug : mac80211: start delete_ath9k_devices
Jan 1 00:02:43 882 user.debug : mac80211: leave delete_ath9k_devices
Jan 1 00:02:43 882 user.debug : mac80211: leave deconfigure_single_ath9k
Jan 1 00:02:43 882 user.debug : mac80211: start configure_single_ath9k
Jan 1 00:02:43 882 user.debug : mac80211: start setRTS
Jan 1 00:02:43 882 user.debug : mac80211: leave setRTS
Jan 1 00:02:47 882 daemon.err ntpclient[2607]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:02:47 882 daemon.err ntpclient[2607]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:02:47 882 daemon.notice ntpclient[2607]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:02:47 882 daemon.debug ntpclient[2607]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:02:47 882 daemon.err ntpclient[2607]: Failed connecting to 212.18.3.19 [212.18.3.19]: Network unreachable
Jan 1 00:02:47 882 daemon.debug ntpclient[2607]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:02:47 882 daemon.err ntpclient[2607]: Failed connecting to 88.99.174.22 [88.99.174.22]: Network unreachable
Jan 1 00:02:47 882 daemon.err process_monitor[1991]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5885 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5865 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5845 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5825 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5805 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5785 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5765 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5745 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5720 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5680 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5660 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5640 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5620 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5600 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5580 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5560 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5540 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5520 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5500 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5320 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5300 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5280 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5260 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5240 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5220 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5200 qual:100 noise:-92 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5700 qual:99 noise:-91 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq:5180 qual:99 noise:-91 eirp: 24
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5885 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5865 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5845 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5825 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5805 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5785 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5765 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5745 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5720 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5680 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5660 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5640 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5620 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5600 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5580 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5560 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5540 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5520 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5500 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5320 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5300 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5280 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5260 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5240 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5220 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5200 default quality 100
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5700 default quality 99
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: freq: 5180 default quality 99
Jan 1 00:02:50 882 user.info : [autochannel] : wlan1: selected: 5200
Jan 1 00:02:50 882 user.debug : mac80211: start setMacFilter
Jan 1 00:02:50 882 user.debug : mac80211: leave setMacFilter
Jan 1 00:02:50 882 kern.info kernel: [ 171.005021] br0: port 3(wlan1) entered blocking state
Jan 1 00:02:50 882 kern.info kernel: [ 171.017898] br0: port 3(wlan1) entered disabled state
Jan 1 00:02:50 882 daemon.info hostapd: ieee80211ac_supported_vht_capab: set vht cap 338001F9
Jan 1 00:02:50 882 kern.info kernel: [ 171.031017] device wlan1 entered promiscuous mode
Jan 1 00:02:51 882 kern.info kernel: [ 171.835146] br0: port 3(wlan1) entered blocking state
Jan 1 00:02:51 882 kern.info kernel: [ 171.845245] br0: port 3(wlan1) entered forwarding state
Jan 1 00:02:51 882 user.info : [hostapd] : successfully started
Jan 1 00:02:51 882 user.info : [bridge] : interface wlan1 successfully added to bridge br0
Jan 1 00:02:51 882 user.debug : mac80211: start configure_single_ath9k
Jan 1 00:02:51 882 user.debug : mac80211: start setRTS
Jan 1 00:02:51 882 user.debug : mac80211: leave setRTS
Jan 1 00:02:51 882 user.info : [wpa_supplicant] : successfully started
Jan 1 00:02:51 882 user.info : [bridge] : interface wlan0 successfully added to bridge br0
Jan 1 00:02:52 882 user.info : [gratarp] : successfully started
Jan 1 00:02:52 882 user.info root: WireGuard no wan_gateway detected, assuming WAP
Jan 1 00:02:52 882 user.info root: WireGuard no wan_gateway detected, assuming WAP
Jan 1 00:02:53 882 user.info : [wland] : Error on startup, returncode 2
Jan 1 00:02:53 882 user.info root: WireGuard no wan_gateway detected, assuming WAP
Jan 1 00:02:54 882 user.info root: WireGuard no wan_gateway detected, assuming WAP
Jan 1 00:02:55 882 daemon.info process_monitor[1991]: [process_monitor] : cleanup timers
Jan 1 00:02:55 882 user.info : [process_monitor] : daemon successfully stopped
Jan 1 00:02:55 882 user.info : [process_monitor] : successfully started
Jan 1 00:02:56 882 user.info : [init] : Terminated....................................
Jan 1 00:02:56 882 user.info : [init] : send dhcp lease release signal
Jan 1 00:02:57 882 user.info : [init] : Sending SIGTERM to all processes
Jan 1 02:02:57 882 syslog.info syslogd exiting
Jan 1 00:00:45 882 kern.warn kernel: [ 46.059482] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan 1 00:00:45 882 user.info : [cron] : daemon successfully stopped
Jan 1 00:00:45 882 user.info : [cron] : successfully started
Jan 1 00:00:45 882 cron.info cron[2274]: (CRON) STARTUP (fork ok)
Jan 1 00:00:47 882 daemon.debug ntpclient[2010]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:00:47 882 daemon.debug ntpclient[2010]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:00:50 882 daemon.debug ntpclient[2010]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:00:50 882 daemon.err process_monitor[2009]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:50 882 daemon.err process_monitor[2009]: Last update failed, we need to re-update after 30 seconds
Jan 1 00:00:50 882 daemon.debug process_monitor[2009]: We need to re-update after 3600 seconds
Jan 1 00:00:50 882 daemon.info process_monitor[2009]: [process_monitor] : set timer: 3600 seconds, callback: ntp_main()
Jan 1 00:00:45 882 kern.info kernel: [ 45.365026] mtk_soc_eth 1e100000.ethernet eth0: port 2 link down
Jan 1 00:00:47 882 daemon.debug ntpclient[2010]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:00:47 882 daemon.debug ntpclient[2010]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:00:50 882 daemon.debug ntpclient[2010]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:00:50 882 daemon.err process_monitor[2009]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 1 00:00:50 882 daemon.err process_monitor[2009]: Last update failed, we need to re-update after 30 seconds
Jan 1 00:00:50 882 daemon.debug process_monitor[2009]: We need to re-update after 3600 seconds
Jan 1 00:00:50 882 daemon.info process_monitor[2009]: [process_monitor] : set timer: 3600 seconds, callback: ntp_main()
Jan 1 00:01:25 882 daemon.err ntpclient[2290]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:01:25 882 daemon.err ntpclient[2290]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 00:01:25 882 daemon.notice ntpclient[2290]: Network up, resolved address to hostname 212.18.3.19
Jan 1 00:01:25 882 daemon.debug ntpclient[2290]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 00:01:28 882 daemon.debug ntpclient[2290]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 00:01:28 882 daemon.debug ntpclient[2290]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 00:01:31 882 daemon.debug ntpclient[2290]: Timed out waiting for 88.99.174.22 [88.99.174.22].
Jan 1 00:01:31 882 daemon.err process_monitor[2009]: cyclic NTP Update failed (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)

dir882_mi
DD-WRT Novice

Joined: 06 Nov 2022
Posts: 42

Posted: Wed Jan 17, 2024 20:25 Post subject:

dale_gribble39 wrote:

Now USB just for logging.

Use Auto (DHCP) Default GW Mode on the Station interface don't help, also cyclic reboot.
When my main router off, "Station Bridge" router boots.

New log , changed to auto DHCP, and manual reboot.
And again cyclic reboot.

Code:

dale_gribble39
DD-WRT Guru

Joined: 11 Jun 2022
Posts: 1958

Posted: Wed Jan 17, 2024 21:19 Post subject:

Try switching from "Router" to "Gateway" mode on Setup -> Advanced Routing tab. On wlan0, try "Mixed" and either "Full 20MHz" or "Dynamic 20/40Hz". Seems that this is a bit of an ongoing problem:

DIR-878 client bridge problem
r6700v2 and Client Bridge - working with a "poke"
Client Bridge Mode Not Available
_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.
--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5

dir882_mi
DD-WRT Novice

Joined: 06 Nov 2022
Posts: 42

Posted: Wed Jan 17, 2024 23:13 Post subject:

dale_gribble39 wrote:

That seems the problem is permanently.
Nothing help: Gateway, Wireless setting(Network Mode
Channel Width), DHCP auto or manual, even by links only issue.

I tried 11-03-2018-r37582 build and repeater bridge work(connect without reboot), but VAP does not work.

Display posts from previous:

Page 1 of 1

DD-WRT Forum Index -> Ralink SoC based Hardware

All times are GMT

Navigation

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Log in

Station Bridge (Routed) dir878a1 and dir882a1

Quick Links

Log in