You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Missing spoofmac field in the XML configuration To Reproduce
Steps to reproduce the behavior:
Create new vlan
Assign new interface with the newly created LAN
Export the XML configuration
See the differences between newly created and original interfaces.
Expected behavior
Unlike other interfaces, the empty field is missing from the interface configuration of newly created interface. This causes, that the newly created interface is handled incorrectly and cannot load rules attached to it.
When opening in GUI and clicking Save on the interface editation page, the empty field is added and rules are correctly loaded.
Sending empty value for spoofmac attribute is not possible, due to mac validation on the API endpoint.
Thanks for bringing this up. pfSense usually treats missing values and empty values the same therefor this usually wouldn't cause any issues but of course that's not always the case; but I haven't looked deeper into the code to verify. Regardless, you are correct it would be best to default that value to an empty string if none was specified and allow interface updates to revert to the default (empty) value. I'll get this fixed, I have a patch planned for release this weekend so I'll have this included.
Describe the bug
Missing spoofmac field in the XML configuration
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Unlike other interfaces, the empty field is missing from the interface configuration of newly created interface. This causes, that the newly created interface is handled incorrectly and cannot load rules attached to it.
When opening in GUI and clicking Save on the interface editation page, the empty field is added and rules are correctly loaded.
Sending empty value for spoofmac attribute is not possible, due to mac validation on the API endpoint.
Screenshots or Response
exported config.xml
OPT14 is created manually, OPT15 via API
pfSense Version & Package Version:
Affected Endpoints:
Additional context
Is this issue fixed on a later versions of the API? Maybe it is already solved with newer release, IDK.
The text was updated successfully, but these errors were encountered: