Bug 520152

Summary:	Yast Cannot Configure a Modem as Anything but an IP Ethernet Communication device Only.
Product:	[openSUSE] openSUSE 11.1	Reporter:	Scott Couston <scott>
Component:	YaST2	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED FEATURE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	scott
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Scott Couston 2009-07-08 11:26:36 UTC

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.10) Gecko/2009042700 SUSE/3.0.10-1.1.1 Firefox/3.0.10

If a PC has been configured with its IP Network Being via a NIC and Ethernet it is not possible for yast to configure a 9600Baud Modem as a device for sending faxes. Yast assumes that the presence of a Modem on the PC bus as an Internet IP connection Only. It is therefore not able to configure a Modem to be used as a fax modem only. Part of this issue is that in the configuration of the Modem, it expects the number of the ISP Provider. Even creating a custom provider will not work as it demand one single number to dial for the sole purpose of setting up a Dial-UP connection with an ISP.
I am going to setup Hylafax but Yast>Modem may not release any configuration of the Modem. Once Yast sees a Modem the configuration within Yast cannot be deleted.
I am yet to see if Hylafax can over-right the Modem Device which is now in Yast and cannot be removed. I just hope configuration of Hylafax can over-right Yasts' grip on the Modem so it can be configured via faxsetup. Yast needs to be able to configure a Modem on the BUS to be used for any type communications. Currently a Modem can only be configured to provide IP services only and does not even ask the user during setup if the configuration should by for IP functions or any Modem config of any other type of comms connection.

We need to remove this assumption and let the user specify what the device will be used for.

Reproducible: Always

Steps to Reproduce:
1.As above.
2.
3.
Actual Results:
As Above

Expected Results:
Yast can configure a modem device based on the manner the user want to use the device. Currently Yast can only consider that a Modem is for connection to an ISP, without offering the user to be able to configure the device for ANY other type comms, except the default access being via IP

Comment 1 Michal Zugec 2010-05-03 09:15:54 UTC

This is a feature request, not bugreport. Please use   openFATE (https://features.opensuse.org/) instead of bugzilla.

Comment 2 Scott Couston 2010-05-03 12:56:43 UTC

Since middle of 2009 we did not have FATE available - The feature request was opened immediately upon FATE being available and has been sitting there to handle multiple adapters,multiple protocol stacks, and multiple emulators to go with protocol stacks - The world DOES NOT RUN ON ETHERNET AND TCP/IP - Just ask EVERY .AU gov AND AU.mil and ALL Policing and ever single banking corporation in .AU. We still use secure comms, Mainframes and 3270 emulators a huge market Novell has no interest in selling 500,000 CAL units and more! 
Given your production excellence I am loath to provide a personal introduction to our largest bank IT Security Manager - Westpac Corporation whom is a personal friend - /good luck with that one!