Menu
What's new
By:
Filters Better Search

[Beta] Asuswrt-merlin 380.68 Beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
I have a RT-AC3200 running in AP Mode.... I just upgraded to 380.68 Beta from 380.67 and the router is not able to do a NTP update. I keep getting this error... This was not an issue before. Thanks...

Jul 31 18:00:41 ntp: start NTP update
Jul 31 18:01:09 ntp: start NTP update
Jul 31 18:01:36 ntp: start NTP update
Jul 31 18:02:03 ntp: start NTP update
Jul 31 18:02:30 ntp: start NTP update
Jul 31 18:02:57 ntp: start NTP update
Jul 31 18:03:24 ntp: start NTP update
Jul 31 18:03:51 ntp: start NTP update
Jul 31 18:04:18 ntp: start NTP update
Jul 31 18:04:45 ntp: start NTP update
Jul 31 18:05:12 ntp: start NTP update
Jul 31 18:05:39 ntp: start NTP update
Jul 31 18:06:06 ntp: start NTP update
Jul 31 18:06:33 ntp: start NTP update
Jul 31 18:07:00 ntp: start NTP update
Jul 31 18:07:27 ntp: start NTP update
Jul 31 18:07:54 ntp: start NTP update
Jul 31 18:08:21 ntp: start NTP update
Jul 31 18:08:48 ntp: start NTP update
 
As I glanced over the router boot up log (RT-AC3200 in AP Mode), I saw all these error messages that I've never seen before.... What seems to be the problem, and how do I fix this? Thanks...

Jul 31 18:00:12 kernel: brd: module loaded
Jul 31 18:00:12 kernel: loop: module loaded
Jul 31 18:00:12 kernel: pflash: found no supported devices
Jul 31 18:00:12 kernel: bcmsflash: found no supported devices
Jul 31 18:00:12 kernel: Boot partition size = 524288(0x80000)
Jul 31 18:00:12 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
Jul 31 18:00:12 kernel: nflash: squash filesystem with lzma found at block 29
Jul 31 18:00:12 kernel: Creating 4 MTD partitions on "nflash":
Jul 31 18:00:12 kernel: 0x000000000000-0x000000080000 : "boot"
Jul 31 18:00:12 kernel: 0x000000080000-0x000000200000 : "nvram"
Jul 31 18:00:12 kernel: 0x000000200000-0x000004000000 : "linux"
Jul 31 18:00:12 kernel: 0x0000003b2af0-0x000004000000 : "rootfs"
Jul 31 18:00:12 kernel: PPP generic driver version 2.4.2
Jul 31 18:00:12 kernel: PPP MPPE Compression module registered
Jul 31 18:00:12 kernel: NET: Registered protocol family 24
Jul 31 18:00:12 kernel: PPTP driver version 0.8.5
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache ent�U�4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:176 terminated OK
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to r8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:16c terminated OK
Jul 31 18:00:13 kernel: <6>br1: port 1(eth1) entering forwarding state
Jul 31 18:00:13 kernel: <6>device eth1 left promiscuous mode
Jul 31 18:00:13 kernel: <6>br1: port 1(eth1) entering disabled state
Jul 31 18:00:13 kernel: <4>g_thread:166 terminated OK
 
MXM said:
As I glanced over the router boot up log (RT-AC3200 in AP Mode), I saw all these error messages that I've never seen before.... What seems to be the problem, and how do I fix this? Thanks...

