I see.  Chrony is getting blocked.

All this setup is temporary because soon it will be going through a WireGuard 
tunnel.




‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, August 5, 2020 10:51 AM, Tom Eastep <teas...@shorewall.net> wrote:

> On 8/5/20 10:30 AM, colony.three--- via Shorewall-users wrote:
>
> > HAZZAH, like magic the Master does it again!
> > This is regular Shorewall, compiling rules in its own machine, all in 
> > /etc/shorewall.
> > BUT, AUTOMAKE=Yes. As soon as I set it to No, everything started TWERKING!
> > Thank you again Tom. I never would have found this in a million years.
> > For others, beware: Automake=Yes is the default. Might should be No if you 
> > consider port-forwarding.
>
> The real problem is the time/date issue on that system. When the current
> time says 2018 and the firewall script was created in 2020, AUTOMAKE=Yes
> is going to prevent the script from getting re-generated for the next
> two years!!
>
> -Tom
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Tom Eastep \ Q: What do you get when you cross a mobster
> Shoreline, \ with an international standard?
> Washington, USA \ A: Someone who makes you an offer you
> http://shorewall.org \ can't understand
> \________________________________________
>
> Shorewall-users mailing list
> Shorewall-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shorewall-users




_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to