What's new

AB-Solution 2.0 is out! (v2.0.1)

  • 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!

If I understand it right, the call to the post-mount script has the parameter of the partition just mounted. So running
Code:
./post-mount
is not the same as running
Code:
./post-mount /tmp/mnt/sda1
The former will form the link with the -d version, but will try to form it when each partition is mounted, even if it is already formed, and even if entware isn't on it, while the $1 version will only try to form it when the right partition is mounted, and in a reboot. Also, a partition label helps to see it is the "right" partition.

Ok but I can't get it working with the $1 version, surely I do something wrong.
 
Ok but I can't get it working with the $1 version, surely I do something wrong.
Are you rebooting and Entware is not coming up?

Or are you in terminal running /jffs/scripts/post-mount start /tmp/mnt/sda1?
 
Version 2.0.1 incremental update is released. See post#1 for more info.
v2.0 users may update by selecting the [cu] option in the Menu.

Changelog:
New: Green "IPv6" is shown in header when service is enabled
Fix: Removed falsely placed error message when running [22]
Fix: Changed IPv4 validation when selecting custom block IP. This caused a failed app restart
Fix: toggle weekly stats to [on] was not set correctly
General: Changed wording of post-mount and dnsmasq.postconf "Do not edit" warning
General: Code maintenance
 
Last edited:
Great! Thank You

s.2016-09-07 12.01.08.jpg
 
does 2.0 requires to change the asus web interface to https only and different port? to be able to use pixelserv
 
does 2.0 requires to change the asus web interface to https only and different port? to be able to use pixelserv
That's up to you. AB-Solution provides the blocklist and directs them wherever pixelserv-tls listens, pixelserv does the rest
 
I can't install version 2, it fails when it tries to check for internet connection, specifically this line:
Code:
echo -e "GET http://google.com HTTP/1.0\n" | nc google.com 80
Fails with a segmentation fault. Has this been tested with ARM models and specifically the RT-AC56U? The nc command is completely non functional.

EDIT: managed to proceed by modifying the script to use the entware version of netcat. The busybox one is broken on the RT-AC56U.
 
Last edited:
I can't install version 2, it fails when it tries to check for internet connection, specifically this line:
Code:
echo -e "GET http://google.com HTTP/1.0\n" | nc google.com 80
Fails with a segmentation fault. Has this been tested with ARM models and specifically the RT-AC56U? The nc command is completely non functional.

EDIT: managed to proceed by modifying the script to use the entware version of netcat. The busybox one is broken on the RT-AC56U.
Thanks for sharing. I tested this on my RT-AC87U, also ARM based.
I need to build in a fallback anyway if google is blocked or is not answering for some reason.
I will try to get rid of the 'nc' as well if possible.
And a timeout would be nice too.
 
My ads are not blocking on my ac3100. I am new to this script. Do I need to install pixelserv?
testing on this site, no ads are blocked.
http://www.worldjournal.com/

Edit:
It seems I have to turn off dns based filtering. Working Now.
I was using a dns adblocking service to block each of my individual device. Now that I have it on my router, don't need it anymore.
 
Last edited:
I see the same thing as in the screenshot in message #25. When first run, ab-solution shows a message that an upgrade is available from 2.0 to 2.0.1, even though it has already been upgraded, because the .cfg file remains at "2.0". Perhaps because line 1783 is commented out? Trivial, of course.
 
Last edited:
I see the same thing as in the screenshot in message #25. When first run, ab-solution shows a message that an upgrade is available from 2.0 to 2.0.1, even though it has already been upgraded. Something about the initialization for messages_check()? Trivial, of course.
No, that message is deliberately intended.

AB-Solution version numbers are ordered like so:
major.minor.maintenance
2.0.1 is therefore a maintenance update from 2.0.

With the update option [cu], the latest version of ab-solution.sh is being downloaded and replaces the previous version.
Then the app is restarted and it found a version change to upgrade to. Neat huh?
Everything works as intended :)

So, you just updated to the latest version. But even if it is a maintenance update, I deliberately triggered the upgrade function because the system had a few minor changes that need a check.

This is the best way for me to ensure you have a working installation.

Would anyone have a problem with that?
 
Trivial, of course.
Of couse it is. But if that's the only complaint you have, then I am pretty happy and satisfied with my work on AB-Solution :D
And since it's so trivial, the next version will do the check without the need of the precious users keyboard input.
 
No, that message is deliberately intended.

AB-Solution version numbers are ordered like so:
major.minor.maintenance
2.0.1 is therefore a maintenance update from 2.0.

With the update option [cu], the latest version of ab-solution.sh is being downloaded and replaces the previous version.
Then the app is restarted and it found a version change to upgrade to. Neat huh?
Everything works as intended :)

So, you just updated to the latest version. But even if it is a maintenance update, I deliberately triggered the upgrade function because the system had a few minor changes that need a check.

This is the best way for me to ensure you have a working installation.

Would anyone have a problem with that?
I'm being a little dense. I upgraded to 2.0.1 a few days ago. Each time I run ab-solution, it tells me my installation needs upgrading from 2.0 to 2.0.1, I think because the .cfg file still says "2.0". Shouldn't the message only appear if there is something newer than 2.0.1?
 
I'm being a little dense. I upgraded to 2.0.1 a few days ago. Each time I run ab-solution, it tells me my installation needs upgrading from 2.0 to 2.0.1, I think because the .cfg file still says "2.0". Shouldn't the message only appear if there is something newer than 2.0.1?
You have updated the script version from 2.0 to 2.0.1.
That is what [cu] does for you so conveniently.
The underlying system still needs upgrading to 2.0.1.

Is that so hard to understand?
 
Last edited:

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!
Top