DBMS_PROFILER - only anonymous

I am trying to get over with DBMS_PROFILER, but I face a problem, that I can't get through.
I followed the tutorial on this page:
http://www.oracleflash.com/44/Write-fast-and-efficient-PLSQL---DBMS_PROFILER.html
and everything was fine till I did not change the user. When I run the profiler as the owner of the code, all the statistics are fine, but when I run those procedures as a different user (that of course has EXECUTE permissions) I can see only "ANONYMOUS" in profiler tables.
I found something looking around in the internet, and performed these actions:
- I granted execute permissions for user calling procedures,
- I also granted DEBUG permissions,
- I compiled procedures for DEBUG,
- I have checked that code is "INTERPRETED" and not "NATIVE",
- finally, calling user also have CREATE PROCEDURE privilege.
Nevertheless, it still doesn't work. The problem is I want to profile application, that is running code as a different user, so I cannot change that. Any ideas what should I do, and why it is not working?

Similar Messages

DBMS_PROFILER and ONLY ANONYMOUS

Hello,
I'm using 11gR2.
I followed this tutorial (http://www.oracle-base.com/articles/9i/dbms_profiler.php) to install and test dbms_profiler.
I'm surprised to get only information about ANONYMOUS BLOCK, although I should see information about DO_SOMETHING.
Can anyone give me help ?
Thanks.
SQL> select * from PLSQL_PROFILER_UNITS;
RUNID UNIT_NUMBER UNIT_TYPE
UNIT_OWNER UNIT_NAME UNIT_TIM
TOTAL_TIME SPARE1 SPARE2
1 1 ANONYMOUS BLOCK
<anonymous> <anonymous> 00/00/00
0

Sorry I forgot this part.
So I post everything again
c:\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN>sqlplus sys/manager@myserver:1521/mydb as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Mar. Mai 21 23:47:43 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ConnectÚ Ó :
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> @profload
Package crÚÚ.
Autorisation de privilÞges (GRANT) acceptÚe.
Synonyme crÚÚ.
BibliothÞque crÚÚe.
Corps de package crÚÚ.
Testing for correct installation
SYS.DBMS_PROFILER successfully loaded.
ProcÚdure PL/SQL terminÚe avec succÞs.
SQL>
SQL> CREATE USER profiler IDENTIFIED BY profiler DEFAULT TABLESPACE users QUOTA
UNLIMITED ON users;
CREATE USER profiler IDENTIFIED BY profiler DEFAULT TABLESPACE users QUOTA UNLIM
ITED ON users
ERREUR Ó la ligne 1 :
ORA-01920: nom utilisateur 'PROFILER' en conflit avec autre nom utilisateur ou
de r¶le
SQL> GRANT connect TO profiler;
Autorisation de privilÞges (GRANT) acceptÚe.
SQL>
SQL> CREATE PUBLIC SYNONYM plsql_profiler_runs FOR profiler.plsql_profiler_runs;
CREATE PUBLIC SYNONYM plsql_profiler_runs FOR profiler.plsql_profiler_runs
ERREUR Ó la ligne 1 :
ORA-00955: ce nom d'objet existe dÚjÓ
SQL> CREATE PUBLIC SYNONYM plsql_profiler_units FOR profiler.plsql_profiler_unit
s;
CREATE PUBLIC SYNONYM plsql_profiler_units FOR profiler.plsql_profiler_units
ERREUR Ó la ligne 1 :
ORA-00955: ce nom d'objet existe dÚjÓ
SQL> CREATE PUBLIC SYNONYM plsql_profiler_data FOR profiler.plsql_profiler_data;
CREATE PUBLIC SYNONYM plsql_profiler_data FOR profiler.plsql_profiler_data
ERREUR Ó la ligne 1 :
ORA-00955: ce nom d'objet existe dÚjÓ
SQL> CREATE PUBLIC SYNONYM plsql_profiler_runnumber FOR profiler.plsql_profiler_
runnumber;
CREATE PUBLIC SYNONYM plsql_profiler_runnumber FOR profiler.plsql_profiler_runnu
mber
ERREUR Ó la ligne 1 :
ORA-00955: ce nom d'objet existe dÚjÓ
SQL> connect profiler/profiler@myserver:1521/mydb
ConnectÚ.
SQL> @proftab
Table supprimÚe.
Table supprimÚe.
Table supprimÚe.
SÚquence supprimÚe.
Table crÚÚe.
Commentaire crÚÚ.
Table crÚÚe.
Commentaire crÚÚ.
Table crÚÚe.
Commentaire crÚÚ.
SÚquence crÚÚe.
SQL> GRANT SELECT ON plsql_profiler_runnumber TO PUBLIC;
Autorisation de privilÞges (GRANT) acceptÚe.
SQL> GRANT SELECT, INSERT, UPDATE, DELETE ON plsql_profiler_data TO PUBLIC;
Autorisation de privilÞges (GRANT) acceptÚe.
SQL> GRANT SELECT, INSERT, UPDATE, DELETE ON plsql_profiler_units TO PUBLIC;
Autorisation de privilÞges (GRANT) acceptÚe.
SQL> GRANT SELECT, INSERT, UPDATE, DELETE ON plsql_profiler_runs TO PUBLIC;
Autorisation de privilÞges (GRANT) acceptÚe.
SQL> CREATE OR REPLACE PROCEDURE do_something (p_times IN NUMBER) AS
2 l_dummy NUMBER;
3 BEGIN
4 FOR i IN 1 .. p_times LOOP
5 SELECT l_dummy + 1
6 INTO l_dummy
7 FROM dual;
8 END LOOP;
9 END;
10 /
ProcÚdure crÚÚe.
SQL> DECLARE
2 l_result BINARY_INTEGER;
3 BEGIN
4 l_result := DBMS_PROFILER.start_profiler(run_comment => 'do_something: '
|| SYSDATE);
5 do_something(p_times => 100);
6 l_result := DBMS_PROFILER.stop_profiler;
7 END;
8 /
ProcÚdure PL/SQL terminÚe avec succÞs.
SQL> SELECT runid,
2 run_date,
3 run_comment,
4 run_total_time
5 FROM plsql_profiler_runs
6 ORDER BY runid;
RUNID RUN_DATE
RUN_COMMENT
RUN_TOTAL_TIME
1 21/05/13
do_something: 21/05/13
30000000
SQL> SELECT u.runid,
2 u.unit_number,
3 u.unit_type,
4 u.unit_owner,
5 u.unit_name,
6 d.line#,
7 d.total_occur,
8 d.total_time,
9 d.min_time,
10 d.max_time
11 FROM plsql_profiler_units u
12 JOIN plsql_profiler_data d ON u.runid = d.runid AND u.unit_number =
d.unit_number
13 WHERE u.runid = 1
14 ORDER BY u.unit_number, d.line#;
RUNID UNIT_NUMBER UNIT_TYPE
UNIT_OWNER UNIT_NAME LINE#
TOTAL_OCCUR TOTAL_TIME MIN_TIME MAX_TIME
1 1 ANONYMOUS BLOCK
<anonymous> <anonymous> 1
0 0 0 0
1 1 ANONYMOUS BLOCK
<anonymous> <anonymous> 4
0 0 0 0
RUNID UNIT_NUMBER UNIT_TYPE
UNIT_OWNER UNIT_NAME LINE#
TOTAL_OCCUR TOTAL_TIME MIN_TIME MAX_TIME
1 1 ANONYMOUS BLOCK
<anonymous> <anonymous> 5
1 4631326 4631326 4631326
1 1 ANONYMOUS BLOCK
<anonymous> <anonymous> 6
RUNID UNIT_NUMBER UNIT_TYPE
UNIT_OWNER UNIT_NAME LINE#
TOTAL_OCCUR TOTAL_TIME MIN_TIME MAX_TIME
0 0 0 0
1 1 ANONYMOUS BLOCK
<anonymous> <anonymous> 7
0 0 0 0
SQL> set linesize 500
SQL> set pages 0
SQL> SELECT u.runid,
2 u.unit_number,
3 u.unit_type,
4 u.unit_owner,
5 u.unit_name,
6 d.line#,
7 d.total_occur,
8 d.total_time,
9 d.min_time,
10 d.max_time
11 FROM plsql_profiler_units u
12 JOIN plsql_profiler_data d ON u.runid = d.runid AND u.unit_number =
d.unit_number
13 WHERE u.runid = 1
14 ORDER BY u.unit_number, d.line#;
1 1 ANONYMOUS BLOCK <anonymous>
<anonymous> 1 0 0
0 0
1 1 ANONYMOUS BLOCK <anonymous>
<anonymous> 4 0 0
0 0
1 1 ANONYMOUS BLOCK <anonymous>
<anonymous> 5 1 4631326 4
631326 4631326
1 1 ANONYMOUS BLOCK <anonymous>
<anonymous> 6 0 0
0 0
1 1 ANONYMOUS BLOCK <anonymous>
<anonymous> 7 0 0
0 0

Run dbms_profiler by not owner

I run pl/sql-script with dbms_profiler calls, such this:
begin
dbms_profiler.start_profiler;
user1.proc1;
dbms_profiler.stop_profiler;
dbms_profiler.flush_data;
end;
it's ok if script runs under user1 !
I issued:
grant all on user1.proc to user2 with grant option;
garnt execute on dbms_profiler to user2;
and run sript under user2.
I have no oracle errors, but instead procedures and functions of user1 I see in plsql_profile_units table only records about ANONYMOUS BLOCKS
Say me, please, how I can to avoid this problem.
Michael

This thread has a similar issue.
DBMS_PROFILER and ONLY ANONYMOUS
What user OWNS the code you are profiling? What user is executing the profile gathering?
Are you sure that you have granted the necessary privs per the doc?
Do you meet this condition?
http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_profil.htm
>
Security Model
The profiler only gathers data for units for which a user has CREATE privilege; you cannot use the package to profile units for which EXECUTE ONLY access has been granted. In general, if a user can debug a unit, the same user can profile it. However, a unit can be profiled whether or not it has been compiled DEBUG. Oracle advises that modules that are being profiled should be compiled DEBUG, since this provides additional information about the unit in the database.
>
Does the user running the profiler have CREATE privilege on the code?

Run dbms_profiler for not owners

I run pl/sql-script with dbms_profiler calls, such this:
begin
dbms_profiler.start_profiler;
dbms_profiler.stop_profiler;
user1.proc1;
dbms_profiler.flush_data;
end;
it's ok if script runs under user1 !
I issued grant all on user1.proc to user2 with grant option;
and run sript under user2. There are only ANONYMOUS BLOCKS in plsql_profiler_units for thjis call !
Say me, please, how I can to avoid this problem.
Michael

the problem has solved

Anonymous access with named users

Hi!
I am trying to set up anonymous access with named users on EP6 SP9. I am using Database only as UME Data storage. I have applied the note #728106, since most of the content is html-pages on the KM.
I defined the UME settings ume.login.guest_user.uniqueids=anon01,anon02
ume.login.anonymous_user.mode=1
Restarted the server and attached user account into roles (which contain only anonymous content).
I then accessed the page /irj/portal/anonymous (or the longer version /irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.anonymous) and everything was fine. However I wasn't able to get the portal working with /irj/portal/anonymous?j_user=anon02. I always received Portal runtime error. From the logs I saw that the portal tried to access as user anon01.
When I changed the UME settings into
ume.login.guest_user.uniqueids=anon02,anon01
I was able to get the anon02 user account working, but not /irj/portal/anonymous?j_user=anon01. From the logs I saw that the portal tried to access as user anon02.
Both user account are using the same rule, portal desktop and framework page. I can see the correct (and different) TLN for each user only in the content are I see this error.
Any ideas?
Thanks,
Petri

I need to switch between two named anonymous users.
It works fine using http://<server>:<port>/irj/portal?j_user=<first_Guest_user>&j_password=<pwd_of_first_Guest_user>&login_submit=true
Then to switch to the other user I must do a log-off or close the browser and input the other url http://<server>:<port>/irj/portal?j_user=<second_Guest_user>&j_password=<pwd_of_second_Guest_user>&login_submit=true
I developed a servlet to switch the users using IAuthentication (method forceLogoffUser) and then redirect to the respective url. But when I call forceLogoffUser method I get a login screen and the script stop executing. Passing 'returnURL' parameter did not work.
Parameters:
req - HttpServletRequest
resp - HttpServletResponse
returnURL - url to use to logon again.
Is there a way to switch automaticaly between the two named anonymous users?

Only Guest users with Lync Web App

Hello!
I would like to allow just "Guest" users when they use the Lync Web App 2013. Is there anyway from Lync Server side to configure this?
Now it pops-up the user & password authentication, and I want to restrict the users to use only Anonymous access when they join to a Conference. Is this possible?
Thanks in advance! :D
Daniel

Hi,
You can change the publishing rule to block “Join using your corporate credentials” option. For details:
http://blogs.technet.com/b/lyncinternals/archive/2011/11/16/3462376.aspx
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Kent Huang
TechNet Community Support

Modifying Connectors for Receiving Internet Mail - Anonymous setting?

I have a mail reflector for my domain to deliver mail on an alternate port, other than 25 because my ISP blocks port 25. I have the following default receive connectors:
Default Client Font End Transport (FrontEnd Transport) - TLS, Basic, Integrated, Exchange users, port 587
Default Client Proxy (Hub Transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange Server Auth, Exchange Servers, Exchange users, port 465
Default Front End Transport (FrontEnd Transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange server auth, Exchange Servers, Legacy Exchange Servers, Anonymous Users, port 25
Default Hub Transport (Hub transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange Server Auth, Exchange Servers, Legacy, Exchange Users, port 2525
Default Outbound Proxy Frontend Transport (Frontend transport) TLS, Enable domain security, Basic, Offer basic after TLS, integrated, Exchange server auth, exchange servers, anonymous, port 717
Issue: When I initially had mail forwarded to port 2525, I received a mail delivery system message: host mail.skincdc.com[69.250.204.88] said: 530 5.7.1 .Client was not authenticated (in reply to MAIL FROM command).
I modified the “Default Hub Transport” connector to allow Anonymous Users in addition to what I already had selected in the security settings. Voila, email is delivered to my exchange server from external domains.
I wasn’t sure if adding Anonymous Users to this connector would pose any issues. In order to try an alternate port, I changed my registrar to port 2626 and created a new receive connector Hub Transport, with only Anonymous
Users and port 2626. I saw the initial connection in my TMG firewall logs, but mail never made it to my exchange server, and I wasn’t receiving the above error message right away as before. Disabling this new rule and modifying the firewall back to port 2525,
email immediately was delivered. So can I just leave my Default Hub Transport receive connector as is with the security settings and Anonymous set? Thanks.
Next….getting email to send out on a different port than 25 to external domains. Still having issues with this one.
-SK

Hi Slevin
According to your setup you would need to receive emails on different port apart from 25
You can do the following thing
1) Create a dedicated receive connector for your ISP domain
2) Grant relay permission only to your ISP subnet and IP ranges
3) Change the port to your desired number on which you need to receive emails from them
4) Disable the default receive connector since its not required anymore
So the mail-flow for inbound will be in the following type
Inbound
From Internet - Mails comes to your ISP - ISP delivers to your firewall on different port - then it comes to exchange server
Let me know if you have any confusions on this and i will be able to help you further
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Unknown /Private /Anonymous call blocking for specific extensions - CUCM 7.5.3

