Hi I am new to IPFire.
Coming from opnsense, wanted to know if it is possible to do network IP range blocks (192.168.50.10-192.168.50.20) within the Firewall groups rules. Hosts seems to be a single element. Network seems to only support CIDR?
Looking at the perl code for the Firewall Groups WUI page I could only find port range being defined and used.
I also checked out the network-functions.pl and general-functions.pl code and I could find the validportrange function but there is nothing for validiprange or iprange and also not if I checked just for range, I could only find the validportrange function.
So it looks like the answer is no, IP ranges can not be defined in the Network groups. You need to create individual host entries for each IP address and then you can group them together into a group that covers that IP range.
I suspected as much. To remedy it, I did what is not recommended: I entered the IPs “by hand” by editing IPFire’s configuration files. But a mistake is fatal: you risk damaging IPFire. And this has happened to me before .
And anyway, I always inserted them one by one. Only with copy/paste/notepad I do it faster.
I thank you @cfusco
I didn’t know that. You gave me a very good suggestion.
I will do studies on it, maybe on an IPFire used as a forklift (to try).
With the terminal I am not good, but I will try to succeed anyway.
Until next time .
In addition to Post #8, I feel obliged to inform those who wish to use my way, to also be careful not to change the attributes I have framed in the figure.
If you switch a file from linux to windows, the framed permissions are also reset, and this is also fatal to IPFire files. When I was new to IPFire, I had to reinstall the whole system also because of making the error just mentioned.
Inspired by @cfusco suggestion and observing @anowak rule
I did some tests on my IPFire CU174 test.
I am very satisfied and I must say that it works!!!
However, I noticed that every time I restart IPFire, the iptables rules are reset and have to be reinstated.
I found an unusual method to solve this problem, perhaps even as dangerous as editing IPFire files “by hand”.
I describe it with pictures…