Jul 31 18:00:12 kernel: brd: module loaded
Jul 31 18:00:12 kernel: loop: module loaded
Jul 31 18:00:12 kernel: pflash: found no supported devices
Jul 31 18:00:12 kernel: bcmsflash: found no supported devices
Jul 31 18:00:12 kernel: Boot partition size = 524288(0x80000)
Jul 31 18:00:12 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
Jul 31 18:00:12 kernel: nflash: squash filesystem with lzma found at block 29
Jul 31 18:00:12 kernel: Creating 4 MTD partitions on "nflash":
Jul 31 18:00:12 kernel: 0x000000000000-0x000000080000 : "boot"
Jul 31 18:00:12 kernel: 0x000000080000-0x000000200000 : "nvram"
Jul 31 18:00:12 kernel: 0x000000200000-0x000004000000 : "linux"
Jul 31 18:00:12 kernel: 0x0000003b2af0-0x000004000000 : "rootfs"
Jul 31 18:00:12 kernel: PPP generic driver version 2.4.2
Jul 31 18:00:12 kernel: PPP MPPE Compression module registered
Jul 31 18:00:12 kernel: NET: Registered protocol family 24
Jul 31 18:00:12 kernel: PPTP driver version 0.8.5
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache ent�U�4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:176 terminated OK
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to r8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:16c terminated OK
Jul 31 18:00:13 kernel: <6>br1: port 1(eth1) entering forwarding state
Jul 31 18:00:13 kernel: <6>device eth1 left promiscuous mode
Jul 31 18:00:13 kernel: <6>br1: port 1(eth1) entering disabled state
Jul 31 18:00:13 kernel: <4>g_thread:166 terminated OK
Click to expand...

I decided to reflash the router a second time, and this time this error is not present.... Must have been an issue with the original flash....

However, the NTP error is still there....

Jul 31 18:00:41 ntp: start NTP update
Jul 31 18:01:08 ntp: start NTP update
Jul 31 18:01:35 ntp: start NTP update
Jul 31 18:02:02 ntp: start NTP update
Jul 31 18:02:29 ntp: start NTP update
Jul 31 18:02:56 ntp: start NTP update
Jul 31 18:03:23 ntp: start NTP update
Jul 31 18:03:50 ntp: start NTP update
Jul 31 18:04:17 ntp: start NTP update
Jul 31 18:04:44 ntp: start NTP update
Jul 31 18:05:11 ntp: start NTP update
 
MXM said:
I have a RT-AC3200 running in AP Mode.... I just upgraded to 380.68 Beta from 380.67 and the router is not able to do a NTP update. I keep getting this error... This was not an issue before. Thanks...

Jul 31 18:00:41 ntp: start NTP update
Jul 31 18:01:09 ntp: start NTP update
Jul 31 18:01:36 ntp: start NTP update
Jul 31 18:02:03 ntp: start NTP update
Jul 31 18:02:30 ntp: start NTP update
Jul 31 18:02:57 ntp: start NTP update
Jul 31 18:03:24 ntp: start NTP update
Jul 31 18:03:51 ntp: start NTP update
Jul 31 18:04:18 ntp: start NTP update
Jul 31 18:04:45 ntp: start NTP update
Jul 31 18:05:12 ntp: start NTP update
Jul 31 18:05:39 ntp: start NTP update
Jul 31 18:06:06 ntp: start NTP update
Jul 31 18:06:33 ntp: start NTP update
Jul 31 18:07:00 ntp: start NTP update
Jul 31 18:07:27 ntp: start NTP update
Jul 31 18:07:54 ntp: start NTP update
Jul 31 18:08:21 ntp: start NTP update
Jul 31 18:08:48 ntp: start NTP update
Click to expand...

After some digging around, I was using time-c.nist.gov as my NTP server. I also tried the time-a.nist.gov. But neither one worked despite them being up and running.

Then I tried using their respective IP addresses and then the NTP update worked just fine. So, it looks like some DNS resolution problem within the router firmware....
 
MXM said:
After some digging around, I was using time-c.nist.gov as my NTP server. I also tried the time-a.nist.gov. But neither one worked despite them being up and running.

Then I tried using their respective IP addresses and then the NTP update worked just fine. So, it looks like some DNS resolution problem within the router firmware....
Click to expand...

I don't think internal name resolution works while in AP mode, only in Router mode.
 