Hello ,
Can anyone explain is there anyways to block only anonymous/Private/Unknown calls to specific DN's in CUCM 7.5.3?
Regards,
Ram

Thanks for your revert....
Sorry ,Yes you are right we are using CUCM 7.1.3.32900-4 and we are not using H.323 gateway.
In that case ,I will look for system to be upgraded to 8.0 or later version to make it work as stated by brianmeade
Thanks,
Ram

Hostapd - client sees network but can't connect

I have a mobile phone Samsung S5230W with WiFi capability, and a laptop HP Compaq nx7400 with Broadcom BCM4311 wireless card. I'm trying to share an Internet connection between those two devices, but I can't because i receive 'authentication failed' message, even that the password is right -
##### hostapd configuration file ##############################################
# Empty lines and lines starting with # are ignored
# AP netdevice name (without 'ap' postfix, i.e., wlan0 uses wlan0ap for
# management frames); ath0 for madwifi
interface=wlan0
# In case of madwifi, atheros, and nl80211 driver interfaces, an additional
# configuration parameter, bridge, may be used to notify hostapd if the
# interface is included in a bridge. This parameter is not used with Host AP
# driver. If the bridge parameter is not set, the drivers will automatically
# figure out the bridge interface (assuming sysfs is enabled and mounted to
# /sys) and this parameter may not be needed.
# For nl80211, this parameter can be used to request the AP interface to be
# added to the bridge automatically (brctl may refuse to do this before hostapd
# has been started to change the interface mode). If needed, the bridge
# interface is also created.
bridge=br0
# Driver interface type (hostap/wired/madwifi/test/none/nl80211/bsd);
# default: hostap). nl80211 is used with all Linux mac80211 drivers.
# Use driver=none if building hostapd as a standalone RADIUS server that does
# not control any wireless/wired driver.
driver=nl80211
# hostapd event logger configuration
# Two output method: syslog and stdout (only usable if not forking to
# background).
# Module bitfield (ORed bitfield of modules that will be logged; -1 = all
# modules):
# bit 0 (1) = IEEE 802.11
# bit 1 (2) = IEEE 802.1X
# bit 2 (4) = RADIUS
# bit 3 (8) = WPA
# bit 4 (16) = driver interface
# bit 5 (32) = IAPP
# bit 6 (64) = MLME
# Levels (minimum value for logged events):
# 0 = verbose debugging
# 1 = debugging
# 2 = informational messages
# 3 = notification
# 4 = warning
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
# Dump file for state information (on SIGUSR1)
dump_file=/tmp/hostapd.dump
# Interface for separate control program. If this is specified, hostapd
# will create this directory and a UNIX domain socket 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 hostapd processes/interfaces can be run at the same time if more
# than one interface is used.
# /var/run/hostapd is the recommended directory for sockets and by default,
# hostapd_cli will use it when trying to connect with hostapd.
ctrl_interface=/var/run/hostapd
# 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 hostapd 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, hostapd is configured to use gid 0 (root). If you
# want to allow non-root users to use the contron 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.
# This variable can be a group name or gid.
#ctrl_interface_group=wheel
#ctrl_interface_group=0
##### IEEE 802.11 related configuration #######################################
# SSID to be used in IEEE 802.11 management frames
ssid=network
# Country code (ISO/IEC 3166-1). Used to set regulatory domain.
# Set as needed to indicate country in which device is operating.
# This can limit available channels and transmit power.
#country_code=US
# Enable IEEE 802.11d. This advertises the country_code and the set of allowed
# channels and transmit power levels based on the regulatory limits. The
# country_code setting must be configured with the correct country for
# IEEE 802.11d functions.
# (default: 0 = disabled)
#ieee80211d=0
# Operation mode (a = IEEE 802.11a, b = IEEE 802.11b, g = IEEE 802.11g,
# Default: IEEE 802.11b
hw_mode=g
# Channel number (IEEE 802.11)
# (default: 0, i.e., not set)
# Please note that some drivers (e.g., madwifi) do not use this value from
# hostapd and the channel will need to be configuration separately with
# iwconfig.
channel=1
# Beacon interval in kus (1.024 ms) (default: 100; range 15..65535)
beacon_int=100
# DTIM (delivery trafic information message) period (range 1..255):
# number of beacons between DTIMs (1 = every beacon includes DTIM element)
# (default: 2)
dtim_period=2
# Maximum number of stations allowed in station table. New stations will be
# rejected after the station table is full. IEEE 802.11 has a limit of 2007
# different association IDs, so this number should not be larger than that.
# (default: 2007)
max_num_sta=5
# RTS/CTS threshold; 2347 = disabled (default); range 0..2347
# If this field is not included in hostapd.conf, hostapd will not control
# RTS threshold and 'iwconfig wlan# rts <val>' can be used to set it.
rts_threshold=2347
# Fragmentation threshold; 2346 = disabled (default); range 256..2346
# If this field is not included in hostapd.conf, hostapd will not control
# fragmentation threshold and 'iwconfig wlan# frag <val>' can be used to set
# it.
fragm_threshold=2346
# Rate configuration
# Default is to enable all rates supported by the hardware. This configuration
# item allows this list be filtered so that only the listed rates will be left
# in the list. If the list is empty, all rates are used. This list can have
# entries that are not in the list of rates the hardware supports (such entries
# are ignored). The entries in this list are in 100 kbps, i.e., 11 Mbps = 110.
# If this item is present, at least one rate have to be matching with the rates
# hardware supports.
# default: use the most common supported rate setting for the selected
# hw_mode (i.e., this line can be removed from configuration file in most
# cases)
supported_rates=10 20 55 110 60 90 120 180 240 360 480 540
# Basic rate set configuration
# List of rates (in 100 kbps) that are included in the basic rate set.
# If this item is not included, usually reasonable default set is used.
#basic_rates=10 20
#basic_rates=10 20 55 110
#basic_rates=60 120 240
# Short Preamble
# This parameter can be used to enable optional use of short preamble for
# frames sent at 2 Mbps, 5.5 Mbps, and 11 Mbps to improve network performance.
# This applies only to IEEE 802.11b-compatible networks and this should only be
# enabled if the local hardware supports use of short preamble. If any of the
# associated STAs do not support short preamble, use of short preamble will be
# disabled (and enabled when such STAs disassociate) dynamically.
# 0 = do not allow use of short preamble (default)
# 1 = allow use of short preamble
#preamble=1
# Station MAC address -based authentication
# Please note that this kind of access control requires a driver that uses
# hostapd to take care of management frame processing and as such, this can be
# used with driver=hostap or driver=nl80211, but not with driver=madwifi.
# 0 = accept unless in deny list
# 1 = deny unless in accept list
# 2 = use external RADIUS server (accept/deny lists are searched first)
macaddr_acl=0
# Accept/deny lists are read from separate files (containing list of
# MAC addresses, one per line). Use absolute path name to make sure that the
# files can be read on SIGHUP configuration reloads.
#accept_mac_file=/etc/hostapd/hostapd.accept
#deny_mac_file=/etc/hostapd/hostapd.deny
# IEEE 802.11 specifies two authentication algorithms. hostapd can be
# configured to allow both of these or only one. Open system authentication
# should be used with IEEE 802.1X.
# Bit fields of allowed authentication algorithms:
# bit 0 = Open System Authentication
# bit 1 = Shared Key Authentication (requires WEP)
auth_algs=1
# Send empty SSID in beacons and ignore probe request frames that do not
# specify full SSID, i.e., require stations to know SSID.
# default: disabled (0)
# 1 = send empty (length=0) SSID in beacon and ignore probe request for
# broadcast SSID
# 2 = clear SSID (ASCII 0), but keep the original length (this may be required
# with some clients that do not support empty SSID) and ignore probe
# requests for broadcast SSID
ignore_broadcast_ssid=0
# TX queue parameters (EDCF / bursting)
# default for all these fields: not set, use hardware defaults
# tx_queue_<queue name>_<param>
# queues: data0, data1, data2, data3, after_beacon, beacon
# (data0 is the highest priority queue)
# parameters:
# aifs: AIFS (default 2)
# cwmin: cwMin (1, 3, 7, 15, 31, 63, 127, 255, 511, 1023)
# cwmax: cwMax (1, 3, 7, 15, 31, 63, 127, 255, 511, 1023); cwMax >= cwMin
# burst: maximum length (in milliseconds with precision of up to 0.1 ms) for
# bursting
# Default WMM parameters (IEEE 802.11 draft; 11-03-0504-03-000e):
# These parameters are used by the access point when transmitting frames
# to the clients.
# Low priority / AC_BK = background
#tx_queue_data3_aifs=7
#tx_queue_data3_cwmin=15
#tx_queue_data3_cwmax=1023
#tx_queue_data3_burst=0
# Note: for IEEE 802.11b mode: cWmin=31 cWmax=1023 burst=0
# Normal priority / AC_BE = best effort
#tx_queue_data2_aifs=3
#tx_queue_data2_cwmin=15
#tx_queue_data2_cwmax=63
#tx_queue_data2_burst=0
# Note: for IEEE 802.11b mode: cWmin=31 cWmax=127 burst=0
# High priority / AC_VI = video
#tx_queue_data1_aifs=1
#tx_queue_data1_cwmin=7
#tx_queue_data1_cwmax=15
#tx_queue_data1_burst=3.0
# Note: for IEEE 802.11b mode: cWmin=15 cWmax=31 burst=6.0
# Highest priority / AC_VO = voice
#tx_queue_data0_aifs=1
#tx_queue_data0_cwmin=3
#tx_queue_data0_cwmax=7
#tx_queue_data0_burst=1.5
# Note: for IEEE 802.11b mode: cWmin=7 cWmax=15 burst=3.3
# Special queues; normally not user configurable
#tx_queue_after_beacon_aifs=2
#tx_queue_after_beacon_cwmin=15
#tx_queue_after_beacon_cwmax=1023
#tx_queue_after_beacon_burst=0
#tx_queue_beacon_aifs=2
#tx_queue_beacon_cwmin=3
#tx_queue_beacon_cwmax=7
#tx_queue_beacon_burst=1.5
# 802.1D Tag (= UP) to AC mappings
# WMM specifies following mapping of data frames to different ACs. This mapping
# can be configured using Linux QoS/tc and sch_pktpri.o module.
# 802.1D Tag 802.1D Designation Access Category WMM Designation
# 1 BK AC_BK Background
# 2 - AC_BK Background
# 0 BE AC_BE Best Effort
# 3 EE AC_BE Best Effort
# 4 CL AC_VI Video
# 5 VI AC_VI Video
# 6 VO AC_VO Voice
# 7 NC AC_VO Voice
# Data frames with no priority information: AC_BE
# Management frames: AC_VO
# PS-Poll frames: AC_BE
# Default WMM parameters (IEEE 802.11 draft; 11-03-0504-03-000e):
# for 802.11a or 802.11g networks
# These parameters are sent to WMM clients when they associate.
# The parameters will be used by WMM clients for frames transmitted to the
# access point.
# note - txop_limit is in units of 32microseconds
# note - acm is admission control mandatory flag. 0 = admission control not
# required, 1 = mandatory
# note - here cwMin and cmMax are in exponent form. the actual cw value used
# will be (2^n)-1 where n is the value given here
wmm_enabled=1
# WMM-PS Unscheduled Automatic Power Save Delivery [U-APSD]
# Enable this flag if U-APSD supported outside hostapd (eg., Firmware/driver)
#uapsd_advertisement_enabled=1
# Low priority / AC_BK = background
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
# Note: for IEEE 802.11b mode: cWmin=5 cWmax=10
# Normal priority / AC_BE = best effort
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
# Note: for IEEE 802.11b mode: cWmin=5 cWmax=7
# High priority / AC_VI = video
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
# Note: for IEEE 802.11b mode: cWmin=4 cWmax=5 txop_limit=188
# Highest priority / AC_VO = voice
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
# Note: for IEEE 802.11b mode: cWmin=3 cWmax=4 burst=102
# Static WEP key configuration
# The key number to use when transmitting.
# It must be between 0 and 3, and the corresponding key must be set.
# default: not set
#wep_default_key=0
# The WEP keys to use.
# A key may be a quoted string or unquoted hexadecimal digits.
# The key length should be 5, 13, or 16 characters, or 10, 26, or 32
# digits, depending on whether 40-bit (64-bit), 104-bit (128-bit), or
# 128-bit (152-bit) WEP is used.
# Only the default key must be supplied; the others are optional.
# default: not set
#wep_key0=123456789a
#wep_key1="vwxyz"
#wep_key2=0102030405060708090a0b0c0d
#wep_key3=".2.4.6.8.0.23"
# Station inactivity limit
# If a station does not send anything in ap_max_inactivity seconds, an
# empty data frame is sent to it in order to verify whether it is
# still in range. If this frame is not ACKed, the station will be
# disassociated and then deauthenticated. This feature is used to
# clear station table of old entries when the STAs move out of the
# range.
# The station can associate again with the AP if it is still in range;
# this inactivity poll is just used as a nicer way of verifying
# inactivity; i.e., client will not report broken connection because
# disassociation frame is not sent immediately without first polling
# the STA with a data frame.
# default: 300 (i.e., 5 minutes)
#ap_max_inactivity=300
# Maximum allowed Listen Interval (how many Beacon periods STAs are allowed to
# remain asleep). Default: 65535 (no limit apart from field size)
#max_listen_interval=100
# WDS (4-address frame) mode with per-station virtual interfaces
# (only supported with driver=nl80211)
# This mode allows associated stations to use 4-address frames to allow layer 2
# bridging to be used.
#wds_sta=1
##### IEEE 802.11n related configuration ######################################
# ieee80211n: Whether IEEE 802.11n (HT) is enabled
# 0 = disabled (default)
# 1 = enabled
# Note: You will also need to enable WMM for full HT functionality.
ieee80211n=0
# ht_capab: HT capabilities (list of flags)
# LDPC coding capability: [LDPC] = supported
# Supported channel width set: [HT40-] = both 20 MHz and 40 MHz with secondary
# channel below the primary channel; [HT40+] = both 20 MHz and 40 MHz
# with secondary channel below the primary channel
# (20 MHz only if neither is set)
# Note: There are limits on which channels can be used with HT40- and
# HT40+. Following table shows the channels that may be available for
# HT40- and HT40+ use per IEEE 802.11n Annex J:
# freq HT40- HT40+
# 2.4 GHz 5-13 1-7 (1-9 in Europe/Japan)
# 5 GHz 40,48,56,64 36,44,52,60
# (depending on the location, not all of these channels may be available
# for use)
# Please note that 40 MHz channels may switch their primary and secondary
# channels if needed or creation of 40 MHz channel maybe rejected based
# on overlapping BSSes. These changes are done automatically when hostapd
# is setting up the 40 MHz channel.
# Spatial Multiplexing (SM) Power Save: [SMPS-STATIC] or [SMPS-DYNAMIC]
# (SMPS disabled if neither is set)
# HT-greenfield: [GF] (disabled if not set)
# Short GI for 20 MHz: [SHORT-GI-20] (disabled if not set)
# Short GI for 40 MHz: [SHORT-GI-40] (disabled if not set)
# Tx STBC: [TX-STBC] (disabled if not set)
# Rx STBC: [RX-STBC1] (one spatial stream), [RX-STBC12] (one or two spatial
# streams), or [RX-STBC123] (one, two, or three spatial streams); Rx STBC
# disabled if none of these set
# HT-delayed Block Ack: [DELAYED-BA] (disabled if not set)
# Maximum A-MSDU length: [MAX-AMSDU-7935] for 7935 octets (3839 octets if not
# set)
# DSSS/CCK Mode in 40 MHz: [DSSS_CCK-40] = allowed (not allowed if not set)
# PSMP support: [PSMP] (disabled if not set)
# L-SIG TXOP protection support: [LSIG-TXOP-PROT] (disabled if not set)
#ht_capab=[HT40-][SHORT-GI-20][SHORT-GI-40]
##### IEEE 802.1X-2004 related configuration ##################################
# Require IEEE 802.1X authorization
ieee8021x=0
# IEEE 802.1X/EAPOL version
# hostapd is implemented based on IEEE Std 802.1X-2004 which defines EAPOL
# version 2. However, there are many client implementations that do not handle
# the new version number correctly (they seem to drop the frames completely).
# In order to make hostapd interoperate with these clients, the version number
# can be set to the older version (1) with this configuration value.
#eapol_version=2
# Optional displayable message sent with EAP Request-Identity. The first \0
# in this string will be converted to ASCII-0 (nul). This can be used to
# separate network info (comma separated list of attribute=value pairs); see,
# e.g., RFC 4284.
#eap_message=hello
#eap_message=hello\0networkid=netw,nasid=foo,portid=0,NAIRealms=example.com
# WEP rekeying (disabled if key lengths are not set or are set to 0)
# Key lengths for default/broadcast and individual/unicast keys:
# 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits)
# 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits)
#wep_key_len_broadcast=5
#wep_key_len_unicast=5
# Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once)
#wep_rekey_period=300
# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if
# only broadcast keys are used)
eapol_key_index_workaround=0
# EAP reauthentication period in seconds (default: 3600 seconds; 0 = disable
# reauthentication).
#eap_reauth_period=3600
# Use PAE group address (01:80:c2:00:00:03) instead of individual target
# address when sending EAPOL frames with driver=wired. This is the most common
# mechanism used in wired authentication, but it also requires that the port
# is only used by one station.
#use_pae_group_addr=1
##### Integrated EAP server ###################################################
# Optionally, hostapd can be configured to use an integrated EAP server
# to process EAP authentication locally without need for an external RADIUS
# server. This functionality can be used both as a local authentication server
# for IEEE 802.1X/EAPOL and as a RADIUS server for other devices.
# Use integrated EAP server instead of external RADIUS authentication
# server. This is also needed if hostapd is configured to act as a RADIUS
# authentication server.
eap_server=0
# Path for EAP server user database
#eap_user_file=/etc/hostapd/hostapd.eap_user
# CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
#ca_cert=/etc/hostapd/hostapd.ca.pem
# Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
#server_cert=/etc/hostapd/hostapd.server.pem
# Private key matching with the server certificate for EAP-TLS/PEAP/TTLS
# This may point to the same file as server_cert if both certificate and key
# are included in a single file. PKCS#12 (PFX) file (.p12/.pfx) can also be
# used by commenting out server_cert and specifying the PFX file as the
# private_key.
#private_key=/etc/hostapd/hostapd.server.prv
# Passphrase for private key
#private_key_passwd=secret
# Enable CRL verification.
# Note: hostapd does not yet support CRL downloading based on CDP. Thus, a
# valid CRL signed by the CA is required to be included in the ca_cert file.
# This can be done by using PEM format for CA certificate and CRL and
# concatenating these into one file. Whenever CRL changes, hostapd needs to be
# restarted to take the new CRL into use.
# 0 = do not verify CRLs (default)
# 1 = check the CRL of the user certificate
# 2 = check all CRLs in the certificate path
#check_crl=1
# 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. This parameter is required if anonymous EAP-FAST is used.
# You can generate DH parameters file with OpenSSL, e.g.,
# "openssl dhparam -out /etc/hostapd/hostapd.dh.pem 1024"
#dh_file=/etc/hostapd/hostapd.dh.pem
# Configuration data for EAP-SIM database/authentication gateway interface.
# This is a text string in implementation specific format. The example
# implementation in eap_sim_db.c uses this as the UNIX domain socket name for
# the HLR/AuC gateway (e.g., hlr_auc_gw). In this case, the path uses "unix:"
# prefix.
#eap_sim_db=unix:/tmp/hlr_auc_gw.sock
# Encryption key for EAP-FAST PAC-Opaque values. This key must be a secret,
# random value. It is configured as a 16-octet value in hex format. It can be
# generated, e.g., with the following command:
# od -tx1 -v -N16 /dev/random | colrm 1 8 | tr -d ' '
#pac_opaque_encr_key=000102030405060708090a0b0c0d0e0f
# EAP-FAST authority identity (A-ID)
# A-ID indicates the identity of the authority that issues PACs. The A-ID
# should be unique across all issuing servers. In theory, this is a variable
# length field, but due to some existing implementations requiring A-ID to be
# 16 octets in length, it is strongly recommended to use that length for the
# field to provid interoperability with deployed peer implementations. This
# field is configured in hex format.
#eap_fast_a_id=101112131415161718191a1b1c1d1e1f
# EAP-FAST authority identifier information (A-ID-Info)
# This is a user-friendly name for the A-ID. For example, the enterprise name
# and server name in a human-readable format. This field is encoded as UTF-8.
#eap_fast_a_id_info=test server
# Enable/disable different EAP-FAST provisioning modes:
#0 = provisioning disabled
#1 = only anonymous provisioning allowed
#2 = only authenticated provisioning allowed
#3 = both provisioning modes allowed (default)
#eap_fast_prov=3
# EAP-FAST PAC-Key lifetime in seconds (hard limit)
#pac_key_lifetime=604800
# EAP-FAST PAC-Key refresh time in seconds (soft limit on remaining hard
# limit). The server will generate a new PAC-Key when this number of seconds
# (or fewer) of the lifetime remains.
#pac_key_refresh_time=86400
# EAP-SIM and EAP-AKA protected success/failure indication using AT_RESULT_IND
# (default: 0 = disabled).
#eap_sim_aka_result_ind=1
# Trusted Network Connect (TNC)
# If enabled, TNC validation will be required before the peer is allowed to
# connect. Note: This is only used with EAP-TTLS and EAP-FAST. If any other
# EAP method is enabled, the peer will be allowed to connect without TNC.
#tnc=1
##### IEEE 802.11f - Inter-Access Point Protocol (IAPP) #######################
# Interface to be used for IAPP broadcast packets
#iapp_interface=eth0
##### RADIUS client configuration #############################################
# for IEEE 802.1X with external Authentication Server, IEEE 802.11
# authentication with external ACL for MAC addresses, and accounting
# The own IP address of the access point (used as NAS-IP-Address)
own_ip_addr=127.0.0.1
# Optional NAS-Identifier string for RADIUS messages. When used, this should be
# a unique to the NAS within the scope of the RADIUS server. For example, a
# fully qualified domain name can be used here.
# When using IEEE 802.11r, nas_identifier must be set and must be between 1 and
# 48 octets long.
#nas_identifier=ap.example.com
# RADIUS authentication server
#auth_server_addr=127.0.0.1
#auth_server_port=1812
#auth_server_shared_secret=secret
# RADIUS accounting server
#acct_server_addr=127.0.0.1
#acct_server_port=1813
#acct_server_shared_secret=secret
# Secondary RADIUS servers; to be used if primary one does not reply to
# RADIUS packets. These are optional and there can be more than one secondary
# server listed.
#auth_server_addr=127.0.0.2
#auth_server_port=1812
#auth_server_shared_secret=secret2
#acct_server_addr=127.0.0.2
#acct_server_port=1813
#acct_server_shared_secret=secret2
# Retry interval for trying to return to the primary RADIUS server (in
# seconds). RADIUS client code will automatically try to use the next server
# when the current server is not replying to requests. If this interval is set,
# primary server will be retried after configured amount of time even if the
# currently used secondary server is still working.
#radius_retry_primary_interval=600
# Interim accounting update interval
# If this is set (larger than 0) and acct_server is configured, hostapd will
# send interim accounting updates every N seconds. Note: if set, this overrides
# possible Acct-Interim-Interval attribute in Access-Accept message. Thus, this
# value should not be configured in hostapd.conf, if RADIUS server is used to
# control the interim interval.
# This value should not be less 600 (10 minutes) and must not be less than
# 60 (1 minute).
#radius_acct_interim_interval=600
# Dynamic VLAN mode; allow RADIUS authentication server to decide which VLAN
# is used for the stations. This information is parsed from following RADIUS
# attributes based on RFC 3580 and RFC 2868: Tunnel-Type (value 13 = VLAN),
# Tunnel-Medium-Type (value 6 = IEEE 802), Tunnel-Private-Group-ID (value
# VLANID as a string). vlan_file option below must be configured if dynamic
# VLANs are used. Optionally, the local MAC ACL list (accept_mac_file) can be
# used to set static client MAC address to VLAN ID mapping.
# 0 = disabled (default)
# 1 = option; use default interface if RADIUS server does not include VLAN ID
# 2 = required; reject authentication if RADIUS server does not include VLAN ID
#dynamic_vlan=0
# VLAN interface list for dynamic VLAN mode is read from a separate text file.
# This list is used to map VLAN ID from the RADIUS server to a network
# interface. Each station is bound to one interface in the same way as with
# multiple BSSIDs or SSIDs. Each line in this text file is defining a new
# interface and the line must include VLAN ID and interface name separated by
# white space (space or tab).
#vlan_file=/etc/hostapd/hostapd.vlan
# Interface where 802.1q tagged packets should appear when a RADIUS server is
# used to determine which VLAN a station is on. hostapd creates a bridge for
# each VLAN. Then hostapd adds a VLAN interface (associated with the interface
# indicated by 'vlan_tagged_interface') and the appropriate wireless interface
# to the bridge.
#vlan_tagged_interface=eth0
##### RADIUS authentication server configuration ##############################
# hostapd can be used as a RADIUS authentication server for other hosts. This
# requires that the integrated EAP server is also enabled and both
# authentication services are sharing the same configuration.
# File name of the RADIUS clients configuration for the RADIUS server. If this
# commented out, RADIUS server is disabled.
#radius_server_clients=/etc/hostapd/hostapd.radius_clients
# The UDP port number for the RADIUS authentication server
#radius_server_auth_port=1812
# Use IPv6 with RADIUS server (IPv4 will also be supported using IPv6 API)
#radius_server_ipv6=1
##### WPA/IEEE 802.11i configuration ##########################################
# Enable WPA. Setting this variable configures the AP to require WPA (either
# WPA-PSK or WPA-RADIUS/EAP based on other configuration). For WPA-PSK, either
# wpa_psk or wpa_passphrase must be set and wpa_key_mgmt must include WPA-PSK.
# For WPA-RADIUS/EAP, ieee8021x must be set (but without dynamic WEP keys),
# RADIUS authentication server must be configured, and WPA-EAP must be included
# in wpa_key_mgmt.
# This field is a bit field that can be used to enable WPA (IEEE 802.11i/D3.0)
# and/or WPA2 (full IEEE 802.11i/RSN):
# bit0 = WPA
# bit1 = IEEE 802.11i/RSN (WPA2) (dot11RSNAEnabled)
wpa=3
# WPA pre-shared keys for WPA-PSK. This can be either entered as a 256-bit
# secret in hex format (64 hex digits), wpa_psk, or as an ASCII passphrase
# (8..63 characters) that will be converted to PSK. This conversion uses SSID
# so the PSK changes when ASCII passphrase is used and the SSID is changed.
# wpa_psk (dot11RSNAConfigPSKValue)
# wpa_passphrase (dot11RSNAConfigPSKPassPhrase)
#wpa_psk=---
wpa_passphrase=---
# Optionally, WPA PSKs can be read from a separate text file (containing list
# of (PSK,MAC address) pairs. This allows more than one PSK to be configured.
# Use absolute path name to make sure that the files can be read on SIGHUP
# configuration reloads.
#wpa_psk_file=/etc/hostapd/hostapd.wpa_psk
# Set of accepted key management algorithms (WPA-PSK, WPA-EAP, or both). The
# entries are separated with a space. WPA-PSK-SHA256 and WPA-EAP-SHA256 can be
# added to enable SHA256-based stronger algorithms.
# (dot11RSNAConfigAuthenticationSuitesTable)
wpa_key_mgmt=WPA-PSK
# Set of accepted cipher suites (encryption algorithms) for pairwise keys
# (unicast packets). This is a space separated list of algorithms:
# 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]
# Group cipher suite (encryption algorithm for broadcast and multicast frames)
# is automatically selected based on this configuration. If only CCMP is
# allowed as the pairwise cipher, group cipher will also be CCMP. Otherwise,
# TKIP will be used as the group cipher.
# (dot11RSNAConfigPairwiseCiphersTable)
# Pairwise cipher for WPA (v1) (default: TKIP)
wpa_pairwise=CCMP
# Pairwise cipher for RSN/WPA2 (default: use wpa_pairwise value)
rsn_pairwise=CCMP
# Time interval for rekeying GTK (broadcast/multicast encryption keys) in
# seconds. (dot11RSNAConfigGroupRekeyTime)
wpa_group_rekey=600
# Rekey GTK when any STA that possesses the current GTK is leaving the BSS.
# (dot11RSNAConfigGroupRekeyStrict)
#wpa_strict_rekey=1
# Time interval for rekeying GMK (master key used internally to generate GTKs
# (in seconds).
wpa_gmk_rekey=86400
# Maximum lifetime for PTK in seconds. This can be used to enforce rekeying of
# PTK to mitigate some attacks against TKIP deficiencies.
#wpa_ptk_rekey=600
# Enable IEEE 802.11i/RSN/WPA2 pre-authentication. This is used to speed up
# roaming be pre-authenticating IEEE 802.1X/EAP part of the full RSN
# authentication and key handshake before actually associating with a new AP.
# (dot11RSNAPreauthenticationEnabled)
rsn_preauth=1
# Space separated list of interfaces from which pre-authentication frames are
# accepted (e.g., 'eth0' or 'eth0 wlan0wds0'. This list should include all
# interface that are used for connections to other APs. This could include
# wired interfaces and WDS links. The normal wireless data interface towards
# associated stations (e.g., wlan0) should not be added, since
# pre-authentication is only used with APs other than the currently associated
# one.
#rsn_preauth_interfaces=eth0
# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e) is
# allowed. This is only used with RSN/WPA2.
# 0 = disabled (default)
# 1 = enabled
#peerkey=1
# ieee80211w: Whether management frame protection (MFP) is enabled
# 0 = disabled (default)
# 1 = optional
# 2 = required
#ieee80211w=0
# Association SA Query maximum timeout (in TU = 1.024 ms; for MFP)
# (maximum time to wait for a SA Query response)
# dot11AssociationSAQueryMaximumTimeout, 1...4294967295
#assoc_sa_query_max_timeout=1000
# Association SA Query retry timeout (in TU = 1.024 ms; for MFP)
# (time between two subsequent SA Query requests)
# dot11AssociationSAQueryRetryTimeout, 1...4294967295
#assoc_sa_query_retry_timeout=201
# okc: Opportunistic Key Caching (aka Proactive Key Caching)
# Allow PMK cache to be shared opportunistically among configured interfaces
# and BSSes (i.e., all configurations within a single hostapd process).
# 0 = disabled (default)
# 1 = enabled
#okc=1
##### IEEE 802.11r configuration ##############################################
# Mobility Domain identifier (dot11FTMobilityDomainID, MDID)
# MDID is used to indicate a group of APs (within an ESS, i.e., sharing the
# same SSID) between which a STA can use Fast BSS Transition.
# 2-octet identifier as a hex string.
#mobility_domain=a1b2
# PMK-R0 Key Holder identifier (dot11FTR0KeyHolderID)
# 1 to 48 octet identifier.
# This is configured with nas_identifier (see RADIUS client section above).
# Default lifetime of the PMK-RO in minutes; range 1..65535
# (dot11FTR0KeyLifetime)
#r0_key_lifetime=10000
# PMK-R1 Key Holder identifier (dot11FTR1KeyHolderID)
# 6-octet identifier as a hex string.
#r1_key_holder=000102030405
# Reassociation deadline in time units (TUs / 1.024 ms; range 1000..65535)
# (dot11FTReassociationDeadline)
#reassociation_deadline=1000
# List of R0KHs in the same Mobility Domain
# format: <MAC address> <NAS Identifier> <128-bit key as hex string>
# This list is used to map R0KH-ID (NAS Identifier) to a destination MAC
# address when requesting PMK-R1 key from the R0KH that the STA used during the
# Initial Mobility Domain Association.
#r0kh=02:01:02:03:04:05 r0kh-1.example.com 000102030405060708090a0b0c0d0e0f
#r0kh=02:01:02:03:04:06 r0kh-2.example.com 00112233445566778899aabbccddeeff
# And so on.. One line per R0KH.
# List of R1KHs in the same Mobility Domain
# format: <MAC address> <R1KH-ID> <128-bit key as hex string>
# This list is used to map R1KH-ID to a destination MAC address when sending
# PMK-R1 key from the R0KH. This is also the list of authorized R1KHs in the MD
# that can request PMK-R1 keys.
#r1kh=02:01:02:03:04:05 02:11:22:33:44:55 000102030405060708090a0b0c0d0e0f
#r1kh=02:01:02:03:04:06 02:11:22:33:44:66 00112233445566778899aabbccddeeff
# And so on.. One line per R1KH.
# Whether PMK-R1 push is enabled at R0KH
# 0 = do not push PMK-R1 to all configured R1KHs (default)
# 1 = push PMK-R1 to all configured R1KHs whenever a new PMK-R0 is derived
#pmk_r1_push=1
##### Neighbor table ##########################################################
# Maximum number of entries kept in AP table (either for neigbor table or for
# detecting Overlapping Legacy BSS Condition). The oldest entry will be
# removed when adding a new entry that would make the list grow over this
# limit. Note! WFA certification for IEEE 802.11g requires that OLBC is
# enabled, so this field should not be set to 0 when using IEEE 802.11g.
# default: 255
#ap_table_max_size=255
# Number of seconds of no frames received after which entries may be deleted
# from the AP table. Since passive scanning is not usually performed frequently
# this should not be set to very small value. In addition, there is no
# guarantee that every scan cycle will receive beacon frames from the
# neighboring APs.
# default: 60
#ap_table_expiration_time=3600
##### Wi-Fi Protected Setup (WPS) #############################################
# WPS state
# 0 = WPS disabled (default)
# 1 = WPS enabled, not configured
# 2 = WPS enabled, configured
#wps_state=0
# AP can be configured into a locked state where new WPS Registrar are not
# accepted, but previously authorized Registrars (including the internal one)
# can continue to add new Enrollees.
#ap_setup_locked=1
# Universally Unique IDentifier (UUID; see RFC 4122) of the device
# This value is used as the UUID for the internal WPS Registrar. If the AP
# is also using UPnP, this value should be set to the device's UPnP UUID.
# If not configured, UUID will be generated based on the local MAC address.
#uuid=12345678-9abc-def0-1234-56789abcdef0
# Note: If wpa_psk_file is set, WPS is used to generate random, per-device PSKs
# that will be appended to the wpa_psk_file. If wpa_psk_file is not set, the
# default PSK (wpa_psk/wpa_passphrase) will be delivered to Enrollees. Use of
# per-device PSKs is recommended as the more secure option (i.e., make sure to
# set wpa_psk_file when using WPS with WPA-PSK).
# When an Enrollee requests access to the network with PIN method, the Enrollee
# PIN will need to be entered for the Registrar. PIN request notifications are
# sent to hostapd ctrl_iface monitor. In addition, they can be written to a
# text file that could be used, e.g., to populate the AP administration UI with
# pending PIN requests. If the following variable is set, the PIN requests will
# be written to the configured file.
#wps_pin_requests=/var/run/hostapd_wps_pin_requests
# Device Name
# User-friendly description of device; up to 32 octets encoded in UTF-8
#device_name=Wireless AP
# 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=WAP
# 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=6-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
# Static access point PIN for initial configuration and adding Registrars
# If not set, hostapd will not allow external WPS Registrars to control the
# access point. The AP PIN can also be set at runtime with hostapd_cli
# wps_ap_pin command. Use of temporary (enabled by user action) and random
# AP PIN is much more secure than configuring a static AP PIN here. As such,
# use of the ap_pin parameter is not recommended if the AP device has means for
# displaying a random PIN.
#ap_pin=12345670
# Skip building of automatic WPS credential
# This can be used to allow the automatically generated Credential attribute to
# be replaced with pre-configured Credential(s).
#skip_cred_build=1
# Additional Credential attribute(s)
# This option can be used to add pre-configured Credential attributes into M8
# message when acting as a Registrar. If skip_cred_build=1, this data will also
# be able to override the Credential attribute that would have otherwise been
# automatically generated based on network configuration. This configuration
# option points to an external file that much contain the WPS Credential
# attribute(s) as binary data.
#extra_cred=hostapd.cred
# 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)
# Note: With wps_cred_processing=1, skip_cred_build should be set to 1 and
# extra_cred be used to provide the Credential data for Enrollees.
# wps_cred_processing=1 will disabled automatic updates of hostapd.conf file
# both for Credential processing and for marking AP Setup Locked based on
# validation failures of AP PIN. An external program is responsible on updating
# the configuration appropriately in this case.
#wps_cred_processing=0
# AP Settings Attributes for M7
# By default, hostapd generates the AP Settings Attributes for M7 based on the
# current configuration. It is possible to override this by providing a file
# with pre-configured attributes. This is similar to extra_cred file format,
# but the AP Settings attributes are not encapsulated in a Credential
# attribute.
#ap_settings=hostapd.ap_settings
# WPS UPnP interface
# If set, support for external Registrars is enabled.
#upnp_iface=br0
# Friendly Name (required for UPnP)
# Short description for end use. Should be less than 64 characters.
#friendly_name=WPS Access Point
# Manufacturer URL (optional for UPnP)
#manufacturer_url=http://www.example.com/
# Model Description (recommended for UPnP)
# Long description for end user. Should be less than 128 characters.
#model_description=Wireless Access Point
# Model URL (optional for UPnP)
#model_url=http://www.example.com/model/
# Universal Product Code (optional for UPnP)
# 12-digit, all-numeric code that identifies the consumer package.
#upc=123456789012
##### Multiple BSSID support ##################################################
# Above configuration is using the default interface (wlan#, or multi-SSID VLAN
# interfaces). Other BSSIDs can be added by using separator 'bss' with
# default interface name to be allocated for the data packets of the new BSS.
# hostapd will generate BSSID mask based on the BSSIDs that are
# configured. hostapd will verify that dev_addr & MASK == dev_addr. If this is
# not the case, the MAC address of the radio must be changed before starting
# hostapd (ifconfig wlan0 hw ether <MAC addr>). If a BSSID is configured for
# every secondary BSS, this limitation is not applied at hostapd and other
# masks may be used if the driver supports them (e.g., swap the locally
# administered bit)
# BSSIDs are assigned in order to each BSS, unless an explicit BSSID is
# specified using the 'bssid' parameter.
# If an explicit BSSID is specified, it must be chosen such that it:
# - results in a valid MASK that covers it and the dev_addr
# - is not the same as the MAC address of the radio
# - is not the same as any other explicitly specified BSSID
# Please note that hostapd uses some of the values configured for the first BSS
# as the defaults for the following BSSes. However, it is recommended that all
# BSSes include explicit configuration of all relevant configuration items.
#bss=wlan0_0
#ssid=test2
# most of the above items can be used here (apart from radio interface specific
# items, like channel)
#bss=wlan0_1
#bssid=00:13:10:95:fe:0b
I tried to access this network through the other device - same problem. What's the problem? Thanks in advance.

