opnsense_firewall_filter not accepting destination port range about terraform-provider-opnsense

[chrisreeves-]

All good @browningluke thanks for your extremely fast response! :) :)

The provider is ssooooo good so thanks for all the hard work you've put into it to date!

[chrisreeves-]

Beautiful, that fixed it!

Thanks again :) :)

[browningluke]

Hey @chrisreeves-, thanks for opening this issue!

Unfortunately this is an oversight of how this resource was implemented. Even though the docs say that this is possible, because the destination.port is expecting an integer, it fails.

I'll get working on a fix, should be out in a few days. However it may result in you having to remove & import the existing rules you've created, since the schema will change slightly. Sorry about that!

[browningluke]

Hey there @chrisreeves- , this should be fixed in v0.9.0. I'll close this issue now, but feel free to re-open it if you still run into issues!

Just for clarity's sake, this is how you define port ranges now:

  destination = {
    net  = "192.168.0.1"
    port = "80-443"
  }

[chrisreeves-]

Hey @browningluke it still seems to be an issue in 0.9.0

I've tried to remove all resources and do a fresh config

[browningluke]

Hey @chrisreeves-, that error actually looks like it's from a quirk of how the os-firewall plugin API works. It considers the protocol attribute case sensitive.

In that code example you showed, try set protocol = "TCP".