thelonelycoder said:
Add this to the /jffs/scripts/wan-start:
Code: 
sleep 5
nvram set wan0_realip_ip=
nvram set wan0_realip_state=0
Click to expand...
Have this added and the router reboots. The flashing indicator is still there. :confused:

wan.png
 
eclp said:
Have this added and the router reboots. The flashing indicator is still there. :confused:

View attachment 10105
Click to expand...
You may have to increase the sleep time to 8 or so.
Also, is wan-start set as executable, are the line endings in Unix format?
Code: 
chmod a+rx /jffs/scripts/wan-start
dos2unix /jffs/scripts/wan-start
You do not need to restart the router to test it, just enter this:
Code: 
/jffs/scripts/wan-start
 
OK thanks! It works now ...
Code: 
/jffs/scripts/wan-start
 
On occasion, I use a script to start a Selective routing PPTP Client

e.g.
https://www.snbforums.com/threads/delay-pptp-vpn-start.38026/#post-313277

whilst there are several concurrent Selective OpenVPN clients ACTIVE.

Under this Beta, when starting the Selective PPTP Client, ALL ACTIVE OpenVPN clients are now immediately terminated seemingly by the command request

Code: 
service restart_vpncall

before the PPTP client is initiated/initialised ?

Code: 
17:22:00 RT-AC68U user.warn (VPN_Client_Switch.sh): 21341 Request..... [status]
17:22:01 RT-AC68U user.warn (VPN_Client_Switch.sh): 21341 VPN Client Status:
17:22:01 RT-AC68U user.warn (VPN_Client_Switch.sh): 21341 *NO VPN Clients connected*

