# IPS and "apt update" Failure

**URL:** <https://community.ipfire.org/t/ips-and-apt-update-failure/1985>\
**Category:** Firewall Rules\
**Created:** [20 April 2020 17:03 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985 "2020-04-20T17:03:32Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![boguo](https://community.ipfire.org/user_avatar/community.ipfire.org/boguo/32/10726_2.png) [@boguo](https://community.ipfire.org/u/boguo)\
**Post date:** [20 April 2020 17:03 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/1 "2020-04-20T17:03:32Z")

</div>

Hi there,

After I enabled IPS using the “[Emergingthreaths.net](http://Emergingthreaths.net) Community Rules,” simple commands such as “apt update” had failed. Dropbox services might also have impacted…

Understanding the various Internet threats is very intimidating to me, but not turning on IPS makes me vulnerable. Wonder if there are some recipes we can use to know what specific rulesets are more relevant and would not cause any unintended side effects.

Thanks!

Bo

 ![Selection_999(052)](https://community.ipfire.org/uploads/default/original/2X/1/16555971efff0337c806d2a39745ce020ea4e3fb.png)

---

<div class="post-metadata">

**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\
**Post date:** [20 April 2020 17:38 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/2 "2020-04-20T17:38:31Z")

</div>

There may be too many IPS rules turned on. I ran into a similar issue with one IPS Rule:

[https://forum.ipfire.org/viewtopic.php?f=27&t=22848&p=124976&hilit=apt](https://forum.ipfire.org/viewtopic.php?f=27&t=22848&p=124976&hilit=apt)

PS - sorry I don’t have recommendation of what should be on or off

---

<div class="post-metadata">

**Author:** ![username\_not\_availab](https://community.ipfire.org/user_avatar/community.ipfire.org/username_not_availab/32/15885_2.png) [@username\_not\_availab](https://community.ipfire.org/u/username_not_availab)\
**Post date:** [19 February 2025 23:12 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/3 "2025-02-19T23:12:51Z")

</div>

It’s a 5 year old post, but in case someone else has the same issue:  
It is the policy subpacket (as also mentioned [here](https://community.ipfire.org/t/ubuntu-updates-slow-fail-with-ips-on/8371/2))

Click on “customize ruleset” and find the policy rule

 ![Screenshot 2025-02-19 at 23.45.00](https://community.ipfire.org/uploads/default/original/2X/3/328814db5a34f50d77fabf76219e787f5cffbc07.png)

And the use ctrl+F to find the two “APT” entries.

 ![Screenshot 2025-02-19 at 23.45.21](https://community.ipfire.org/uploads/default/original/2X/e/e96f1bdd326f770e15c6cca2a91e0b2a56c980c9.jpeg)

deselect both. Click Apply!

Now “apt update” should work again as expected.  
(Tested in Debian 12 behind IPfire. - Although the IPS is only running on the RED interface and none of the internal ones.)

---

<div class="post-metadata">

**Author:** ![bloater99](https://community.ipfire.org/user_avatar/community.ipfire.org/bloater99/32/15796_2.png) [@bloater99](https://community.ipfire.org/u/bloater99)\
**Post date:** [20 February 2025 13:36 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/4 "2025-02-20T13:36:24Z")

</div>

Is it still the case that changes to individual entries in each rule will be undone during the next ruleset update? If so, then your instructions above will only work temporarily.

---

<div class="post-metadata">

**Author:** ![waynetsun](https://community.ipfire.org/user_avatar/community.ipfire.org/waynetsun/32/16554_2.png) [@waynetsun](https://community.ipfire.org/u/waynetsun)\
**Post date:** [20 February 2025 13:50 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/5 "2025-02-20T13:50:04Z")

</div>

No, that isn‘t the fact. Individual changes remain as set.

---

<div class="post-metadata">

**Author:** ![username\_not\_availab](https://community.ipfire.org/user_avatar/community.ipfire.org/username_not_availab/32/15885_2.png) [@username\_not\_availab](https://community.ipfire.org/u/username_not_availab)\
**Post date:** [20 February 2025 13:50 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/6 "2025-02-20T13:50:48Z")

</div>

Hey Tim,  
interesting comment. I’ll observe it.  
If that would really be the case, we need to find another solution.

One could try to deselect the entire ‘emerging\_policy.rules’ box then, however, chances are that it would then also be reset after an update.

Let’s find out…

---

<div class="post-metadata">

**Author:** ![bloater99](https://community.ipfire.org/user_avatar/community.ipfire.org/bloater99/32/15796_2.png) [@bloater99](https://community.ipfire.org/u/bloater99)\
**Post date:** [20 February 2025 15:21 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/7 "2025-02-20T15:21:20Z")

</div>

This was my experience in the past. You could deslect the entire .rules file and that would stay deselected. But changing an individual rule within the .rules file would get undone at the next ruleset update. Maybe that has changed since my last experience.

---

<div class="post-metadata">

**Author:** ![waynetsun](https://community.ipfire.org/user_avatar/community.ipfire.org/waynetsun/32/16554_2.png) [@waynetsun](https://community.ipfire.org/u/waynetsun)\
**Post date:** [20 February 2025 17:30 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/8 "2025-02-20T17:30:46Z")

</div>

To be more precise: I assumed that it was about switching one of the rules on/off. As far as I know, this remains the same even after updating the rulesets. A change as a new or modified existing rule will probably not actually be retained after an update.

---

<div class="post-metadata">

**Author:** ![username\_not\_availab](https://community.ipfire.org/user_avatar/community.ipfire.org/username_not_availab/32/15885_2.png) [@username\_not\_availab](https://community.ipfire.org/u/username_not_availab)\
**Post date:** [27 February 2025 20:32 UTC](https://community.ipfire.org/t/ips-and-apt-update-failure/1985/9 "2025-02-27T20:32:09Z")

</div>

So, some good news, and some bad news.

**Good news:** It seem the setting persists after rule-updates. So far APT is working fine on all my machines so far.

**Bad News:** Same problem now appeared for background updates of the Arduino IDE. Any download of board-JSON files for example from arcuino.cc throws an error.

So, I’ll search now for the interfering rule… Hint’s are appreciated. If I find something I’ll share it here.

EDIT: also [reported here](https://community.ipfire.org/t/dns-queries-for-arduino-cc-are-dropped-by-ips/6565/41?page=3) - it seems to be DNS related.  
Which I can confirm already: `ping arduino.cc` fails with a “name resolution failed”. IDS disabled, it immediately works.

Though, I am not really sure why the other thread is considered as _“solved”_.
