Sabayon Linux 11 Mate isn't installable [Solved]

Installer Issues via Installer -- Not for global upgrades or upgrading individual packages -- ONLY ISSUES WITH INSTALLATION OF THE OS -- Can't get Sabayon installed, than post here, otherwise use correct forums

Moderator: Moderators

Sabayon Linux 11 Mate isn't installable [Solved]

Postby Ryuno-Ki » Wed Mar 27, 2013 2:02

Good evening *yawn*
I've tried the last ~4 hours to install Sabayon Linux 11 Mate x86 on my machine (hardware details in the signature).
Yes, I've doubled checked the md5sums. They're correct.
I tried UNetBootin and dd to create a bootable USB-Stick (on Ubuntu Linux 12.04 Precise Pangolin).
With the first one I can choose some extra points, which aren't available, when just cloning the .iso.
But only the "Help" point let me boot some text mode.
But the boot partition isn't found. I can access Ubuntu 10.04 on /dev/sda1 but not my Sabayon Linux installation.
I've tried the released Mate and the daily build of this flavour. Both with no luck.

Can someone explain me, how the boot parameters work?

However, the reason I want to reinstall SL is a change from 64Bit back to 32Bit and wiping Lucid while doing it.

After creating the Live pen drive I couldn't even login. ~/.xsession-errors told me, that "startkde" was missing, so I installed LightDM shortly. No idea, how my Display Manager could be removed without an intervention by me … however, I can boot my Sabayon Linux installation on hard disk again.

I'll attach some logfiles, when I am up again. Which one do you need?
Code: Select all
# fdisk -l
$ cat ~/.xsession-errors
# cat /var/log/Xorg.0.log
$ dmesg

more?
Last edited by Ryuno-Ki on Wed Mar 27, 2013 23:07, edited 1 time in total.
HP-Pavilion ◆ AMD Athlon™ 64 Processor 4000+ ◆ GeForce 6150SE nForce 430 ◆ 1 GiB RAM
German Wiki translator ◆ Want to contribute on the wiki? Ask the Bureaucrats!
Please, mark solved threads ◆ Posts unread and unansweredPackage requests ◆ Sabayon XI with MATE
Ryuno-Ki
Technological Hen
 
Posts: 437
Joined: Mon Feb 27, 2012 22:15
Location: Southern Germany

Re: Sabayon Linux 11 Mate isn't installable

Postby Ryuno-Ki » Wed Mar 27, 2013 23:07

Solved.

Well, at least halfway.
I've downloaded Sabayon 11 CoreCDX x86 and burned it on CD. (Yes, both md5sums are correct).
Then I started the Live boot menu and was presented with a black screen again.
After playing around with the boot options, I found a combination, which works.
Add the following parameter and remove "installer-gui" from the Installation choice (Press F5 and select noapic, nolapic and nomodeset if you like)
Code: Select all
nox legacy session=fluxbox

I don't know, whether all parameters are mandatory, but at least it works.
I've got the boot splash screen ... and then a root shell.
After searching the /home directory and the .desktop-files in /home/sabayonuser/Desktop I discovered the command, you need to run:
Code: Select all
# liveinst

This leads you to a textmode installation (with horrible video bugs) and allows you to walk through the installation process.

You should write down your user/password, because I can't tell you, when the keyboard layout switches from US one to yours.

Now I have a minimalistic installation running - and no WiFi.
But this is another issue.