17:22:07 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 Request..... [1 on]
17:22:07 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 No VPN ACTIVE - Starting VPN Client 1
17:22:08 RT-AC68U kern.notice rc_service: service 22155:notify_rc start_vpnclient1
17:22:09 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 Waiting for VPN Client 1 (NewYork) to connect.....
17:22:10 RT-AC68U kern.notice custom_script: Running /jffs/scripts/openvpnclient1.postconf (args: /etc/openvpn/client1/config.ovpn)
17:22:10 RT-AC68U user.warn (openvpnclient1.postconf): 22189 v2.50 Started..... [/etc/openvpn/client1/config.ovpn]
17:22:10 RT-AC68U user.warn (openvpnclient1.postconf): 22189 VPN Client 1 is allowed to BIND to any WAN interface ('br0:VPN' not found!)
17:22:10 RT-AC68U user.warn (openvpnclient1.postconf): 22189 Complete.
17:22:11 RT-AC68U daemon.notice openvpn[22221]: OpenVPN 2.4.3 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Aug 13 2017
17:22:11 RT-AC68U daemon.notice openvpn[22221]: library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.08
17:22:11 RT-AC68U daemon.warn openvpn[22222]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
17:22:11 RT-AC68U daemon.notice openvpn[22222]: TCP/UDP: Preserving recently used remote address: [AF_INET]XXX.XXX.XXX.XXX
17:22:11 RT-AC68U daemon.notice openvpn[22222]: Socket Buffers: R=[122880->122880] S=[122880->122880]
<snip>
17:22:13 RT-AC68U daemon.notice openvpn[22222]: TUN/TAP device tun11 opened
17:22:13 RT-AC68U daemon.notice openvpn[22222]: TUN/TAP TX queue length set to 100
17:22:13 RT-AC68U daemon.notice openvpn[22222]: do_ifconfig, tt->did_ifconfig_ipv6_setup=0
17:22:13 RT-AC68U daemon.notice openvpn[22222]: /usr/sbin/ip link set dev tun11 up mtu 1500
17:22:14 RT-AC68U daemon.notice openvpn[22222]: /usr/sbin/ip addr add dev tun11 ZZZ.ZZZ.ZZZ.147/24 broadcast ZZZ.ZZZ.ZZZ.255
17:22:14 RT-AC68U daemon.notice openvpn[22222]: updown.sh tun11 1500 1558 ZZZ.ZZZ.ZZZ.147 255.255.255.0 init
17:22:14 RT-AC68U user.warn openvpn-updown: Forcing 172.16.0.1 to use DNS server 100.120.0.1
17:22:14 RT-AC68U kern.notice rc_service: service 22348:notify_rc updateresolv
17:22:15 RT-AC68U user.warn custom_script: Running /jffs/scripts/openvpn-event (args: tun11 1500 1558 ZZZ.ZZZ.ZZZ.147 255.255.255.0 init)
17:22:15 RT-AC68U user.warn openvpn-event[22367]: User openvpn-event running
17:22:15 RT-AC68U user.warn openvpn-event[22367]:      Script executing.. for event: vpnclient1-up
17:22:15 RT-AC68U user.warn (vpnclient1-up): 22381 User Processing 'up' (tun11) via ZZZ.ZZZ.ZZZ.147 args = [tun11 1500 1558 ZZZ.ZZZ.ZZZ.147 255.255.255.0 init]
17:22:15 RT-AC68U user.warn (vpnclient1-up): 22381 Added cru #GetVPN1_WANIP# every hh:01
17:22:15 RT-AC68U user.warn (vpnclient1-up): 22381 User Processing Complete.
17:22:15 RT-AC68U user.warn (VPN_SyslogMonitor.sh): 22410 VPN Syslog Event Monitor starting.....
17:22:17 RT-AC68U daemon.notice openvpn[22222]: /usr/sbin/ip route add WWW.WWW.WWW.WWW/32 via WWW.WWW.WWW.WWW
17:22:17 RT-AC68U daemon.notice openvpn[22222]: /usr/sbin/ip route add 0.0.0.0/1 via ZZZ.ZZZ.ZZZ.1
17:22:17 RT-AC68U daemon.notice openvpn[22222]: /usr/sbin/ip route add 128.0.0.0/1 via ZZZ.ZZZ.ZZZ.1
17:22:17 RT-AC68U user.warn (vpnrouting.sh): 22444 v380.66 Patched by Martineau vpnrouting.sh
17:22:17 RT-AC68U user.warn openvpn-routing: Configuring policy rules for client 1
17:22:17 RT-AC68U user.warn openvpn-routing: Creating VPN routing table (mode 2)
17:22:17 RT-AC68U user.warn (vpnrouting.sh): 22444 Martineau Deleting routes 0.0.0.0/1 and 128.0.0.0/1 from table main (254)
17:22:18 RT-AC68U user.warn (vpnrouting.sh): 22444 Martineau Skipping deletion of rule 10000  unoffically reserved for WAN fwmark 0x7000
17:22:18 RT-AC68U user.warn openvpn-routing: Adding route for 172.16.0.1 to 0.0.0.0 through VPN client 1
17:22:18 RT-AC68U user.warn (vpnrouting.sh): 22444 Martineau Adding VPN1 RPDB fwmark rule 0x1000 prio 10100
17:22:18 RT-AC68U user.warn openvpn-routing: Completed routing policy configuration for client 1
17:22:18 RT-AC68U user.warn custom script: Running /jffs/scripts/openvpn-event (args: tun11 1500 1558 ZZZ.ZZZ.ZZZ.147 )
17:22:18 RT-AC68U user.warn openvpn-event[22597]: User openvpn-event running
17:22:18 RT-AC68U user.warn openvpn-event[22597]:      Script executing.. for event: vpnclient1-route-up
17:22:18 RT-AC68U user.warn (vpnclient1-route-up): 22610 User Processing 'route-up' (tun11) via ZZZ.ZZZ.ZZZ.147 args=[tun11 1500 1558 ZZZ.ZZZ.ZZZ.147]
17:22:18 RT-AC68U user.warn (vpnclient1-route-up): 22610 CMD: ip route add 10.8.0.0/24 dev tun21 table NewYork
17:22:18 RT-AC68U user.warn (vpnclient1-route-up): 22610 CMD: ip route add 10.16.0.0/24 dev tun22 table NewYork
17:22:19 RT-AC68U user.warn (vpnclient1-route-up): 22610 User Processing Complete.
17:22:19 RT-AC68U daemon.notice openvpn[22222]: Initialization Sequence Completed

