After a power cycle I suddenly found that CTF was available, though there are no options for FA. I've selected it and applied. I've also pointed the router to a few top-level DNS servers and checked the box to ignore ISP DNS. The problem still persists. I'm trying to get Comcrap to extend the lease time, but I have to constantly wade through low-level tech support that wants me to try a million things that I've already done.
Even though I think the premise is to be able to load those kernel modules on the fly, a reboot is always a safer bet. _________________ "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
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Fri Jun 24, 2022 19:18 Post subject:
FA requires more than one reboot, due to in chip FA accelerator I think its not enabled by default, and you should only use FA if you have gigabit WAN, less CTF should be fine.
Okay, if FA isn't necessary, then that's not an issue. CTF is enabled at least.
It happened again. Dropped the IP for a few seconds, reset the uptime counter. Right in the middle of an important call, and I'm in a near dead zone for cell service. This is rapidly making my nice, expensive router a borderline paperweight. Please let me know if there's anything I can try, or even a debug build I could load onto the router to provide further details.
The logs look a little different now. Maybe it's relevant, maybe not, but I figured I should update. This seems to coincide with another disconnect/reconnect and the last log entry was about a half hour prior. I did enable IPv6 yesterday, but it seems that Xfinity isn't using it, or maybe I need to do some additional work to get an IPv6 address.
Quote:
Jun 24 15:44:02 DD-WRT user.info : [ctf] : fast path forwarding successfully started
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: reading /tmp/resolv.dnsmasq
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: using nameserver 4.2.2.1#53
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: using nameserver 4.2.2.2#53
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: using only locally-known addresses for test
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: using only locally-known addresses for onion
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: using only locally-known addresses for localhost
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: using only locally-known addresses for local
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: using only locally-known addresses for invalid
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: using only locally-known addresses for bind
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: read /etc/hosts - 2 addresses
Jun 24 15:44:02 DD-WRT user.info : [wland] : daemon successfully stopped
Jun 24 15:44:02 DD-WRT user.info : [wland] : daemon successfully started
Jun 24 15:44:02 DD-WRT user.info : [wan] : WAN is up. IP: [redacted]
Jun 24 15:44:02 DD-WRT user.info : [dnsmasq] : daemon successfully stopped
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[9811]: exiting on receipt of SIGTERM
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: started, version 2.87test8 cachesize 1500
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-nftset no-auth cryptohash DNSSEC loop-detect inotify no-dumpfile
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq-dhcp[10845]: DHCP, IP range 192.168.1.64 -- 192.168.1.253, lease time 1d
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for test
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for onion
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for localhost
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for local
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for invalid
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for bind
Jun 24 15:44:02 DD-WRT user.info : [dnsmasq] : daemon successfully started
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: reading /tmp/resolv.dnsmasq
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using nameserver 4.2.2.1#53
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using nameserver 4.2.2.2#53
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for test
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for onion
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for localhost
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for local
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for invalid
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: using only locally-known addresses for bind
Jun 24 15:44:02 DD-WRT daemon.info dnsmasq[10845]: read /etc/hosts - 2 addresses
Jun 24 15:44:02 DD-WRT user.info : [radvd] : daemon successfully stopped
Jun 24 15:44:02 DD-WRT daemon.warn radvd[9813]: exiting, 1 sigterm(s) received
Jun 24 15:44:02 DD-WRT daemon.info radvd[9813]: sending stop adverts
Jun 24 15:44:02 DD-WRT daemon.info radvd[9813]: removing /var/run/radvd.pid
Jun 24 15:44:02 DD-WRT daemon.info radvd[9813]: returning from radvd main
Jun 24 15:44:02 DD-WRT daemon.info radvd[10846]: version 2.19 started
Jun 24 15:44:02 DD-WRT user.info : [radvd] : RADVD daemon successfully started
Jun 24 15:44:03 DD-WRT user.info : [vpn modules] : vpn modules successfully unloaded
Jun 24 15:44:03 DD-WRT user.info : [vpn modules] : nf_conntrack_proto_gre successfully loaded
Jun 24 15:44:03 DD-WRT user.info : [vpn modules] : nf_nat_proto_gre successfully loaded
Jun 24 15:44:03 DD-WRT user.info : [vpn modules] : nf_conntrack_pptp successfully loaded
Jun 24 15:44:03 DD-WRT user.info : [vpn modules] : nf_nat_pptp successfully loaded
Jun 24 15:44:03 DD-WRT user.info : [ctf] : fast path forwarding successfully started
Jun 24 15:44:03 DD-WRT user.info : [ctf] : fast path forwarding successfully started
Jun 24 15:44:03 DD-WRT user.info : [process_monitor] : daemon successfully stopped
Jun 24 15:44:03 DD-WRT daemon.info process_monitor[10019]: [process_monitor] : cleanup timers
Jun 24 15:44:03 DD-WRT user.info : [process_monitor] : successfully started
Jun 24 15:44:03 DD-WRT daemon.debug ntpclient[11043]: Connecting to 2.pool.ntp.org [65.100.46.164] ...
Jun 24 15:44:03 DD-WRT daemon.info ntpclient[11043]: Time set from 2.pool.ntp.org [65.100.46.164].
Jun 24 15:44:03 DD-WRT daemon.info process_monitor[11042]: Cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jun 24 15:44:03 DD-WRT daemon.info process_monitor[11042]: Local timer delta is 0
Jun 24 15:44:04 DD-WRT daemon.debug process_monitor[11042]: We need to re-update after 86400 seconds
Jun 24 15:44:04 DD-WRT daemon.info process_monitor[11042]: [process_monitor] : set timer: 86400 seconds, callback: ntp_main()
I'm guessing that switching over to CTF is probably changing a few things and that maybe some of these entries are incidental.[/quote]