1
Zenarmor (Sensei) / Re: 1.17 update caused eastpect crash
« on: May 13, 2024, 08:40:37 pm »
Editing eastpect.cfg to disable CTI seems to have resolved the issue for me.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Zenarmor (Sensei) / Re: 1.17 update caused eastpect crash
« on: May 05, 2024, 04:40:14 pm »
Well, it seems this may have been only a partial solution. After monitoring it yesterday, I am back to getting crashes, but only once every two hours or so.
I'm now trying the emulated driver and, if that fails, will spin up Unbound on the firewall for local resolution.
I'm now trying the emulated driver and, if that fails, will spin up Unbound on the firewall for local resolution.
3
Zenarmor (Sensei) / Re: 1.17 update caused eastpect crash
« on: May 04, 2024, 05:20:41 pm »
Hey just4fun,
Wanted to thank you for pointing me in the right direction here. I also experienced repeated crashing after updating to 1.17.
I have an internal Unbound server and when looking at the queries from the firewall, I saw that all *.zenarmor.com domains asked for A and AAAA records except for cti.zenarmor.com. This only asked for AAAA records.
Since I did not have IPv6 enabled at the time, it was failing. After enabling IPv6 on my WAN interface to allow the firewall to respond via v6, ZenArmor has been up and running without a crash for a few hours. I am also running the native Netmap driver.
If you dig/nslookup cti.zenarmor.com, there are absolutely A records, so maybe this was an oversight in the 1.17 code to not ask for them. I'm curious if this is the same for you.
turbo_lag
Wanted to thank you for pointing me in the right direction here. I also experienced repeated crashing after updating to 1.17.
I have an internal Unbound server and when looking at the queries from the firewall, I saw that all *.zenarmor.com domains asked for A and AAAA records except for cti.zenarmor.com. This only asked for AAAA records.
Since I did not have IPv6 enabled at the time, it was failing. After enabling IPv6 on my WAN interface to allow the firewall to respond via v6, ZenArmor has been up and running without a crash for a few hours. I am also running the native Netmap driver.
If you dig/nslookup cti.zenarmor.com, there are absolutely A records, so maybe this was an oversight in the 1.17 code to not ask for them. I'm curious if this is the same for you.
turbo_lag
Pages: [1]