Network configuration |
modules/Lan.ycp |
Network card data | |
|
|
This module has an unstable interface. |
Current module information
autoinstallation: if true, write_only is disabled and the network settings are applied at once, like during the normal installation. #128810, #168806
Hotplug type ("" if not hot pluggable)
wl_wpa_eap aggregates the settings in a map for easier CWM access.
Structure wpa_eap
WPA_EAP_MODE: string ("TTLS" "PEAP" or "TLS") WPA_EAP_IDENTITY: string WPA_EAP_PASSWORD: string (for TTLS and PEAP) WPA_EAP_ANONID: string (for TTLS and PEAP) WPA_EAP_CLIENT_CERT: string (for TLS, file name) WPA_EAP_CLIENT_KEY: string (for TLS, file name) WPA_EAP_CLIENT_KEY_PASSWORD: string (for TLS) WPA_EAP_CA_CERT: string (file name) WPA_EAP_AUTH: string ("", "MD5", "GTC", "CHAP"*, "PAP"*, "MSCHAP"*, "MSCHAPV2") (*: TTLS only) WPA_EAP_PEAP_VERSION: string ("", "0", "1")
Abort function return boolean return true if abort
Hardware information
- See
-
ReadHardware
Modules information
- See
-
ReadModules
Deleted modules
/etc/install.inf data
Data was modified?
Which operation is pending?
Data was modified?
- Return value:
-
true if modified
For s390 hwinfo gives us a multitude of types but some are handled the same, mostly acording to the driver which is used. So let's group them under the name Driver Type.
- Parameters:
-
type a type, as in Lan::type
- Return value:
-
driver type, like formerly type2 for s390
Lan::Read (`cache) will do nothing if initialized already.
Read all network settings from the SCR
- Parameters:
-
cache : `cache=use cached data, `nocache=reread from disk (for reproposal); TODO pass to submodules
- Return value:
-
true on success
(a specialization used when a parameterless function is needed)
- Return value:
-
Read(`cache)
Update the SCR according to network settings
- Return value:
-
true on success
Only write configuration without starting any init scripts and SuSEconfig
- Return value:
-
true on success
Import data
- Parameters:
-
settings settings to be imported
- Return value:
-
true on success
Export data
- Return value:
-
dumped settings (later acceptable by Import())
Select the hardware component
- Parameters:
-
hw the component
Select the hardware component
- Parameters:
-
which index of the component
Create a textual summary and a list of unconfigured devices
- Parameters:
-
mode "split": split configured and unconfigured?
"summary": add resolver and routing symmary, "proposal": for proposal, add links for direct config
- Return value:
-
summary of the current configuration
Create a textual summary for the NetworkManager proposal
- Return value:
-
[rich text, links]
Create an overview table with all configured devices
- Return value:
-
table items
Return 10 free devices
- Parameters:
-
type device type
- Return value:
-
of 10 free devices
Return 10 free aliases
- Parameters:
-
type device type num device number
- Return value:
-
of 10 free devices
must be in sync with SetDefaultsForHW
must be in sync with GetDefaultsForHW
the defaults here are what sysconfig defaults to (as opposed to what a new interface gets, in Select)
Set various device variables
- Parameters:
-
devmap map with variables defaults
Select the given device
- Parameters:
-
dev device to select ("" for new device, default values)
- Return value:
-
true if success
Add a new device
- Return value:
-
true if success
Edit the given device
- Parameters:
-
name device to edit
- Return value:
-
true if success
Delete the given device
- Parameters:
-
name device to delete
- Return value:
-
true if success
Commit pending operation
- Return value:
-
true if success
Get the module configuration for the modules configured in the interface section
- Parameters:
-
ay_device Device, for example eth0 ay_modules list of modules from the AY profile
- Return value:
-
the module map with module name and options
Find matching device Find a device, optionally with some predefined values
- Parameters:
-
interface interface map
- Return value:
-
The map of the matching device.
Uses product info and is subject to installed packages.
- Return value:
-
Should NM be enabled?
Create minimal ifcfgs for the case when NetworkManager is used: NM does not need them but yast2-firewall and SuSEfirewall2 do Avoid existing ifcfg from network installation
Propose interface configuration
- Return value:
-
true if something was proposed
Propose the hostname See also DNS::Read
- Return value:
-
true if something was proposed
Propose configuration for routing and resolver
- Return value:
-
true if something was proposed
Propose a configuration
- Return value:
-
true if something was proposed
Create a configuration for autoyast
- Return value:
-
true if something was proposed
Check if any device except the current one is configured with DHCP. The current one is checked separately because there may be uncommitted changes. (#17391)
- Return value:
-
true if any DHCP device except the current one is configured
Check if the given device has any virtual alias.
- Parameters:
-
dev device to be checked
- Return value:
-
true if there are some aliases
- Return value:
-
of packages needed when writing the config
- Return value:
-
of packages needed when writing the config in autoinst mode
Function which returns if the settings were modified
- Return value:
-
settings were modified
Function sets internal variable, which indicates, that any settings were modified, to "true"
Function sets internal variable, which indicates, that any settings were modified, to "false"