[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[fink.nottle]

@john9527
I managed to solve most of my bufferbloat woes by using one AC68U as a router running lede, and another one running your fork as an access point. Everything performs pretty well now. One minor issue that I've noticed is that if I enable ipv6 on the router, the wifi clients connected to the AP don't work very well (with ipv6 at least). I have a couple of anecdotal points regarding that. http://speedtestbeta.xfinity.com/ does an ipv6 test, which fails if the client is connected to the AP. It works if it is connected to the router directly with a cable. The fast.com android app also behaves erratically. I was looking around on the internet regarding similar issues, and came across some posts like this one: https://blog.hqcodeshop.fi/archives/100-IPv6-through-WLAN-access-point.html. Something to do with accept_ra and forwarding perhaps ? I must note that basic ipv6 test on http://ipv6-test.com/ works. So I'm guessing that it is some sort of configuration issue ?

 

[punchsuckr]

I do have dnscrypt enabled.



Strict enforcement is disabled, no dns filter on the system, no dns servers on the lan page as well. The dnscrypt servers I am using are 'dnscrypt.eu with dnssec' servers (after i clarified another issue with you a few days back). I got no other symptoms other than a few failed queries in chrome which would then quickly resolve.

anything?

 

[punchsuckr]

Also, it takes over 4 minutes for wan to come up after a reboot or if i reboot the modem...this really didn't happen with v20xx , the wan light comes on as usual after after a really short time.
All this is with dnscrypt off (with failing dns queries and the dnsbench result I switched it off), all settings which they were in v20.

EDIT: Also found this entry in the log which I think haven't seen before i guess...

dnsmasq[572]: Maximum number of concurrent DNS queries reached (max: 150)

this is after I launched dnsbench on a pc.

 

[punchsuckr]

It's quite weird... after I posted here I again upgraded to e4 and enabled dnscrypt (same dnscrypt.eu with dnssec servers) and now dnsbench works happily. The long time to bring wan up remains though.. around 3:50 after a reboot. There used to be no delay whatsoever with v20.

EDIT: Will a reset to factory defaults help?

 

[octopus]

Replace the call to the example Send_mail procedure
Send_Mail $VPN_ID $VPN_WANIP
with a call to your /jffs/configs???/sendmail.sh script and pass the appropriate VPN WAN IP as an additional argument, or simply copy your sendmail.sh code inline.

@Martineau
Is it a way to modify so I can use it with: vpnclient1-route-up and vpnclient1-down?

 

[Martineau]

@Martineau
Is it a way to modify so I can use it with: vpnclient1-route-up and vpnclient1-down?

Err Yes

No 100% clear on what the question is...you can call your send mail script /jffs/configs???/sendmail.sh from vpnclient-route-up/vpnclient1-down.

 

[octopus]

Okay sorry to not be clear....
I tested and set: vpn_client1_state to (0) and run script, then it's timed out 60 sek.
I want to send mail when tun11 is going down/up. (mail is not sending on interface tun11)

I'm using: nvram get vpn_script_state from openvpn-event to se if
vpnclient1-route-up or vpnclient1-down is called.

 

[Martineau]

Okay sorry to not be clear....
I tested and set: vpn_client1_state to (0) and run script, then it's timed out 60 sek.
I want to send mail when tun11 is going down/up. (mail is not sending on interface tun11)

I'm using: nvram get vpn_script_state from openvpn-event to se if
vpnclient1-route-up or vpnclient1-down is called.

If script vpnclient1-down is running then vpn_client1_state may already be "0" but to be sure you can use the same technique I described in

http://www.snbforums.com/threads/fo...lts-releases-v22e4.18914/page-260#post-302300

e.g.

vpnclient1-down

#!#bin/sh

Say(){
   logger -st "($(basename $0))" $$ $@
}

Say "Requesting Is_VPN_really_DOWN.sh script for" $dev
/jffs/scripts/Is_VPN_really_DOWN.sh 1 &

e.g. Is_VPN_really_DOWN.sh

VPN_ID=$1
DISCONNECTED=0
if [ $(Check_VPNState $VPN_ID $DISCONNECTED ) = $DISCONNECTED ]; then
   send_mail etc.
fi

 

[punchsuckr]

It's quite weird... after I posted here I again upgraded to e4 and enabled dnscrypt (same dnscrypt.eu with dnssec servers) and now dnsbench works happily. The long time to bring wan up remains though.. around 3:50 after a reboot. There used to be no delay whatsoever with v20.

EDIT: Will a reset to factory defaults help?

Reset and mixed results, i believe the late connection to wan is an isp issue since now sometimes it will connect quickly, other times not.

 

[john9527]

Reset and mixed results, i believe the late connection to wan is an isp issue since now sometimes it will connect quickly, other times not.

Try changing your NTP servers one at a time.....the slow boot can be caused by a flakey time server.

EDIT: Also found this entry in the log which I think haven't seen before i guess...

dnsmasq[572]: Maximum number of concurrent DNS queries reached (max: 150)

this is after I launched dnsbench on a pc.

This is normal when running dnsbench (you do know all the reasons why it can be a less than useful tool, right?). It floods the interface with DNS requests, almost like malware.

 

[john9527]

If script vpnclient1-down is running then vpn_client1_state will most probably already be "0" so there is no point checking for a value of "2"

e.g. vpnclient1-down

DISCONNECTED=0
if [ $(Check_VPNState $VPN_ID $DISCONNECTED ) = $DISCONNECTED ]; then
   send_mail etc.
fi

From my testing, the final state isn't updated (either up or down) until the script exits. So either
- make separate script (send_mail_up, send mail_down) and don't include the state check
- start the send_mail script including a '&' at the end of the call, so it runs in the background

 

[octopus]

If script vpnclient1-down is running then vpn_client1_state will most probably already be "0" so there is no point checking for a value of "2"
e.g. vpnclient1-down

DISCONNECTED=0
if [ $(Check_VPNState $VPN_ID $DISCONNECTED ) = $DISCONNECTED ]; then
   send_mail etc.
fi

@Martineau Hmm I tried it but it didn't work. Testing again. Thanks...........

From my testing, the final state isn't updated (either up or down) until the script exits. So either
- make separate script (send_mail_up, send mail_down) and don't include the state check
- start the send_mail script including a '&' at the end of the call, so it runs in the background

@john9527 I got it. Thanks..............
I use vpn_script_state check only to know which as have sent mail.

 

[Martineau]

@Martineau Hmm I tried it but it didn't work. Testing again. Thanks...........
.

I updated OP
http://www.snbforums.com/threads/fo...lts-releases-v22e4.18914/page-262#post-303091

with what I really meant!

 

[punchsuckr]

John I keep seeing this line in the log frequently, is this some bug or what?

watchdog: restart httpd, error detected or process not responding (52)

 

[john9527]

John I keep seeing this line in the log frequently, is this some bug or what?

watchdog: restart httpd, error detected or process not responding (52)

No, not a bug.....but an indicator of a potential problem. In the fork, I modified the http/https watchdog so that it not only checks that the httpd process is running, it also tries to talk to it via curl. It's been there unchanged for quite some time. I just checked on my N66, and it's working correctly.

The (52) is the curl error code, which says it successfully sent the command, but httpd never responded in 10 sec. The only time I have ever seen this error, is when I ran some scenarios purposely trying to log on from two systems simultaneously, although it could be a hang for a a different, unknown reason.

So....
- are you accessing the router from more than one client at a time?
- do you see any strange login attempts in the syslog? I hate to say it, but I can speculate it may be a result of someone trying to hack your system if you have web access enabled.

 

[punchsuckr]

No, not a bug.....but an indicator of a potential problem. In the fork, I modified the http/https watchdog so that it not only checks that the httpd process is running, it also tries to talk to it via curl. It's been there unchanged for quite some time. I just checked on my N66, and it's working correctly.

The (52) is the curl error code, which says it successfully sent the command, but httpd never responded in 10 sec. The only time I have ever seen this error, is when I ran some scenarios purposely trying to log on from two systems simultaneously, although it could be a hang for a a different, unknown reason.

So....
- are you accessing the router from more than one client at a time?
- do you see any strange login attempts in the syslog? I hate to say it, but I can speculate it may be a result of someone trying to hack your system if you have web access enabled.

Nope accessing it only via one pc, even got a administration access limit set to 3 clients only and those clients are all off except one from which i am accessing the admin page.. and never enabled web access for any service (kind of a security freak, me).

Some additional details:
openvpn-disabled
dnscrypt enabled (working properly)
media server disabled
https admin page disabled (wan access disabled)
telnet disabled
ssh enabled (wan access disabled)
admin passwd set to lastpass generated random pass so is the wifi passkey
local sntp server enabled
Allow only specified IP address for administration page set to 3 clients with those 3 away from the normal dhcp range

Everything else default..

After a reboot, i see the above message some 5 times at a 30sec interval and then after 1 sec this one:

watchdog: aborting httpd response checks - unrecoverable error

Can I do something about it? I already reset the router today..

EDIT: and no strange login attempts...

 

[john9527]

Can I do something about it? I already reset the router today..

Tries 5X then gives up.....that's how it's supposed to work.

Try adding the router address to the 'Specified IP address' list.

 

[raggedhobo]

Hello all!

I happened to find myself upon this forum as I am looking to improve my RT-AC66U's performance and everything pointed here. I'm on the current official firmware, so in order to not brick I just wanted to clarify what I need to do.

1. Download and Install the ASUS recovery tool
2. Download this firmware
3. Connect router to computer in recovery mode
5. Run the utility tool, selecting this firmware
6. I'm done?

If this isn't the spot for this I'm sincerely sorry. If it is, thanks for the help!

 

[john9527]

Hello all!

I happened to find myself upon this forum as I am looking to improve my RT-AC66U's performance and everything pointed here. I'm on the current official firmware, so in order to not brick I just wanted to clarify what I need to do.

1. Download and Install the ASUS recovery tool
2. Download this firmware
3. Connect router to computer in recovery mode
5. Run the utility tool, selecting this firmware
6. I'm done?

If this isn't the spot for this I'm sincerely sorry. If it is, thanks for the help!

6. After the router reboots, perform a reset to factory defaults
7. Manually reconfigure the router (don't try and load a backup saved from the previous level)

Welcome to the forum!

 

[punchsuckr]

Tries 5X then gives up.....that's how it's supposed to work.

Try adding the router address to the 'Specified IP address' list.

Holy shirt that worked Thanks!!