wanting to modify lo and unable to ignore #135
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
more info
question
TBD
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
liske/ifstate#135
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Upgraded to 2.1 and seeing following behavior. After applying settings ifstate continues to want to modify "lo":
Adding ^lo$ to ignore ifname does not help:
Explicitely configuring lo also does not work:
interfaces: lo: addresses: - address: ::1/128 scope: hostleads to the same behaviour. There should be a way to apply settings without diff being shown, either by ignoring lo or explicitely configuring it to match system.
What kernel/distri are you using? I'm not able to reproduce this behavior, yet 🤔
The ignore won't work since ifstate implicitly adds a
lointerface definition in every namespace it handles by using these default values:_default_lo_link = {'addresses': ['127.0.0.1/8',{'address': '::1/128','proto': 1, # kernel_lo}],'link': {'kind': 'physical','state': 'up','mtu': 65536,}}Could you please run
ifstatecli shelland post the output ofpprint(ipr.get_addr(index=1))? Thanks!Thank you for the quick response! Here are the details:
Thanks, the
IFA_PROTOis missing for::1. So ifstate removes the IP and adds it again with the proto with no avail.I observed a simular issue with
IFA_PROTOon kernel generated IPv6 mod. EUI64 LLA (while it works on several other). So I'm going to just drop the proto from the_default_lo_linkfor now as it is not reliable.