http://bugzilla.novell.com/show_bug.cgi?id=559520 http://bugzilla.novell.com/show_bug.cgi?id=559520#c0 Summary: Yast2 software mangement misinterprets no_proxy settings Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i386 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Rainer.Koenig@ts.fujitsu.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.15) Gecko/2009102814 Iceweasel/3.0.6 (Debian-3.0.6-3) Test lab with PXE install of openSUSE from an internal server 192.168.2.1. Access to internet is possible via a proxy in another subnet. But this proxy is not able to access back to 192.168.2.1 since this is not routed back to the laboratory net. So now I define proxy settings in Yast with "no proxy for" 127.0.0.1, 192.168.2.0/24 If now I want to access repositories on the internet I get error messages for my repo on 192.168.2.1 where I installed from. There is a nice workaround: Just excluding the server instead of the whole subnet works. So I guess YaST2 is just unable to handle "192.168.2.0/24" correctly. Reproducible: Always Steps to Reproduce: 1. Install from PXE 2. Define Proxy settings 3. Try to install something Actual Results: You get a message from YaST that it can't access the repository on the local laboratory network server Expected Results: No problem Workaround is easy by just excluding the host instead of the network. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.