-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bridge and IGMP setting #106
Comments
Second error |
Wow, this menu appears after enabling IGMP, I did not see it when implementing a bridge interface and it will need to be added. |
Yep, here's the different between the API objects for two bridges - one has IGMP snooping enabled, the other doesn't: [
{
".id": "*2",
"actual-mtu": "1500",
"ageing-time": "5m",
"arp": "enabled",
"arp-timeout": "auto",
"auto-mac": "true",
"dhcp-snooping": "false",
"disabled": "false",
"fast-forward": "true",
"forward-delay": "15s",
"igmp-snooping": "false",
"l2mtu": "65535",
"mac-address": "FE:F3:52:67:CA:3A",
"max-message-age": "20s",
"mtu": "auto",
"name": "bridge",
"priority": "0x8000",
"protocol-mode": "rstp",
"running": "true",
"transmit-hold-count": "6",
"vlan-filtering": "false"
},
{
".id": "*4",
"actual-mtu": "1500",
"ageing-time": "5m",
"arp": "enabled",
"arp-timeout": "auto",
"auto-mac": "true",
"dhcp-snooping": "false",
"disabled": "false",
"fast-forward": "false",
"forward-delay": "15s",
"igmp-snooping": "true",
"igmp-version": "2",
"l2mtu": "65535",
"last-member-interval": "1s",
"last-member-query-count": "2",
"mac-address": "7E:5F:A1:0E:25:56",
"max-message-age": "20s",
"membership-interval": "4m20s",
"mld-version": "1",
"mtu": "auto",
"multicast-querier": "false",
"multicast-router": "temporary-query",
"name": "bridge-lan",
"priority": "0x8000",
"protocol-mode": "rstp",
"querier-interval": "4m15s",
"query-interval": "2m5s",
"query-response-interval": "10s",
"running": "true",
"startup-query-count": "2",
"startup-query-interval": "31s250ms",
"transmit-hold-count": "6",
"vlan-filtering": "false"
}
] I just tested setting one of the extra fields on a bridge that doesn't have IGMP snooping enabled, and it seems the API ignores it:
The only bad thing about this is if someone sets one of these igmp fields without actually enabling igmp snooping, Terraform will think it was successful and update the state. Additionally, I don't know of a way to enable/disable fields based on the value of another. |
Wait a bit, I'm preparing patches for this. |
Yes, this is predictable behavior, but I don't see a problem with it yet (storing dummy properties in the TF state file).
|
@durandguru Please check the fixes v1.0.7 |
🎉 This issue has been resolved in version 1.0.7 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
in 1.0.8 │ Warning: Field not found |
Hmm, I thought I found all the fields according to the documentation 😕. Please show your bridge section from the TF file. |
fix: #106 Added "multicast_router" field.
resource "routeros_bridge" "bridge" { I just use the default values from mikrotik for igmp. |
🎉 This issue has been resolved in version 1.0.9 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
@vaerh tested 1.0.9 and got this error: │ Error: InternalValidate |
fix(#106): Fix internal validation (for release).
🎉 This issue has been resolved in version 1.0.11 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
I'm sorry, I've corrected the error. |
Almost all the errors are gone in 1.0.11. Still got this one on routeros_bridge_port |
This is one of the 8 fields for monitoring the current state of the bridge.
This is one of the 8 fields for monitoring the current state of the bridge.
🎉 This issue has been resolved in version 1.0.12 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
These messages are gone ;-) |
This is one of the 8 fields for monitoring the current state of the bridge.
Describe the bug
I enable IGMP on the bridge. After apply I get an error about MikrotikResourceDataToTerraform
To Reproduce
resource "routeros_bridge" "bridge" {
name = "bridge"
ingress_filtering = true
protocol_mode = "rstp"
priority = "0x3000"
igmp_snooping = true
vlan_filtering = true
}
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Error
│ Warning: Field not found
│
│ with routeros_bridge.bridge,
│ on ports.tf line 1, in resource "routeros_bridge" "bridge":
│ 1: resource "routeros_bridge" "bridge" {
│
│ [MikrotikResourceDataToTerraform] The field was lost during the Schema development: igmp_version <<<= 2
The text was updated successfully, but these errors were encountered: