Aegis Aegis (simple yet effective protection)

[D3FenD3r]

done update ............. but always the old one version 1.4.6

 

[D3FenD3r]

 

[Jauger]

Close out your browser and reopen...should show latest

 

[D3FenD3r]

done several times .... it always remains 1.4.6

 

[R. Gerrits]

same here, upgrading via web didn't work. Afterwards it still said version 1.4.6
Also confirmed via commandline.

Upgrade via commandline did work though (aegis unset, aegis upgrade, aegis up)

 

[HELLO_wORLD]

Thanks all for this feedback.

Found the problem. Web update sees"up" in "upgrade" and thinks the command asked is up

Will fix that soon, abut be aware that once it will be ready, since actual version has the bug, upgrade from command line will be necessary, but upgrades after that will be ok again.

 

[HELLO_wORLD]

1.4.9

Fix upgrade from web (will work when upgrading to next version)

PLEASE, UPGRADE THIS WAY:
From command line:

aegis upgrade

 

[Jauger]

Thanks Hello_World for your hard work. Web Ui logs are working correctly, all outgoing devices are showing. Merry Christmas to you and your family..................

 

[HELLO_wORLD]

1.5.0

Web Companion: Fixed minor bug where some log lines were not reported in the web interface.
Aegis Core: Changed the show log algorithm to one similar used in Web Companion log display (based on awk, a lot faster and more efficient than shell based) + some optimizations and code cleaning.

 

[NetBytes]

1.5.0

Web Companion: Fixed minor bug where some log lines were not reported in the web interface.
Aegis Core: Changed the show log algorithm to one similar used in Web Companion log display (based on awk, a lot faster and more efficient than shell based) + some optimizations and code cleaning.

Up and running, thank you!

 

[D3FenD3r]

aegis updated ... only the log stopped at 2 hours ago
it is 9 pm but the log shows 19 and does NOT go on.
i did REFRESH and SHIELD UP but nothing.

after several reboots, the log has updated and runs smoothly

 

[HELLO_wORLD]

aegis updated ... only the log stopped at 2 hours ago
it is 9 pm but the log shows 19 and does NOT go on.
i did REFRESH and SHIELD UP but nothing.

View attachment 28815

after several reboots, the log has updated and runs smoothly

Ok, to keep an eye on...

aegis status is saying is logging is enabled or disabled (or status in Web Page)

To stop logging, the important command is
aegis log -disable or aegis up -log-disable
Or from Web Companion

To enable logging:
aegis log -enable or aegis up -log-enable
Or from Web Companion

To stop aegis, then restart firewall, aegis and enable logging:
aegis down; aegis up -log-enable -net-wall

 

[D3FenD3r]

I reopen aegis and the log is still stopped at 3 hours ago

 

[HELLO_wORLD]

Ok @D3FenD3r , it appears that for some reason, the log daemon is crashing. Probably a difference between R7800 and R9000 (I can only test on R7800).
I will revert the daemon to how it was on 1.4.9, and it will be fine (provided you did not have this problem with 1.4.9, right?)

 

[HELLO_wORLD]

1.5.1

Reverted log daemon.

For @D3FenD3r (or others who experienced this bug): aegis down then aegis up with logging.


Only difference is $(wc -l some file|cut -d' ' -f1) that was in 1.5.0 $(wc -l <some file)

Not sure why it would not behave the same. Result is same on R7800 (faster because not calling cut).

 

[D3FenD3r]

updated .... the log started immediately, I wait and see if everything works

 

[HELLO_wORLD]

1.5.2

New option in command line:

aegis log -live

To display the log real-time (like in the web log tab).
To exit, use CTRL-C

Also, tried something else in the log daemon; @D3FenD3r tell me if the bug is back in this version (and please confirm it was gone with 1.5.1), if so, I will revert again and just not touch it further.

 

[D3FenD3r]

updated, log started, after a while it froze.
I enter the router and "aegis log -live" shows some old lines and nothing moves.

if you want me to do something

 

[D3FenD3r]

put this on and off again

aegis down; aegis up -log-enable -net-wall
and aegis log -live works too


when this happens, the log appears to be blocked

 

[HELLO_wORLD]

updated, log started, after a while it froze.
I enter the router and "aegis log -live" shows some old lines and nothing moves.

if you want me to do something

Thank you @D3FenD3r
What happens is that for you, the aegis log daemon who is feeding the log file is crashing when it uses the command wc with an input like <file, but it seems fine using it like wc file.
I am not explaining now and here the technicalities.
Bed time for me.

Tomorrow morning, I will simply revert to the "wc file | cut" way instead of "wc <file" one and it will be working again.

I might ask you after that to run some test code, just to understand why the < version is crashing on your setup.