ICMP rules should allow selecting multiple types

[feld]

With pf and ipfw it's quite easy to write a single line rule that lets you define the allowed ICMP and ICMP6 types, but with OpnSense you have to create an individual rule for each type. Can this be refactored to allow selecting multiple types just like you can select multiple interfaces?

�

[patient0]

It was discussed a long ago in "Implementing a better ICMP selector in filter rules" but nothing came of it.

[franco]

Just add a GitHub ticket and we can consider it for automation rules.

[patient0]

Just add a GitHub ticket and we can consider it for automation rules.

I'll do that.

What do you refer to by "...consider it for automation rules"?

[franco]

Firewall: Automation: Filter which is already MVC.

[patient0]

Firewall: Automation: Filter which is already MVC.

I see, I have to read up on that. I have no idea what firewall automation is or what they are for.

[franco]

The point is to get the foot in the door and we don't want to change static *.php pages due to maintenance reasons, but who knows what happens once the basic support is in...


Cheers,
Franco

[patient0]

The point is to get the foot in the door and we don't want to change static *.php pages due to maintenance reasons, but who knows what happens once the basic support is in...

I undertand, thanks you Franco, for being as patient as your are :)

[Monviech (Cedrik)]

https://github.com/opnsense/core/issues/8513

As firewall automation is in development right now I added this as issue for it.

[patient0]

As firewall automation is in development right now I added this as issue for it.

Thanks a ton!