https://bugzilla.novell.com/show_bug.cgi?id=309092 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |yast2-maintainers@suse.de Severity|Major |Enhancement -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=309092#c3 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|lnussel@novell.com | --- Comment #3 from Ludwig Nussel 2007-09-11 04:28:13 MST --- You are right. DNS replies should just work as iptables consideres them as ESTABLISHED or RELATED. If that's not the case with some proprietary vpn solution then there is nothing we can do about it. DHCP clients use packet sockets that bypass filtering rules so there is normally no need to open then explicitly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=309092#c5 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #5 from Lukas Ocilka 2007-09-11 07:02:20 MST --- I'm sorry but I seems your configuration is really very rare and it seems that the Custom Rules is the best way to go. YaST Firewall interface should not confuse common users with commonly-unneeded stuff. If YaST UI doesn't fit your needs, you can still edit /etc/sysconfig/SuSEfirewall2 file directly. 1.) Might be also caused by a wrong VPN or wrong router configuration. Such packets should be in state RELATED/ESTABLISHED when they arrive to the client's network interface. 2.) In firewall, you can set some rules for incoming packets, not outgoing (yes, iptables can configure both, but not YaST Firewall). Such definition you need "any packets coming from port 53" might be dangerous and doesn't cover the common way of using YaST Firewall. Custom Rules or editing the configuration manually is the way to go. _useful_ doesn't need to mean _useful-for-the-majority-of-users_ we can't have all features every single user needs, I'm sorry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.