Bugzilla – Full Text Bug Listing |
Summary: | firewall: validate interface name when attaching it to zone | ||
---|---|---|---|
Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | macias - <bluedzins> |
Component: | YaST2 | Assignee: | Michal Filka <mfilka> |
Status: | REOPENED --- | QA Contact: | Jiri Srain <jsrain> |
Severity: | Enhancement | ||
Priority: | P5 - None | CC: | artkoz78, cookie170, locilka |
Version: | Current | ||
Target Milestone: | --- | ||
Hardware: | x86-64 | ||
OS: | Other | ||
Whiteboard: | |||
Found By: | --- | Services Priority: | |
Business Priority: | Blocker: | --- | |
Marketing QA Status: | --- | IT Deployment: | --- |
Description
macias -
2010-02-10 17:10:16 UTC
. *** This bug has been marked as a duplicate of bug 578789 *** What is relevance with the other bug except for the poster and module (firewall)? Validating should occur just after user entered the interface names. It has nothing to do _what_ she/he entered. There's no reason for firewall to validate input it gets from network modules (list of network interfaces). IMO network should check the interfaces before returning them to firewall. Maciej, I suppose you're using NetworkManager, which uses it's own configuration format. To "add" interface into firewall, try just "touch /etc/sysconfig/network/ifcfg-eth0" or start "yast2 lan" and create configuration for eth0. Does it works for you? Thank you for the tip. This workaround works and I also confirm it is KNM related, because once I turn it off, I can change the zone directly and the interface is recognized. Just in case, remark -- this report is about changing validation "point", not about changing validation algorithm. Michal, is there any Network*::*() function I could you to get list of network devices instead of interfaces? See comment #5. Sounds like task for Michal. Please reassign if you have some function firewall could call or simply fix it in firewall as well :) ;) *** Bug 683487 has been marked as a duplicate of this bug. *** *** Bug 820382 has been marked as a duplicate of this bug. *** *** Bug 955057 has been marked as a duplicate of this bug. *** |