unfortunately I can not reproduce it. In my tests, I get the rule even when interface "tun0+" does not have an ip address. Could you send your .fwb file to me or prepare an example file that demonstrates the problem ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
actually, I have been testing with the latest v5.0.1. I wonder if this is something that has been fixed since 4.2.2. You can download latest package from our nightly builds site or from our repository, see here:
you seem to be building a cluster configuration but you did not map cluster interface objects to interfaces of the member firewalls. Once you do that, rules get generated.
which part of the rule you use this interface in ? Please provide an example
Without IP address
With an IP address
Surely, I've published 2 screens captures.
Many Thanks for your help and your so useful work !
unfortunately I can not reproduce it. In my tests, I get the rule even when interface "tun0+" does not have an ip address. Could you send your .fwb file to me or prepare an example file that demonstrates the problem ?
actually, I have been testing with the latest v5.0.1. I wonder if this is something that has been fixed since 4.2.2. You can download latest package from our nightly builds site or from our repository, see here:
http://www.fwbuilder.org/4.0/docs/firewall_builder_packages.html
example config file
You can find a very simple example file ("debug3.fwl.gz") where the bug appears.
Sorry, I could not even test the new version...
thank you for the example file
you seem to be building a cluster configuration but you did not map cluster interface objects to interfaces of the member firewalls. Once you do that, rules get generated.
Users Guide shows how to do this:
http://www.fwbuilder.org/4.0/docs/users_guide5/clusters.html