17:22:19 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 VPN Client 1 (NewYork) connect'd in 9 secs
17:22:19 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 Guest WiFi 2.4GHz Client 3 routed via VPN Client 1 (NewYork) i.e 10.88.101.0/24 added for dev br1 table 111
17:22:19 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 VPN Server 1 route 10.8.0.0/24 added for dev tun21 table 111
17:22:20 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 VPN Client Status:
17:22:20 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 Waiting for response from 'http://ipecho.net'
17:22:21 RT-AC68U user.warn (VPN_Client_Switch.sh): 22085 Client 1 connected via ZZZ.ZZZ.ZZZ.147 (VPN WAN I/P XXX.XXX.XXX.XXX) (NewYork)

17:22:30 RT-AC68U user.warn (UP_PPTP-L2TP.sh): 22863 v01.01 VPN (PPTP/L2TP) Client connection manager....[ca.hma.rocks]
17:22:30 RT-AC68U user.warn (UP_PPTP-L2TP.sh): 22863 PPTP VPN Client (ca.hma.rocks) connection request.....
17:22:30 RT-AC68U user.warn (UP_PPTP-L2TP.sh): 22863 PPTP VPN DNS -t nat chain DNSPPP5 created.
17:22:31 RT-AC68U kern.notice rc_service: service 22935:notify_rc restart_vpncall
17:22:31 RT-AC68U user.warn (UP_PPTP-L2TP.sh): 22863 Waiting 60 secs for PPTP VPN Client (ca.hma.rocks) to connect.....may take 20-30 secs
17:22:31 RT-AC68U daemon.err openvpn[22222]: event_wait : Interrupted system call (code=4)
17:22:31 RT-AC68U daemon.notice openvpn[22222]: SIGTERM received, sending exit notification to peer
17:22:33 RT-AC68U daemon.notice openvpn[22222]: vpnrouting.sh tun11 1500 1558 ZZZ.ZZZ.ZZZ.147 255.255.255.0 init
<snip>
17:22:34 RT-AC68U kern.notice rc_service: service 23108:notify_rc updateresolv
17:22:34 RT-AC68U kern.notice rc_service: waitting "restart_vpncall" via  ...
17:22:43 RT-AC68U daemon.info pptp[23299]: Plugin pptp.so loaded.
17:22:43 RT-AC68U daemon.info pptp[23299]: PPTP plugin version 0.8.5 compiled for pppd-2.4.7, linux-2.6.36.4
17:22:43 RT-AC68U daemon.notice pptp[23301]: pppd 2.4.7 started by admin, uid 0
17:22:44 RT-AC68U user.warn custom_script: Running /jffs/scripts/openvpn-event (args: tun11 1500 1558 ZZZ.ZZZ.ZZZ.147 255.255.255.0 init)
17:22:44 RT-AC68U user.warn openvpn-event[23312]: User openvpn-event running
17:22:44 RT-AC68U user.warn openvpn-event[23312]:      Script executing.. for event: vpnclient1-down
17:22:45 RT-AC68U user.warn (vpnclient1-down): 23341 User Processing 'down' (tun11) via ZZZ.ZZZ.ZZZ.147 args = [tun11 1500 1558 ZZZ.ZZZ.ZZZ.147 255.255.255.0 init]
17:22:45 RT-AC68U user.warn (vpnclient1-down): 23341 Deleted cru #GetWANIP_VPN1#
17:22:45 RT-AC68U user.warn (vpnclient1-down): 23341 ***DEBUG VPN Syslog Event Monitor terminating PID=22339 rc=1
17:22:45 RT-AC68U user.warn (vpnclient1-down): 23341 ***DEBUG VPN Syslog Event Monitor terminating PID=22347 rc=1
17:22:45 RT-AC68U user.warn (vpnclient1-down): 23341 VPN Syslog Event Monitor killed.
17:22:45 RT-AC68U user.warn (vpnclient1-down): 23341 User Processing Complete.