Retracting the question...no one seems to know.
LarryMcJ

ColdFusion 11 Scheduled Task & IIS 7.5

I have a scheduled task registered in ColdFusion 11 Admin console. ColdFusion 11 is hosted over IIS 7.5. The schedule task is to run 1 perticular file from sub application of the main app. After upgrading application from ColdFusion 9 to ColdFusion 11, scheduled task stopped working.
Note that, on IIS, main App has "Anonymous Authentication - Disabled" and "Windows Authentication - Enabled" ...
While for sub app (which is being called by scheduled task) has "Anonymous Authentication - Enabled" and "Windows Authentication - Disabled".
Moreover, when I try to run the scheduled task manually, it shows "Authentication falure" error in log file as
HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers.
Any help would be greatly appriciated.
Thank you.

I've been fighting the identical problem since upgrading from CF8 on Windows Server 2008R2 with SSL enabled. The main CF application's folder is set for Windows Authentication This is happening on two different test servers- one running CF10 and the other running CF11, both of which had been running CF8 tasks with no problems. IIS settings for the subfolder with the scheduled task have only Anonymous authentication enabled (which is set to use the Application Pool identity that the Application Pool's identity is set to). I've set the file system permissions to allow Everybody, as well as IUSR, on the .CFM in question, and have tried using both HTTP and HTTPS forms of the URL in the scheduled task settings.
I can use the same HTTP/HTTPS URL in a browser directly (without authenticating to the server's application first) and the .CFM runs flawlessly. The CF http.log file shows Status Code=401, and saving the scheduled task output shows "IIS 7.0 Detailed Error - 401.2 - Unauthorized". What has changed in CF10 and CF11 if the underlying IIS server settings that worked before haven't changed?
Thanks,
Myron

File transfer problem during ISE 1.3 upgrade

We have problem running the upgrade command:
iseadm01/admin# application upgrade cleanup
Application upgrade preparation directory cleanup successful
iseadm01/admin# application upgrade prepare ise-upgradebundle-1.2.x-to-1.3.0.876.x86_64.tar.gz FTP
Getting bundle to local machine...
% File transfer error
iseadm01/admin#
The sniffertrace shows that the ISE 1.2 is sending TCP RST after about 30MB file transfer. If we run the command serveral times, it stops exactly after the same amount of transferred bytes.
The disk utilazation looks OK:
iseadm01/admin# dir
Directory of disk:/
      16384 Sep 18 2014 15:55:48 lost+found/
           Usage for disk: filesystem
                  172761088 bytes total used
                14275047424 bytes free
                15234142208 bytes available
iseadm01/admin#
iseadm01/admin# dir
Directory of disk:/
      16384 Sep 18 2014 15:55:48 lost+found/
           Usage for disk: filesystem
                  172761088 bytes total used
                14275047424 bytes free
                15234142208 bytes available
iseadm01/admin#
We have Another ISE (monitor node) and the problem is excact the same on that node.
Thanks

On FileZila click on the User Accounts Icon. The dialog box will show you defined users. By default only anonymous is created.
So you need to create a local ftp username and passowrd. Then assign it a home directory under shared folders. This will be the dfault location a remote clietn will look for files and where you would find the ISE upgrade package, for example.
See following screenshot....

Users quota- not sending email windows 2008 server r2

I have setup quotas in File Server Resources Manager, when I test sending emails, it works ok I get email from FSRM, but users doesn't get email when they reach quota even when they are on 100%. When I check Source Template Limit for each user I can
see that system sends email, but users not getting any email.
All users have email set in User Properties in AD.
What can be wrong?
I never left an open problem....I search, dig and ask, until it's solved....

Hi,
What external mail server do you use? Please try to create a receive connector with basic authentication only & anonymous permission on the mail server.
For more detailed information, you could refer to the links below
SMTP authentication and FSRM
http://social.technet.microsoft.com/Forums/windowsserver/en-us/b1c40455-a337-422b-bedd-597beae13969/smtp-authentication-and-fsrm
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SPA9xx Phone do not show correctly the CID info

Hi,
After some tests, I have found a bug in the SPA9xx phones:
I have connected a SPA962 and some SPA942 to an Asterisk system.
I configured some queues, with which I identify the incoming call and set a TAG in the Caller ID.
Its for identifying from which city the call is coming from :
SIP call -----> Asterisks---->Queue ---> Tag "LYON"-------------------Agents(SPAxxx) Phones.
An incoming call shows on display the phones :
"LYON 0123456789"
This is OK.
But when there is an incoming call with "anonymous", I can see in the trace that SIP sent's "LYON anonymous" to the phones,
but they will show only "Anonymous Call" and the TAG "LYON" is lost/overwritten.
When I use a softphone, like Xlite, it shows "LYON anonymous" as CallerID.
Attached the trace and syslog where you can clearly see the problem.

Dear Mr Montilla,
I disagree, its not a feature request, its a BUG !
To confirm I used a SNOM320 to see if it has the same behavior.
That's not the case because the SNOM worked as it should and showed me the complete information's !
It works also with softphones like Zoiper or Xlite.
So only the SPA9xx phones REPLACE, if there is an anonymous incoming call ALL supplementary information's by "ANONYMOUS".
Attached the photos of the displays from the SPA962 and the SNOM320 of the same incomming call.
I think the problem is quit clear. Its a bug.
I have around 48 SPA962 and 942 running on a Asterisk system and this bug blocks the whole deployment, as this function is a basic request this customer.
So I need ASAP a bugfix for this problem.
Thanks for your quick help in advance.

Exchange management console initialization failure

Hi all.
One of my clients SBS 2011 standard servers downloaded some updates yesterday & since then both the Exchange Management Console & Shell fail to open. In addition mail to the smart phones no longer works. Everything else seems ok. Mail is delivered
& received via Outlook, all services are running. I have tried uninstalling the updates, but the Microsoft C++2010 Redistributable that was installed yesterday does not appear in the list of updates to uninstall. Only one of these updates is listed
which is from 2012. This is the first part of the problem to resolving this issue. There are no "hidden updates" I am sure that this update was the most likely to be causing this issue. Any clues as to how to remove this update?
The Exchange Management Console error is below.
Connecting to the remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.
Exchange Management Shell errors.
Connecting to the remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure.
Connecting to the remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response
from the destination computer. The content type is absent or invalid.
I have checked the settings as per the following possible solutions.
https://support.microsoft.com/kb/2027063?wa=wsignin1.0
I have added & removed & added the WinRM IIS extension & ran WinRM Quickconfig
I have checked Powershell directory in IIS on the problem server. Make sure SSL is not required. Allow
only Anonymous access.
I have run this command from the Windows Powershell - note the warning
set-user yourusername -remotepowershellenabled:$true
Warning: The command completed successfully but no settings of “domain.local/MyBusiness/Users/SBSUsers/User” have
been modified
Checked the ExchangeInstallPath environment variable
Checked the application pool settings in IIS are set to Local System Identity
About the only item I have not tries is to remove & reinstall the PowerShell directory. I will do this over the weekend.
This server has been in operation for almost 3 years without an issue. Microsoft updates come down & now I have been working on the issue for about 6 hours. Any other ideas?
Regards, Scott

Explore Powershell Virutal Directory , what is the size of Web.config file?
What happens if you browse Powershell VD ?
Check the Powershell Application Pool
Make sure Enable 32 bit application under advance settings is set to FALSE
Perform an IISRESET
Also refer to -
http://blogs.technet.com/b/whats_on_scotts_mind_today/archive/2012/12/07/exchange-2010-unable-to-open-exchange-management-console-initialization-failed.aspx
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Migrating Webview Reports to CUIC

Hello,
Everyone is running around with this problem since cisco stops the webview , the CUIC is a great reporting solution but the only thing CUIC is weak with is the stock reports , not only they don't include all the reports mostly needed but they can only be found in the half hour intervals (no consolidated reports)
After months of working and developing i finally found out a way to migrate the webview reports to CUIC in a database query (not only anonymous block) and here are the detailed steps:
1- If you have a webview server (version 8.0 preferred or earlier) go to drive c: then folder icm\custom (if you don't a ZIP file is attached)
2- Under the custom you will find folders for each type of reports (agent per team , agent per agent, calltype , skill group , etc.....)
3- Choose whatever report you want to migrate to CUIC (in this scenario we will choose the calltype22 report)
4- The file that is located under the caltyp folder is name caltyp22.srd
5- open the file using notepad
6- when you open the file you will find along list of data , you should ignore most of it , just search for (retrieve=") , after that you will find a SELECT , copy all the data from there until you reach (" arguments=) (of course don't copy the " arguments=)
7- paste the copied data into a new notepad , search for all the values (112) (it is usually beside the Datetime parameter) replace it with 101
8- delete everything that has the : like this
Call_Type.CallTypeID in ( :list_calltype ) AND
CTHH.DateTime >= :start_date AND
CTHH.DateTime <= :end_date
Any sql command that has the : remove it completely.
9- Copy the updated data and create a new report definition
10- use database query and historical datasource (because the report we are doing now is historical , if you decided to migrate a realtime use the real-time datasource)
11- paste the updated notepad file into query .
12- at the end of the page there is a create fields button, click on it and the report should be verified correctly and the fields are created.
13- after that go the next tab which is the fields , search for calltype (in other reports you may need the agent team , agent, skill group, etc... search for the ID value not the value it self) , click on the edit properties , below beside the value list choose the call types from the drop down menu and click on update.
14- go to the last tab which is the properties , choose the Key Criteria Field to be the call type (call type) and click on the historical checkbox below it , choose from Historical Key Field the Datetime value then click on save at the top of the report definition.
Now your report definition is ready , all what you have to do is to go and create a new report and assign this report definition to it , be aware that in case of creating a new report , all the fields will be visible so go to the edit view and edit the report with only the need values for you.
I hope this helps.
Amer R. Sha'er

Hello,
Sorry, i forgot to add that the above way is only possible with a CUIC premium version (standard won't have this option)
also the data for the times (like average handle and ASA) would be in in normall decimal (like 425) so all what you have to do is to go to the report definition , choose the fields tab , search for asa , click on edit formating , in the fromat field choose time (HH:MM:SS) value , also for the SL if you need , you may also change it to the % in the same way.
One last thing , if you need a footer (which is the total, average or max value) in the summary raw , edit the footer in the same place under the format to the needed value.
Hope this helps.
Amer Sha'er

DBMS_PROFILER - only anonymous

Similar Messages

Maybe you are looking for