Edit: Don't forget to unplug USB pen drives before running "liveinst" :!:
Otherwise it will be included in the LVM (and it's a mess to remove it from there imho)
HP-Pavilion ◆ AMD Athlon™ 64 Processor 4000+ ◆ GeForce 6150SE nForce 430 ◆ 1 GiB RAM
German Wiki translator ◆ Want to contribute on the wiki? Ask the Bureaucrats!
Please, mark solved threads ◆ Posts unread and unansweredPackage requests ◆ Sabayon XI with MATE
Ryuno-Ki
Technological Hen
 
Posts: 437
Joined: Mon Feb 27, 2012 22:15
Location: Southern Germany

Re: Sabayon Linux 11 Mate isn't installable [Solved]

Postby Ryuno-Ki » Mon Apr 01, 2013 21:26

Just for the record some logfiles:

history:
Code: Select all
    1  passwd
    2  lsmod | grep usb
    3  ping -c 3 www.gentoo.de
    4  blacklist rt2800usb
    5  fdisk -l
    6  mount
    7  lsusb
    8  iwlist scan
    9  iwconfig
   10  NetworkManager
   11  wpa_supplicant
   12  bzcat /usr/share/doc/wpa_supplicant-0.7.3-r5/wpa_supplicant.conf.bz2 > /etc/wpa_supplicant/wpa_supplicant.conf
   13  chmod 600 /etc/wpa_supplicant/wpa_supplicant.conf
   14  wpa_supplicant -i wlp0s2f1u4 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -dd
   15  wpa_supplicant -i wlp0s2f1u4 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -dd | less
   16  cp /etc/wpa_supplicant/wpa_supplicant.conf /etc/wpa_supplicant/wpa_supplicant-origin.conf
   17  nano /etc/wpa_supplicant/wpa_supplicant.conf
   18  net-setup wlp0s2f1u4
   19  ifconfig
   20  iwconfig
   21  ls /etc/init.d/
   22  ls -l /etc/init.d/
   23  ls -l /etc/init.d/ | grep lo
   24  cd /etc/init.d/
   25  ln -s net.lo net.wlan0
   26  iwconfig
   27  ln -s net.lo net.wlp0s2f1u4
   28  l /etc/init.d/ | grep lo
   29  ls -l /etc/init.d/ | grep lo
   30  cd ../conf.d/
   31  ls
   32  cp net net-origin
   33  nano net
   34  /etc/init.d/net.wlp0s2f1u4 start
   35  ls /etc/wpa_supplicant/
   36  nano /etc/wpa_supplicant/wpa_supplicant.conf
   37  /etc/init.d/net.wlp0s2f1u4 start
   38  /etc/init.d/net.wlp0s2f1u4 stop
   39  less /var/log/rc.log
   40  rc-update add net.wlp0s2f1u4 default
   41  rc
   42  history
   43  ping -c 3 www.gentoo.de
   44  ls /etc/conf.d/net
   45  ls /etc/conf.d/
   46  nano /etc/conf.d/net
   47  nano /etc/wpa_supplicant/wpa_supplicant.conf
   48  /etc/init.d/net.wlp0s2f1u4 start
   49  /etc/init.d/net.wlp0s2f1u4 stop
   50  /etc/init.d/net.wlp0s2f1u4 start
   51  /etc/init.d/net.wlp0s2f1u4 restart
   52  iwconfig
   53  net-setup wlp0s2f1u4
   54  ifconfig
   55  iwconfig
   56  wpa_supplicant -i wlp0s2f1u4 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -dd | less
   57  wpa_supplicant -i wlp0s2f1u4 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -dd > /home/andre/Desktop/wpa_supplicant.log
   58  chown andre:andre /home/andre/Desktop/wpa_supplicant.log
   59  lsmod > /home/andre/Desktop/lsmod.log
   60  chown andre:andre /home/andre/Desktop/lsmod.log
   61  history > /home/andre/Desktop/history.log


lsmod:
Code: Select all
Module                  Size  Used by
8021q                  11552  0
garp                    3571  1 8021q
stp                      994  1 garp
llc                     2485  2 stp,garp
xt_hl                    745  6
ip6t_rt                 3821  3
nf_conntrack_ipv6       5285  6
nf_defrag_ipv6          5746  1 nf_conntrack_ipv6
ipt_REJECT              1425  1
xt_LOG                  8037  1
xt_limit                 877  2
xt_tcpudp               2117  18
xt_addrtype             1781  4
nf_conntrack_ipv4       8707  6
nf_defrag_ipv4           815  1 nf_conntrack_ipv4
xt_conntrack            2033  12
ip6table_filter          737  1
ip6_tables              8408  2 ip6table_filter,ip6t_rt
ipv6                  206466  32 nf_defrag_ipv6,nf_conntrack_ipv6
nf_conntrack_netbios_ns      617  0
nf_conntrack_broadcast      790  1 nf_conntrack_netbios_ns
nf_nat_ftp              1301  0
nf_nat                 10469  1 nf_nat_ftp
nf_conntrack_ftp        6573  1 nf_nat_ftp
nf_conntrack           47952  8 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_conntrack,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_ipv6
iptable_filter           777  1
ip_tables               8006  1 iptable_filter
x_tables                8918  12 ip6table_filter,xt_hl,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ip6t_rt,ipt_REJECT,ip6_tables,xt_addrtype
snd_hda_codec_realtek    37925  1
snd_hda_intel          18921  0
snd_hda_codec          56550  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               3459  1 snd_hda_codec
snd_pcm                46360  2 snd_hda_codec,snd_hda_intel
nvidia              10195390  30
snd_page_alloc          5107  2 snd_pcm,snd_hda_intel
snd_timer              11091  1 snd_pcm
snd                    33637  6 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
firewire_ohci          22109  0
firewire_core          32467  1 firewire_ohci
k8temp                  2165  0
rt2800usb              11133  0
rt2x00usb               5873  1 rt2800usb
rt2800lib              38887  1 rt2800usb
rt2x00lib              25112  3 rt2x00usb,rt2800lib,rt2800usb
mac80211              183119  3 rt2x00lib,rt2x00usb,rt2800lib
cfg80211              118108  2 mac80211,rt2x00lib
crc_ccitt               1028  1 rt2800lib
forcedeth              41273  0
i2c_nforce2             4305  0
pcspkr                  1065  0
kvm                   175320  0
psmouse                54603  0
serio_raw               3049  0
sha512_generic          8046  0
sha1_generic            1411  0
dm_thin_pool           28876  0
dm_bio_prison           2724  1 dm_thin_pool
dm_persistent_data     26292  1 dm_thin_pool
dm_service_time         2086  0
dm_round_robin          1636  0
dm_queue_length         1809  0
dm_multipath           11745  3 dm_round_robin,dm_queue_length,dm_service_time
scsi_dh                 3570  1 dm_multipath
dm_log_userspace        7747  0
dm_flakey               3199  0
dm_delay                3036  0
dm_bufio                9977  1 dm_persistent_data
virtio_pci              4807  0
virtio_blk              7007  0
virtio_net             10912  0
virtio_console         11759  0
virtio_balloon          3410  0
virtio_ring             4113  5 virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_console
virtio                  2518  5 virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_console
ablk_helper             1205  0
cryptd                  5584  1 ablk_helper
lrw                     2622  0
xts                     2144  0
gf128mul                5171  2 lrw,xts
aes_i586                6864  0
sha256_generic         11206  0
iscsi_tcp               6365  0
tg3                   108636  0
e1000                  97520  0
fuse                   49468  0
xfs                   388172  0
nfs                    84762  0
lockd                  43855  1 nfs
sunrpc                120542  2 nfs,lockd
jfs                   133969  0
reiserfs              183659  0
ext4                  230263  3
jbd2                   42196  1 ext4
ext3                   92173  0
jbd                    32931  1 ext3
ext2                   46078  0
mbcache                 3591  3 ext2,ext3,ext4
sl811_hcd               7648  0
hid_generic              654  0
xhci_hcd               66436  0
ohci_hcd               21583  0
uhci_hcd               17583  0
ehci_hcd               40104  0
sx8                     9684  0
imm                     7134  0
parport                21628  1 imm
pata_pcmcia             6690  0
pcmcia                 33565  1 pata_pcmcia


wpa_supplicant output:
Code: Select all
Initializing interface 'wlp0s2f1u4' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0'
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 893 - start of a new network block
ssid - hexdump_ascii(len=23):
     46 52 49 54 5a 21 42 6f 78 20 46 6f 6e 20 57 4c   FRITZ!Box Fon WL
     41 4e 20 37 31 34 31                              AN 7141         
scan_ssid=1 (0x1)
proto: 0x2
key_mgmt: 0x2
pairwise: 0x10
group: 0x10
PSK (ASCII passphrase) - hexdump_ascii(len=16): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='FRITZ!Box Fon WLAN 7141'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 34:08:04:30:7b:de
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Using existing control interface directory.
ctrl_interface_group=0
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlp0s2f1u4' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

Failed to add interface wlp0s2f1u4
No keys have been configured - skip key clearing
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
netlink: Operstate: linkmode=0, operstate=6


wpa_supplicant.conf: (password obfuscated)
Code: Select all
##### Example wpa_supplicant configuration file ###############################
#
# This file describes configuration file format and lists all available option.
# Please also take a look at simpler configuration examples in 'examples'
# subdirectory.
#
# Empty lines and lines starting with # are ignored
# NOTE! This file may contain password information and should probably be made
# readable only by root user on multiuser systems.
# Note: All file paths in this configuration file should use full (absolute,
# not relative to working directory) path in order to allow working directory
# to be changed. This can happen if wpa_supplicant is run in the background.
# Whether to allow wpa_supplicant to update (overwrite) configuration
#
# This option can be used to allow wpa_supplicant to overwrite configuration
# file whenever configuration is changed (e.g., new network block is added with
# wpa_cli or wpa_gui, or a password is changed). This is required for
# wpa_cli/wpa_gui to be able to store the configuration changes permanently.
# Please note that overwriting configuration file will remove the comments from
# it.
#update_config=1
# global configuration (shared by all network blocks)
#
# Parameters for the control interface. If this is specified, wpa_supplicant
# will open a control interface that is available for external programs to
# manage wpa_supplicant. The meaning of this string depends on which control
# interface mechanism is used. For all cases, the existance of this parameter
# in configuration is used to determine whether the control interface is
# enabled.
#
# For UNIX domain sockets (default on Linux and BSD): This is a directory that
# will be created for UNIX domain sockets for listening to requests from
# external programs (CLI/GUI, etc.) for status information and configuration.
# The socket file will be named based on the interface name, so multiple
# wpa_supplicant processes can be run at the same time if more than one
# interface is used.
# /var/run/wpa_supplicant is the recommended directory for sockets and by
# default, wpa_cli will use it when trying to connect with wpa_supplicant.
#
# Access control for the control interface can be configured by setting the
# directory to allow only members of a group to use sockets. This way, it is
# possible to run wpa_supplicant as root (since it needs to change network
# configuration and open raw sockets) and still allow GUI/CLI components to be
# run as non-root users. However, since the control interface can be used to
# change the network configuration, this access needs to be protected in many
# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
# want to allow non-root users to use the control interface, add a new group
# and change this value to match with that group. Add users that should have
# control interface access to this group. If this variable is commented out or
# not included in the configuration file, group will not be changed from the
# value it got by default when the directory or socket was created.
#
# When configuring both the directory and group, use following format:
# DIR=/var/run/wpa_supplicant GROUP=wheel
# DIR=/var/run/wpa_supplicant GROUP=0
# (group can be either group name or gid)
#
# For UDP connections (default on Windows): The value will be ignored. This
# variable is just used to select that the control interface is to be created.
# The value can be set to, e.g., udp (ctrl_interface=udp)
#
# For Windows Named Pipe: This value can be used to set the security descriptor
# for controlling access to the control interface. Security descriptor can be
# set using Security Descriptor String Format (see http://msdn.microsoft.com/
# library/default.asp?url=/library/en-us/secauthz/security/
# security_descriptor_string_format.asp). The descriptor string needs to be
# prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty
# DACL (which will reject all connections). See README-Windows.txt for more
# information about SDDL string format.
#
ctrl_interface=/var/run/wpa_supplicant
# only root can see the wpa config
ctrl_interface_group=0
# IEEE 802.1X/EAPOL version
# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
# EAPOL version 2. However, there are many APs that do not handle the new
# version number correctly (they seem to drop the frames completely). In order
# to make wpa_supplicant interoperate with these APs, the version number is set
# to 1 by default. This configuration value can be used to set it to the new
# version (2).
eapol_version=1
# AP scanning/selection
# By default, wpa_supplicant requests driver to perform AP scanning and then
# uses the scan results to select a suitable AP. Another alternative is to
# allow the driver to take care of AP scanning and selection and use
# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
# information from the driver.
# 1: wpa_supplicant initiates scanning and AP selection; if no APs matching to
#    the currently enabled networks are found, a new network (IBSS or AP mode
#    operation) may be initialized (if configured) (default)
# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
#    parameters (e.g., WPA IE generation); this mode can also be used with
#    non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
#    APs (i.e., external program needs to control association). This mode must
#    also be used when using wired Ethernet drivers.
# 2: like 0, but associate with APs using security policy and SSID (but not
#    BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
#    enable operation with hidden SSIDs and optimized roaming; in this mode,
#    the network blocks in the configuration file are tried one by one until
#    the driver reports successful association; each network block should have
#    explicit security policy (i.e., only one option in the lists) for
#    key_mgmt, pairwise, group, proto variables
# When using IBSS or AP mode, ap_scan=2 mode can force the new network to be
# created immediately regardless of scan results. ap_scan=1 mode will first try
# to scan for existing networks and only if no matches with the enabled
# networks are found, a new IBSS or AP mode network is created.
ap_scan=1
# EAP fast re-authentication
# By default, fast re-authentication is enabled for all EAP methods that
# support it. This variable can be used to disable fast re-authentication.
# Normally, there is no need to disable this.
fast_reauth=1
# OpenSSL Engine support
# These options can be used to load OpenSSL engines.
# The two engines that are supported currently are shown below:
# They are both from the opensc project (http://www.opensc.org/)
# By default no engines are loaded.
# make the opensc engine available
#opensc_engine_path=/usr/lib/engine_opensc.so
# make the pkcs11 engine available
#pkcs11_engine_path=/usr/lib/engine_pkcs11.so
# configure the path to the pkcs11 module required by the pkcs11 engine
#pkcs11_module_path=/usr/lib/opensc-pkcs11.so
# Dynamic EAP methods
# If EAP methods were built dynamically as shared object files, they need to be
# loaded here before being used in the network blocks. By default, EAP methods
# are included statically in the build, so these lines are not needed
#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
# Driver interface parameters
# This field can be used to configure arbitrary driver interace parameters. The
# format is specific to the selected driver interface. This field is not used
# in most cases.
#driver_param="field=value"
# Country code
# The ISO/IEC alpha2 country code for the country in which this device is
# currently operating.
#country=US
# Maximum lifetime for PMKSA in seconds; default 43200
#dot11RSNAConfigPMKLifetime=43200
# Threshold for reauthentication (percentage of PMK lifetime); default 70
#dot11RSNAConfigPMKReauthThreshold=70
# Timeout for security association negotiation in seconds; default 60
#dot11RSNAConfigSATimeout=60
# Wi-Fi Protected Setup (WPS) parameters
# Universally Unique IDentifier (UUID; see RFC 4122) of the device
# If not configured, UUID will be generated based on the local MAC address.
#uuid=12345678-9abc-def0-1234-56789abcdef0
# Device Name
# User-friendly description of device; up to 32 octets encoded in UTF-8
#device_name=Wireless Client
# Manufacturer
# The manufacturer of the device (up to 64 ASCII characters)
#manufacturer=Company
# Model Name
# Model of the device (up to 32 ASCII characters)
#model_name=cmodel
# Model Number
# Additional device description (up to 32 ASCII characters)
#model_number=123
# Serial Number
# Serial number of the device (up to 32 characters)
#serial_number=12345
# Primary Device Type
# Used format: <categ>-<OUI>-<subcateg>
# categ = Category as an integer value
# OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
#       default WPS OUI
# subcateg = OUI-specific Sub Category as an integer value
# Examples:
#   1-0050F204-1 (Computer / PC)
#   1-0050F204-2 (Computer / Server)
#   5-0050F204-1 (Storage / NAS)
#   6-0050F204-1 (Network Infrastructure / AP)
#device_type=1-0050F204-1
# OS Version
# 4-octet operating system version number (hex string)
#os_version=01020300
# Config Methods
# List of the supported configuration methods
# Available methods: usba ethernet label display ext_nfc_token int_nfc_token
#        nfc_interface push_button keypad
#config_methods=label display push_button keypad
# Credential processing
#   0 = process received credentials internally (default)
#   1 = do not process received credentials; just pass them over ctrl_iface to
#        external program(s)
#   2 = process received credentials internally and pass them over ctrl_iface
#        to external program(s)
#wps_cred_processing=0
# Maximum number of BSS entries to keep in memory
# Default: 200
# This can be used to limit memory use on the BSS entries (cached scan
# results). A larger value may be needed in environments that have huge number
# of APs when using ap_scan=1 mode.
#bss_max_count=200
# filter_ssids - SSID-based scan result filtering
# 0 = do not filter scan results (default)
# 1 = only include configured SSIDs in scan results/BSS table
#filter_ssids=0
# network block
#
# Each network (usually AP's sharing the same SSID) is configured as a separate
# block in this configuration file. The network blocks are in preference order
# (the first match is used).
#
# network block fields:
#
# disabled:
#        0 = this network can be used (default)
#        1 = this network block is disabled (can be enabled through ctrl_iface,
#            e.g., with wpa_cli or wpa_gui)
#
# id_str: Network identifier string for external scripts. This value is passed
#        to external action script through wpa_cli as WPA_ID_STR environment
#        variable to make it easier to do network specific configuration.
#
# ssid: SSID (mandatory); either as an ASCII string with double quotation or
#        as hex string; network name
#
# scan_ssid:
#        0 = do not scan this SSID with specific Probe Request frames (default)
#        1 = scan with SSID-specific Probe Request frames (this can be used to
#            find APs that do not accept broadcast SSID or use multiple SSIDs;
#            this will add latency to scanning, so enable this only when needed)
#
# bssid: BSSID (optional); if set, this network block is used only when
#        associating with the AP using the configured BSSID
#
# priority: priority group (integer)
# By default, all networks will get same priority group (0). If some of the
# networks are more desirable, this field can be used to change the order in
# which wpa_supplicant goes through the networks when selecting a BSS. The
# priority groups will be iterated in decreasing priority (i.e., the larger the
# priority value, the sooner the network is matched against the scan results).
# Within each priority group, networks will be selected based on security
# policy, signal strength, etc.
# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
# using this priority to select the order for scanning. Instead, they try the
# networks in the order that used in the configuration file.
#
# mode: IEEE 802.11 operation mode
# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
# 1 = IBSS (ad-hoc, peer-to-peer)
# 2 = AP (access point)
# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). WPA-None requires
# following network block options:
# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
# both), and psk must also be set.
#
# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
# In addition, this value is only used by the station that creates the IBSS. If
# an IBSS network with the configured SSID is already present, the frequency of
# the network will be used instead of this configured value.
#
# scan_freq: List of frequencies to scan
# Space-separated list of frequencies in MHz to scan when searching for this
# BSS. If the subset of channels used by the network is known, this option can
# be used to optimize scanning to not occur on channels that the network does
# not use. Example: scan_freq=2412 2437 2462
#
# freq_list: Array of allowed frequencies
# Space-separated list of frequencies in MHz to allow for selecting the BSS. If
# set, scan results that do not match any of the specified frequencies are not
# considered when selecting a BSS.
#
# proto: list of accepted protocols
# WPA = WPA/IEEE 802.11i/D3.0
# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
# If not set, this defaults to: WPA RSN
#
# key_mgmt: list of accepted authenticated key management protocols
# WPA-PSK = WPA pre-shared key (this requires 'psk' field)
# WPA-EAP = WPA using EAP authentication
# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
#        generated WEP keys
# NONE = WPA is not used; plaintext or static WEP could be used
# WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms
# WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms
# If not set, this defaults to: WPA-PSK WPA-EAP
#
# auth_alg: list of allowed IEEE 802.11 authentication algorithms
# OPEN = Open System authentication (required for WPA/WPA2)
# SHARED = Shared Key authentication (requires static WEP keys)
# LEAP = LEAP/Network EAP (only used with LEAP)
# If not set, automatic selection is used (Open System with LEAP enabled if
# LEAP is allowed as one of the EAP methods).
#
# pairwise: list of accepted pairwise (unicast) ciphers for WPA
# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
# NONE = Use only Group Keys (deprecated, should not be included if APs support
#        pairwise keys)
# If not set, this defaults to: CCMP TKIP
#
# group: list of accepted group (broadcast/multicast) ciphers for WPA
# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
# If not set, this defaults to: CCMP TKIP WEP104 WEP40
#
# psk: WPA preshared key; 256-bit pre-shared key
# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
# generated using the passphrase and SSID). ASCII passphrase must be between
# 8 and 63 characters (inclusive).
# This field is not needed, if WPA-EAP is used.
# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
# startup and reconfiguration time can be optimized by generating the PSK only
# only when the passphrase or SSID has actually changed.
#
# eapol_flags: IEEE 802.1X/EAPOL options (bit field)
# Dynamic WEP key required for non-WPA mode
# bit0 (1): require dynamically generated unicast WEP key
# bit1 (2): require dynamically generated broadcast WEP key
#         (3 = require both keys; default)
# Note: When using wired authentication, eapol_flags must be set to 0 for the
# authentication to be completed successfully.
#
# mixed_cell: This option can be used to configure whether so called mixed
# cells, i.e., networks that use both plaintext and encryption in the same
# SSID, are allowed when selecting a BSS form scan results.
# 0 = disabled (default)
# 1 = enabled
#
# proactive_key_caching:
# Enable/disable opportunistic PMKSA caching for WPA2.
# 0 = disabled (default)
# 1 = enabled
#
# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
# hex without quotation, e.g., 0102030405)
# wep_tx_keyidx: Default WEP key index (TX) (0..3)
#
# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is
# allowed. This is only used with RSN/WPA2.
# 0 = disabled (default)
# 1 = enabled
#peerkey=1
#
# wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to
# enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies.
#
# Following fields are only used with internal EAP implementation.
# eap: space-separated list of accepted EAP methods
#        MD5 = EAP-MD5 (unsecure and does not generate keying material ->
#                        cannot be used with WPA; to be used as a Phase 2 method
#                        with EAP-PEAP or EAP-TTLS)
#       MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
#                as a Phase 2 method with EAP-PEAP or EAP-TTLS)
#       OTP = EAP-OTP (cannot be used separately with WPA; to be used
#                as a Phase 2 method with EAP-PEAP or EAP-TTLS)
#       GTC = EAP-GTC (cannot be used separately with WPA; to be used
#                as a Phase 2 method with EAP-PEAP or EAP-TTLS)
#        TLS = EAP-TLS (client and server certificate)
#        PEAP = EAP-PEAP (with tunnelled EAP authentication)
#        TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
#                         authentication)
#        If not set, all compiled in methods are allowed.
#
# identity: Identity string for EAP
#        This field is also used to configure user NAI for
#        EAP-PSK/PAX/SAKE/GPSK.
# anonymous_identity: Anonymous identity string for EAP (to be used as the
#        unencrypted identity with EAP types that support different tunnelled
#        identity, e.g., EAP-TTLS)
# password: Password string for EAP. This field can include either the
#        plaintext password (using ASCII or hex string) or a NtPasswordHash
#        (16-byte MD4 hash of password) in hash:<32 hex digits> format.
#        NtPasswordHash can only be used when the password is for MSCHAPv2 or
#        MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP).
#        EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit
#        PSK) is also configured using this field. For EAP-GPSK, this is a
#        variable length PSK.
# ca_cert: File path to CA certificate file (PEM/DER). This file can have one
#        or more trusted CA certificates. If ca_cert and ca_path are not
#        included, server certificate will not be verified. This is insecure and
#        a trusted CA certificate should always be configured when using
#        EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
#        change when wpa_supplicant is run in the background.
#
#        Alternatively, this can be used to only perform matching of the server
#        certificate (SHA-256 hash of the DER encoded X.509 certificate). In
#        this case, the possible CA certificates in the server certificate chain
#        are ignored and only the server certificate is verified. This is
#        configured with the following format:
#        hash:://server/sha256/cert_hash_in_hex
#        For example: "hash://server/sha256/
#        5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a"
#
#        On Windows, trusted CA certificates can be loaded from the system
#        certificate store by setting this to cert_store://<name>, e.g.,
#        ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
#        Note that when running wpa_supplicant as an application, the user
#        certificate store (My user account) is used, whereas computer store
#        (Computer account) is used when running wpasvc as a service.
# ca_path: Directory path for CA certificate files (PEM). This path may
#        contain multiple CA certificates in OpenSSL format. Common use for this
#        is to point to system trusted CA list which is often installed into
#        directory like /etc/ssl/certs. If configured, these certificates are
#        added to the list of trusted CAs. ca_cert may also be included in that
#        case, but it is not required.
# client_cert: File path to client certificate file (PEM/DER)
#        Full path should be used since working directory may change when
#        wpa_supplicant is run in the background.
#        Alternatively, a named configuration blob can be used by setting this
#        to blob://<blob name>.
# private_key: File path to client private key file (PEM/DER/PFX)
#        When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
#        commented out. Both the private key and certificate will be read from
#        the PKCS#12 file in this case. Full path should be used since working
#        directory may change when wpa_supplicant is run in the background.
#        Windows certificate store can be used by leaving client_cert out and
#        configuring private_key in one of the following formats:
#        cert://substring_to_match
#        hash://certificate_thumbprint_in_hex
#        for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
#        Note that when running wpa_supplicant as an application, the user
#        certificate store (My user account) is used, whereas computer store
#        (Computer account) is used when running wpasvc as a service.
#        Alternatively, a named configuration blob can be used by setting this
#        to blob://<blob name>.
# private_key_passwd: Password for private key file (if left out, this will be
#        asked through control interface)
# dh_file: File path to DH/DSA parameters file (in PEM format)
#        This is an optional configuration file for setting parameters for an
#        ephemeral DH key exchange. In most cases, the default RSA
#        authentication does not use this configuration. However, it is possible
#        setup RSA to use ephemeral DH key exchange. In addition, ciphers with
#        DSA keys always use ephemeral DH keys. This can be used to achieve
#        forward secrecy. If the file is in DSA parameters format, it will be
#        automatically converted into DH params.
# subject_match: Substring to be matched against the subject of the
#        authentication server certificate. If this string is set, the server
#        sertificate is only accepted if it contains this string in the subject.
#        The subject string is in following format:
#        /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
# altsubject_match: Semicolon separated string of entries to be matched against
#        the alternative subject name of the authentication server certificate.
#        If this string is set, the server sertificate is only accepted if it
#        contains one of the entries in an alternative subject name extension.
#        altSubjectName string is in following format: TYPE:VALUE
#        Example: EMAIL:server@example.com
#        Example: DNS:server.example.com;DNS:server2.example.com
#        Following types are supported: EMAIL, DNS, URI
# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
#        (string with field-value pairs, e.g., "peapver=0" or
#        "peapver=1 peaplabel=1")
#        'peapver' can be used to force which PEAP version (0 or 1) is used.
#        'peaplabel=1' can be used to force new label, "client PEAP encryption",
#        to be used during key derivation when PEAPv1 or newer. Most existing
#        PEAPv1 implementation seem to be using the old label, "client EAP
#        encryption", and wpa_supplicant is now using that as the default value.
#        Some servers, e.g., Radiator, may require peaplabel=1 configuration to
#        interoperate with PEAPv1; see eap_testing.txt for more details.
#        'peap_outer_success=0' can be used to terminate PEAP authentication on
#        tunneled EAP-Success. This is required with some RADIUS servers that
#        implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
#        Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
#        include_tls_length=1 can be used to force wpa_supplicant to include
#        TLS Message Length field in all TLS messages even if they are not
#        fragmented.
#        sim_min_num_chal=3 can be used to configure EAP-SIM to require three
#        challenges (by default, it accepts 2 or 3)
#        result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
#        protected result indication.
#        'crypto_binding' option can be used to control PEAPv0 cryptobinding
#        behavior:
#         * 0 = do not use cryptobinding (default)
#         * 1 = use cryptobinding if server supports it
#         * 2 = require cryptobinding
#        EAP-WSC (WPS) uses following options: pin=<Device Password> or
#        pbc=1.
# phase2: Phase2 (inner authentication with TLS tunnel) parameters
#        (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
#        "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS)
# Following certificate/private key fields are used in inner Phase2
# authentication when using EAP-TTLS or EAP-PEAP.
# ca_cert2: File path to CA certificate file. This file can have one or more
#        trusted CA certificates. If ca_cert2 and ca_path2 are not included,
#        server certificate will not be verified. This is insecure and a trusted
#        CA certificate should always be configured.
# ca_path2: Directory path for CA certificate files (PEM)
# client_cert2: File path to client certificate file
# private_key2: File path to client private key file
# private_key2_passwd: Password for private key file
# dh_file2: File path to DH/DSA parameters file (in PEM format)
# subject_match2: Substring to be matched against the subject of the
#        authentication server certificate.
# altsubject_match2: Substring to be matched against the alternative subject
#        name of the authentication server certificate.
#
# fragment_size: Maximum EAP fragment size in bytes (default 1398).
#        This value limits the fragment size for EAP methods that support
#        fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
#        small enough to make the EAP messages fit in MTU of the network
#        interface used for EAPOL. The default value is suitable for most
#        cases.
#
# EAP-FAST variables:
# pac_file: File path for the PAC entries. wpa_supplicant will need to be able
#        to create this file and write updates to it when PAC is being
#        provisioned or refreshed. Full path to the file should be used since
#        working directory may change when wpa_supplicant is run in the
#        background. Alternatively, a named configuration blob can be used by
#        setting this to blob://<blob name>
# phase1: fast_provisioning option can be used to enable in-line provisioning
#         of EAP-FAST credentials (PAC):
#         0 = disabled,
#         1 = allow unauthenticated provisioning,
#         2 = allow authenticated provisioning,
#         3 = allow both unauthenticated and authenticated provisioning
#        fast_max_pac_list_len=<num> option can be used to set the maximum
#                number of PAC entries to store in a PAC list (default: 10)
#        fast_pac_format=binary option can be used to select binary format for
#                storing PAC entries in order to save some space (the default
#                text format uses about 2.5 times the size of minimal binary
#                format)
#
# wpa_supplicant supports number of "EAP workarounds" to work around
# interoperability issues with incorrectly behaving authentication servers.
# These are enabled by default because some of the issues are present in large
# number of authentication servers. Strict EAP conformance mode can be
# configured by disabling workarounds with eap_workaround=0.
# Example blocks:
# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
#network={
#        ssid="simple"
#        psk="very secret passphrase"
#        priority=5
#}
#
# Same as previous, but request SSID-specific scanning (for APs that reject
# broadcast SSID)
#network={
#        ssid="second ssid"
#        scan_ssid=1
#        psk="very secret passphrase"
#        priority=2
#}
#
# Only WPA-PSK is used. Any valid cipher combination is accepted.
#network={
#        ssid="example"
#        proto=WPA
#        key_mgmt=WPA-PSK
#        pairwise=CCMP TKIP
#        group=CCMP TKIP WEP104 WEP40
#        psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
#        priority=2
#}
#
# WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying
#network={
#        ssid="example"
#        proto=WPA
#        key_mgmt=WPA-PSK
#        pairwise=TKIP
#        group=TKIP
#        psk="not so secure passphrase"
#        wpa_ptk_rekey=600
#}
#
# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
# or WEP40 as the group cipher will not be accepted.
#network={
#        ssid="example"
#        proto=RSN
#        key_mgmt=WPA-EAP
#        pairwise=CCMP TKIP
#        group=CCMP TKIP
#        eap=TLS
#        identity="user@example.com"
#        ca_cert="/etc/cert/ca.pem"
#        client_cert="/etc/cert/user.pem"
#        private_key="/etc/cert/user.prv"
#        private_key_passwd="password"
#        priority=1
#}
#
# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
# (e.g., Radiator)
#network={
#        ssid="example"
#        key_mgmt=WPA-EAP
#        eap=PEAP
#        identity="user@example.com"
#        password="foobar"
#        ca_cert="/etc/cert/ca.pem"
#        phase1="peaplabel=1"
#        phase2="auth=MSCHAPV2"
#        priority=10
#}
#
# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
# unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
#network={
#        ssid="example"
#        key_mgmt=WPA-EAP
#        eap=TTLS
#        identity="user@example.com"
#        anonymous_identity="anonymous@example.com"
#        password="foobar"
#        ca_cert="/etc/cert/ca.pem"
#        priority=2
#}
#
# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
# use. Real identity is sent only within an encrypted TLS tunnel.
#network={
#        ssid="example"
#        key_mgmt=WPA-EAP
#        eap=TTLS
#        identity="user@example.com"
#        anonymous_identity="anonymous@example.com"
#        password="foobar"
#        ca_cert="/etc/cert/ca.pem"
#        phase2="auth=MSCHAPV2"
#}
#
# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
# authentication.
#network={
#        ssid="example"
#        key_mgmt=WPA-EAP
#        eap=TTLS
#        # Phase1 / outer authentication
#        anonymous_identity="anonymous@example.com"
#        ca_cert="/etc/cert/ca.pem"
#        # Phase 2 / inner authentication
#        phase2="autheap=TLS"
#        ca_cert2="/etc/cert/ca2.pem"
#        client_cert2="/etc/cer/user.pem"
#        private_key2="/etc/cer/user.prv"
#        private_key2_passwd="password"
#        priority=2
#}
#
# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
# group cipher.
#network={
#        ssid="example"
#        bssid=00:11:22:33:44:55
#        proto=WPA RSN
#        key_mgmt=WPA-PSK WPA-EAP
#        pairwise=CCMP
#        group=CCMP
#        psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
#}
#
# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
# and all valid ciphers.
#network={
#        ssid=00010203
#        psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
#}
#
#
# EAP-SIM with a GSM SIM or USIM
#network={
#        ssid="eap-sim-test"
#        key_mgmt=WPA-EAP
#        eap=SIM
#        pin="1234"
#        pcsc=""
#}
#
#
# EAP-PSK
#network={
#        ssid="eap-psk-test"
#        key_mgmt=WPA-EAP
#        eap=PSK
#        anonymous_identity="eap_psk_user"
#        password=06b4be19da289f475aa46a33cb793029
#        identity="eap_psk_user@example.com"
#}
#
#
# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
# EAP-TLS for authentication and key generation; require both unicast and
# broadcast WEP keys.
#network={
#        ssid="1x-test"
#        key_mgmt=IEEE8021X
#        eap=TLS
#        identity="user@example.com"
#        ca_cert="/etc/cert/ca.pem"
#        client_cert="/etc/cert/user.pem"
#        private_key="/etc/cert/user.prv"
#        private_key_passwd="password"
#        eapol_flags=3
#}
#
#
# LEAP with dynamic WEP keys
#network={
#        ssid="leap-example"
#        key_mgmt=IEEE8021X
#        eap=LEAP
#        identity="user"
#        password="foobar"
#}
#
# EAP-IKEv2 using shared secrets for both server and peer authentication
#network={
#        ssid="ikev2-example"
#        key_mgmt=WPA-EAP
#        eap=IKEV2
#        identity="user"
#        password="foobar"
#}
#
# EAP-FAST with WPA (WPA or WPA2)
#network={
#        ssid="eap-fast-test"
#        key_mgmt=WPA-EAP
#        eap=FAST
#        anonymous_identity="FAST-000102030405"
#        identity="username"
#        password="password"
#        phase1="fast_provisioning=1"
#        pac_file="/etc/wpa_supplicant.eap-fast-pac"
#}
#
#network={
#        ssid="eap-fast-test"
#        key_mgmt=WPA-EAP
#        eap=FAST
#        anonymous_identity="FAST-000102030405"
#        identity="username"
#        password="password"
#        phase1="fast_provisioning=1"
#        pac_file="blob://eap-fast-pac"
#}
#
# Plaintext connection (no WPA, no IEEE 802.1X)
#network={
#        ssid="plaintext-test"
#        key_mgmt=NONE
#}
#
#
# Shared WEP key connection (no WPA, no IEEE 802.1X)
#network={
#        ssid="static-wep-test"
#        key_mgmt=NONE
#        wep_key0="abcde"
#        wep_key1=0102030405
#        wep_key2="1234567890123"
#        wep_tx_keyidx=0
#        priority=5
#}
#
#
# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
# IEEE 802.11 authentication
#network={
#        ssid="static-wep-test2"
#        key_mgmt=NONE
#        wep_key0="abcde"
#        wep_key1=0102030405
#        wep_key2="1234567890123"
#        wep_tx_keyidx=0
#        priority=5
#        auth_alg=SHARED
#}
#
#
# IBSS/ad-hoc network with WPA-None/TKIP.
#network={
#        ssid="test adhoc"
#        mode=1
#        frequency=2412
#        proto=WPA
#        key_mgmt=WPA-NONE
#        pairwise=NONE
#        group=TKIP
#        psk="secret passphrase"
#}
#
#
# Catch all example that allows more or less all configuration modes
#network={
#        ssid="example"
#        scan_ssid=1
#        key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
#        pairwise=CCMP TKIP
#        group=CCMP TKIP WEP104 WEP40
#        psk="very secret passphrase"
#        eap=TTLS PEAP TLS
#        identity="user@example.com"
#        password="foobar"
#        ca_cert="/etc/cert/ca.pem"
#        client_cert="/etc/cert/user.pem"
#        private_key="/etc/cert/user.prv"
#        private_key_passwd="password"
#        phase1="peaplabel=0"
#}
#
# Example of EAP-TLS with smartcard (openssl engine)
#network={
#        ssid="example"
#        key_mgmt=WPA-EAP
#        eap=TLS
#        proto=RSN
#        pairwise=CCMP TKIP
#        group=CCMP TKIP
#        identity="user@example.com"
#        ca_cert="/etc/cert/ca.pem"
#        client_cert="/etc/cert/user.pem"
#
#        engine=1
#
#        # The engine configured here must be available. Look at
#        # OpenSSL engine support in the global section.
#        # The key available through the engine must be the private key
#        # matching the client certificate configured above.
#
#        # use the opensc engine
#        #engine_id="opensc"
#        #key_id="45"
#
#        # use the pkcs11 engine
#        engine_id="pkcs11"
#        key_id="id_45"
#
#        # Optional PIN configuration; this can be left out and PIN will be
#        # asked through the control interface
#        pin="1234"
#}
#
# Example configuration showing how to use an inlined blob as a CA certificate
# data instead of using external file
#network={
#        ssid="example"
#        key_mgmt=WPA-EAP
#        eap=TTLS
#        identity="user@example.com"
#        anonymous_identity="anonymous@example.com"
#        password="foobar"
#        ca_cert="blob://exampleblob"
#        priority=20
#}
#
#blob-base64-exampleblob={
#SGVsbG8gV29ybGQhCg==
#}
#
#
# Wildcard match for SSID (plaintext APs only). This example select any
# open AP regardless of its SSID.
#network={
#        key_mgmt=NONE
#}
# Here is the actual config placed
network={
       ssid="FRITZ!Box Fon WLAN 7141"
       scan_ssid=1
       proto=RSN
       key_mgmt=WPA-PSK
       pairwise=CCMP
       group=CCMP
       psk="THE-WLAN-PASSWORD"
}
# reading passphrase from stdin
network={
        ssid="FRITZ!Box Fon WLAN 7141"
        #psk="THE-WLAN-PASSWORD"
        psk=YOUR-WLAN-PASSWORD-OUTPUT-OF-WPA_PASSPHRASE
}

(I think I've uploaded a post before with this information not obfuscated - thanks for deleting it, dear moderator)

/etc/conf.d/net:
Code: Select all
# Sabayon Linux static network configuration tool
config_wlp0s2f1u4="dhcp"
dhcp_wlp0s2f1u4="nosendhost"

This file was changed afterwards by some program.

resolv.conf:
Code: Select all
# Generated by resolvconf
search fritz.box Heimnetzwerk
nameserver 192.168.XXX.XXX


blacklist.conf:
Code: Select all
# This file lists modules which will not be loaded by udev,
# not at coldplugging and not on hotplug events.
# Add your own entries to this file
# in the format "blacklist <name of module>"
# Some examples:
# evbug is a debug tool and should be loaded explicitly
blacklist evbug
# Autoloading eth1394 most of the time re-orders your network
# interfaces, and with buggy kernel 2.6.21, udev persistent-net
# is not able to rename these devices, so you get eth?_rename devices
# plus an exceeded 30sec boot timeout
blacklist eth1394
# You probably want this to not get the console beep loud on every tab :)
#blacklist pcspkr
# these drivers are very simple, the HID drivers are usually preferred
#blacklist usbmouse
#blacklist usbkbd
# Sometimes loading a framebuffer driver at boot gets the console black
#install pci:v*d*sv*sd*bc03sc*i* /bin/true
# hplip and cups 1.4+ use raw USB devices, so it requires usblp not be loaded
blacklist usblp
## make broadcom-sta happy
## <2012-12-08.
#blacklist ssb
#blacklist bcma
#blacklist brcmsmac
#blacklist b43
# make b43 happy (ditch broadcom-sta)
# 2012-12-08. Testing needed.
blacklist wl
# keep nvidia-drivers working, sorry nouveau
blacklist nouveau
# Known to cause kernel OOPS at boot
blacklist ite_cir
# enable WiFi
blacklist rt2800usb
HP-Pavilion ◆ AMD Athlon™ 64 Processor 4000+ ◆ GeForce 6150SE nForce 430 ◆ 1 GiB RAM
German Wiki translator ◆ Want to contribute on the wiki? Ask the Bureaucrats!
Please, mark solved threads ◆ Posts unread and unansweredPackage requests ◆ Sabayon XI with MATE
Ryuno-Ki
Technological Hen
 
Posts: 437
Joined: Mon Feb 27, 2012 22:15
Location: Southern Germany

Re: Sabayon Linux 11 Mate isn't installable [Solved]

Postby Ryuno-Ki » Tue Jul 02, 2013 0:46

wpa_passphrase is needed for the PSK line above (see the comment).

Oh, and once it is running as Daemon (that is, with -B instead of -dd), check, whether dhcpcd is running.

Glad I documented it back then =) Now my network is running =)
HP-Pavilion ◆ AMD Athlon™ 64 Processor 4000+ ◆ GeForce 6150SE nForce 430 ◆ 1 GiB RAM
German Wiki translator ◆ Want to contribute on the wiki? Ask the Bureaucrats!
Please, mark solved threads ◆ Posts unread and unansweredPackage requests ◆ Sabayon XI with MATE
Ryuno-Ki
Technological Hen
 
Posts: 437
Joined: Mon Feb 27, 2012 22:15
Location: Southern Germany


Return to Installer Issues - Calamares **Not for Package Manager Stuff**

Who is online

Users browsing this forum: No registered users and 2 guests