"Drop all Microsoft ports" active after update

Networking
1

Hello!

After the last update ( Core-Update 182) under “Firewall Options” the point “Drop all Microsoft ports” was activated again…
As standard I have it turned “off” because I need SMB for saving my pictures from my smartphone to a NAS thats in Green Network…

This was meanwhile the second time it was activated again after an update and this time I was not searching very long for the problem… but:
Is there a possibility to not automatically change the setting here at every update to “ON”?
Would be great if the settings would stay the way they were set before the update :wink:

Thanks in advance
Tobias

2

Which zone is the smartphone in? I presume that it must be in the blue zone as that is where the drop microsoft ports applies to. So presumably you are trying to go from the blue zone to the green zone.

You are the first person to flag this up.

I have the drop all microsoft ports “on” as I don’t use any microsoft software that needs to access from one zone to anotherzone in IPFire.

In the next couple of days I will look at setting up a CU181 vm on my testbed and carry out an update to CU182 and see if I can reproduce what you are seeing.

If I can reproduce it then you should definitely raise a bug on it.
If I can’t reproduce it, it doesn’t mean a bug should not be raised but it will be more difficult to investigate and fix if we can’t have it occurring, install a fix and confirm that it no longer occurs.

Let’s see first if I can reproduce it or not.

2 Likes
3

I managed to get some time on this, this evening.

I created a vm and installed CU181.
The default setting for drop microsoft is “off”

Screenshot_2024-01-07_20-30-51
Screenshot_2024-01-07_20-30-51786×531 60.5 KB

Then I ran the update from CU181 to CU182.
Before rebooting it was
Screenshot_2024-01-07_20-35-33
Screenshot_2024-01-07_20-35-33979×586 68 KB

After reboot is was
Screenshot_2024-01-07_20-37-53
Screenshot_2024-01-07_20-37-53975×587 68.1 KB

So the default value of "off stayed without changing to “on”

I then created a new vm with CU181 with the default value of “off” for the drop microsoft, selected “on” and pressed save and then rebooted.

Screenshot_2024-01-07_20-50-47
Screenshot_2024-01-07_20-50-47886×572 66.2 KB

Then I changed the selection from “on” to “off” and pressed save.
The message that a reboot is needed for some changes was shown.
Screenshot_2024-01-07_20-51-17
Screenshot_2024-01-07_20-51-17967×570 61.7 KB

Then, without rebooting, I ran the update from CU181 to CU182 and before rebooting post update it still showed the setting as “off”

Screenshot_2024-01-07_20-51-50
Screenshot_2024-01-07_20-51-50980×598 68.6 KB

Then I did the reboot after the CU181 to CU182 update and it still showed “off” for the drop microsoft settings.

Screenshot_2024-01-07_20-53-20
Screenshot_2024-01-07_20-53-20990×588 68.3 KB

So I have not been able to reproduce the problem you have experienced, either by a normal update process from CU181 to CU182 or by a missing reboot of the firewall settings.

In all cases the value that was set on the WUI page stayed there after the update and also after the reboot.

You mentioned that you experienced this now with an update from CU181 to CU182 but that you have had it happen once before after a Core Update. What CU did you go from and to which CU did you upgrade in the previous occurrence?

4 Likes
4

Long time ago that I made that update… but in the last updates the problem was gone!

Thanks for your help!