17:22:50 RT-AC68U daemon.info pptp[23301]: Using interface ppp5
17:22:50 RT-AC68U daemon.notice pptp[23301]: Connect: ppp5 <--> pptp (104.245.145.19)
17:22:51 RT-AC68U daemon.notice pptp[23301]: CHAP authentication succeeded
17:22:51 RT-AC68U daemon.notice pptp[23301]: MPPE 128-bit stateless compression enabled
17:22:51 RT-AC68U daemon.notice pptp[23301]: local  IP address 100.99.4.13
17:22:51 RT-AC68U daemon.notice pptp[23301]: remote IP address 100.99.0.1
17:22:51 RT-AC68U daemon.notice pptp[23301]: primary   DNS address 100.99.0.1
17:22:51 RT-AC68U daemon.notice pptp[23301]: secondary DNS address 100.99.0.1
17:22:52 RT-AC68U user.warn (UP_PPTP-L2TP.sh): 22863 PPTP VPN Client (ca.hma.rocks) connect'd in 16 secs
17:22:52 RT-AC68U user.warn (UP_PPTP-L2TP.sh): 22863 PPTP VPN Client (ca.hma.rocks) connection request complete.

17:23:05 RT-AC68U user.warn (VPN_Client_Switch.sh): 23606 Request..... [status]
17:23:05 RT-AC68U user.warn (VPN_Client_Switch.sh): 23606 VPN Client Status:
17:23:06 RT-AC68U user.warn (VPN_Client_Switch.sh): 23606 *NO VPN Clients connected*
 
RMerlin said:
I don't think internal name resolution works while in AP mode, only in Router mode.
Click to expand...

But while on 380.67 (still AP Mode), the NTP update worked just fine and I never got those messages.... Something must have changed....
 
Martineau said:
On occasion, I use a script to start a Selective routing PPTP Client

e.g.
https://www.snbforums.com/threads/delay-pptp-vpn-start.38026/#post-313277

whilst there are several concurrent Selective OpenVPN clients ACTIVE.

Under this Beta, when starting the Selective PPTP Client, ALL ACTIVE OpenVPN clients are now immediately terminated seemingly by the command request

Code: 
service restart_vpncall

before the PPTP client is initiated/initialised ?
Click to expand...

I don't remember anything having changed in that part of the code (unless it changed before that with a previous GPL merge), but this sounds like what it should be expected to do.

https://github.com/RMerl/asuswrt-merlin/blob/master/release/src/router/rc/services.c#L8833
 
thelonelycoder said:
This feature has been added in 380.68_alpha, at least this is when I noticed it.
Click to expand...

RTCONFIG_REALIP shouldn't be enabled however, so this might be a bug in the 382 state.js backport that expected it to be enabled even if it isn't. I'll have to dig into it.
 
I have 380.68_alpha2-g4b3b19c installed ATM. Works nicely btw.

Is that alpha essentially the same as this beta? No need to install beta right now?
 
Diamond67 said:
I have 380.68_alpha2-g4b3b19c installed ATM. Works nicely btw.

Is that alpha essentially the same as this beta? No need to install beta right now?
Click to expand...

There were a fairly large amount of changes between alpha 2 and beta 1.

