Bug 215991

Summary:	Proxy testing fails during network configuration
Product:	[openSUSE] openSUSE 10.2	Reporter:	Forgotten User DVG0Sx8gYR <forgotten_DVG0Sx8gYR>
Component:	Installation	Assignee:	Katarina Machalkova <kmachalkova>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Minor
Priority:	P5 - None	CC:	kontakt
Version:	Beta 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User DVG0Sx8gYR 2006-10-27 21:55:08 UTC

During the network configuration it's possible to set up a proxy. However, even though a button is provided to test the proxy settings, this test always fails because the network interface isn't actually set up until you have accepted the settings on this page.

To properly test the settings, you need to accept the settings on the network configuration page, and then use the back button on the connection testing page, to take you back to the network configuration page. Testing the proxy settings after this procedure gives a true success or failure response.

Comment 1 Katarina Machalkova 2006-11-07 14:14:45 UTC

You're right that the network settings are not written until user accepts all the settings on this page and then, they're all written at once. 
The reason why it is done this way is that some settings are dependent on another (e.g. if you configure new network interface, the configuration of the firewall also changes, since the interface needs to be added to some firewall zone).

Testing the proxy before the network is actually set up doesn't make much sense. The proposed solution would be to disable 'Test proxy' button in the installation workflow. You can check the functionality of your connection (i.e. of the proxy setup as well) later on, in Internet test ...

Comment 2 Katarina Machalkova 2006-11-08 10:05:55 UTC

Fixed in yast2-network 2.14.9

Comment 3 Katarina Machalkova 2006-11-08 15:49:31 UTC

*** Bug 143271 has been marked as a duplicate of this bug. ***