Code: 
merlin@ubuntu-dev:~/asuswrt/release/src-rt/router/httpd$ git log 4b3b19c..380.68-beta1 --oneline
ede9ff8 Updated documentation
bc6ee4f Bumped revision to 380.68 beta 1
7fe966f Updated documentation
b5fd729 webui: remove unused code line from Sysinfo page
faa0e82 webui: Migrate DHCP Lease status to new table API; made fields sortable
51069bb webui: implement IP sort method to tableAPI
1a451ae webui: Enable tableAPI header support, update existing tables to not show a header
0eb7d4a webui: add port field to the remote syslog server parameters
992cf0c webui: re-adjust stats column width, move CSS to a class
dba7b46 webui: call applyRule() on ovpn client state toggling to ensure that changed eas or policy get saved back to nvram
1b66719 openvpn: Undo cipher push in client options state if cipher is rejected
70eb340 openvpn: management: preserve wait_for_push field when asking for user/pass
17e0634 webui: adjust CSS for textarea fields used by OpenVPN and the System Log
396d950 webui: moved logging options from System to System Log page (to be in line with GPL 382)
f03df3f webui: backport Asus's ajax log viewer from GPL 382
cd4eb68 samba: remove use recvfile setting - not supported in stock Samba
 
RMerlin said:
RTCONFIG_REALIP shouldn't be enabled however, so this might be a bug in the 382 state.js backport that expected it to be enabled even if it isn't. I'll have to dig into it.
Click to expand...

RTCONFIG_REALIP was actually added quite some time ago, with GPL 4180. What's new here is the notification, that was added when state.js/menuTree/notification code was backported from 382.

I'll see if I can make it dismiss-able (I know some warnings are, they use a cookie so you only get notified once).
 
Beta_1 is working great for The Griswalds!

Thank You RMerlin for your fantastic work!!
 
Currently having some issues with SmartConnect showing SSID as "open" when WPA2 Personal is set on my RT-AC88U.
Not sure what I broke, but I factory reset after updating to this latest Beta just to be on the safe side.
Now if I keep 2.4 and 5 bands as separate, things are fine and will show as "Secured" on other devices.
Going through SmartConnect and setting them with WPA2 for some reason bugs them both into being listed as "open" and is easily reproduced.

Something I'm missing that I may have set before the restore that's messing me up?
 
WBV said:
The attached picture is self explanatory. The popup balloon indicates erroneous values depending on if 5G-1 is disabled or not.
Click to expand...

This is actually an old bug also present in Asus' stock firmware. Fixed with this commit.
 
Status
Not open for further replies.

Similar threads

RMerlin
  • Locked
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices
2 3 4
Replies
70
Views
12K
RMerlin
RMerlin
RMerlin
  • Locked
Beta Asuswrt-Merlin 386.14 beta is now available
2
Replies
35
Views
9K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
4 5 6
Replies
100
Views
15K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 386.14 is now available for AC models
11 12 13
Replies
240
Views
39K
Tech9
Tech9
RMerlin
Release Asuswrt-Merlin 3004.388.6 is now available
37 38 39
Replies
768
Views
121K
lgkahn
L
Similar threads
Thread starter Title Forum Replies Date
RMerlin Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices Asuswrt-Merlin 70
RMerlin Beta Asuswrt-Merlin 386.14 beta is now available Asuswrt-Merlin 35
RMerlin Beta Asuswrt-Merlin 3004.388.8 beta is now available Asuswrt-Merlin 155
RMerlin Beta Asuswrt-Merlin 3006.102.1 Beta is now available for WIfi 7 devices Asuswrt-Merlin 97
RMerlin Beta Asuswrt-Merlin 3004.388.7 beta is now available Asuswrt-Merlin 123
RMerlin Beta Asuswrt-Merlin 386.13 beta is now available for AC models Asuswrt-Merlin 32
RMerlin Beta Asuswrt-Merlin 3004.388.6 Beta is now available Asuswrt-Merlin 279
M Asuswrt-Merlin with Nextcloud's share folder functionality Asuswrt-Merlin 1
visortgw Asuswrt Merlin 3006.102.3 Alpha1 for GT-BE98 Pro Asuswrt-Merlin 38
A ASUSwrt-Merlin connection to modem as Access Point and/or Bridge Asuswrt-Merlin 6

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 565 (members: 13, guests: 552)
Top