Path to /i/ prefix
What is a physical path to the /i/ prefix on a Linux system in Oracle XE?
Thanks,
Art
>> So, if I were to put my pictures in this directory via FTP they would use some of my (4GB) database space, right?
Absolutely. 100% correct.
Joel
Similar Messages
-
What are the benefits of id prefixes
Can anyone tell me what the benefits are of the prefix you can provide for portal content (folders, iviews, pages, etc.)
If there is any benefit of prefixes, what would be the best strategy?
Giving every folder in the structure the prefix? Giving only the endcomponent the prefix? Giving only the rootfolder the prefix? etc.
Thanks in advance.
JurjenHi there,
exactly the same problem here. The Naming Convention Service offers the ability to use the path as ID-Prefix. All in all a good idea but at the moment the service doesn't really help because it concatenates all ID-Prefixes from all parent objects which leads to a very long Folder-Prefix.
I would expect the Naming Convention Service to do it in another way. Here an example:
In the PCD one creates a Folder with a Subfolder that also contains a subfolder. The ID's then should be:
portal_content/folder1/
portal_content/folder1/subfolder1/
portal_content/folder1/subfolder1/subsubfolder1/
At the moment the Naming Convention Service sets the following ID's which leads to very long texts:
portal_content/folder1/
portal_content/folder1/folder1.subfolder1
portal_content/folder1/folder1.subfolder1/folder1.subfolder1.subsubfolder1/
Is this really the way the Naming Convention Service is designed to be? -
Specific path selection in E-BGP
I have two routers ASR 9K platform with the image file is "disk0:asr9k-os-mbi-4.3.4.sp4-1.0.0/0x100305/mbiasr9k-rsp3.vm"
Primary link b/w Router 1 and 2 :
Router 1 ------> Directly connected with 30G to Router 2 on a bundle ( Neither ISIS nor BGP running on this link )
Router 2 ------> Directly connected with 30G to Router 1 on a bundle ( Neither ISIS nor BGP running on this link )
Secondary link b/w Router 1 and 2 :
Router 1 and 2 is connected on TenGig /0/0/0/4.451 and I am using secondary link for both Internet and Private (VPN) traffic as this link is running ISIS as my IGP and IPv4/v6 Unicast and IPv4/v6 Labeeled Unicast Peering using this interface
My query is how can I seggregate my IPv4/v6 Unicast Traffic in secondary link and IPv4/v6 Labelled Unicast traffic in my Primary link
Please suggest how can I do in BGP to select one path for Internet Prefixes and another for Private Prefixes
Many thanks in advance
Sankar.Hi,
The OSPF traffic would not pass through the VSL link. The path would directly go from each 4500 to the 3945 (Equal cost load balancing). I think, the 3900 series supports Etherchannel, if this is the case you can also create a L-3 Portchannel between the VSS and 3945 router. This way you use one /30 instead of 2 and you still have redundancy. For BGP, I would do one peering with Loopbacks.
HTH -
Show command to see advertised AS-Path, ASR9K XR 4.3.2
Question for ASR9010 running 4.3.2
Anyone know of a command that will show the as-path for advertised prefixes (my own) besides
show bgp advertised neighbor <ipaddr>
The output from above command gives the information, but is not very concise. For some reason the command:
show bgp neighbor <addr> advertsed-routes
does not show as-path.
Thanks,
Timi don't know if is this you looking for
RP/0/RSP0/CPU0:router# show bgp advertised neighbor 10.0.101.4 summary
Network Next Hop From AS Path
1.1.1.0/24 10.0.101.1 10.0.101.1 2 3 222 333 444 555 i -
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 -
How to configure multiple outgoing interfaces + NAT + PfR
Hello,
I have the following config running on Cisco2851.
Five interfaces (four ADSL and one LAN 10Mb/s) connected to Internet using pppoe.
Local policy is used to make working route tracking.
The PfR also configured to load balance traffic coming from LAN to Internet.
PAT is also configured with "oer" keyword at the end of string to not relocate working translations.
But the router is not performing good. :-(
After investigation I found that the selection of the exit interface and setting source ip for
NAT is not synchronized. The provider's router just drops the incoming packet due to uRPF check.
Also, the selection of the exit interface is not PFR aware (mode select-exit best) during
NAT session setup, and router selects one of the possible exit interfaces randomly.
I have two questions:
1. How to make synchronization of NAT and Routing to build matching pair of Out_IP=Out_Interface and make my setup working?
2. How to select the less loaded interface during setup of NAT phase and Routing phase and really involve PfR?
Actually, these two questions is just my one requirement: during setup of NAT session, I need
to find less loaded interface (PfR should check current rx/tx load), select it, and keep it untouched.
Thanks,
Sergey
Config:
version 15.1
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname bif
boot-start-marker
boot system flash:c2800nm-adventerprisek9-mz.151-4.M8.bin
boot-end-marker
enable secret 5 $1$3ggj$huERPVt0luOX6qo6
no aaa new-model
crypto pki token default removal timeout 0
dot11 syslog
no ip source-route
ip cef
no ip domain lookup
ip domain name zzz.mgm
no ipv6 cef
multilink bundle-name authenticated
key chain PFR
key 0
key-string 7 107E2F2B
voice-card 0
pfr master
logging
border 192.168.254.254 key-chain PFR
interface Dialer5 external
interface Dialer4 external
interface Dialer3 external
interface Dialer2 external
interface Dialer1 external
interface GigabitEthernet0/0 internal
mode select-exit best
pfr border
logging
local Loopback0
master 192.168.254.254 key-chain PFR
license udi pid CISCO2851 sn FCZ0929
username se privilege 15 secret 5 $1$DUbm$RuZKP8X.19uBtm21
username ru privilege 15 secret 5 $1$1V.h$iotp/bjhUg4ho93d
redundancy
ip ssh version 2
track 1 ip sla 1 reachability
delay down 30 up 15
track 2 ip sla 2 reachability
delay down 30 up 15
track 3 ip sla 3 reachability
delay down 30 up 15
track 4 ip sla 4 reachability
delay down 30 up 15
track 5 ip sla 5 reachability
delay down 30 up 15
interface Loopback0
ip address 192.168.254.254 255.255.255.255
interface GigabitEthernet0/0
description ### LAN ###
ip address 192.168.68.1 255.255.255.0
no ip redirects
no ip proxy-arp
ip flow ingress
ip nat inside
ip virtual-reassembly in
duplex auto
speed auto
interface GigabitEthernet0/1
description ### WDSL link to Dialer 5 ###
no ip address
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 5
interface ATM0/0/0
description ### DSL link 1 to Dialer 1 ###
no ip address
no atm ilmi-keepalive
shutdown
pvc 1/32
pppoe-client dial-pool-number 1
interface ATM0/1/0
description ### DSL link 2 to Dialer 2 ###
no ip address
no atm ilmi-keepalive
pvc 1/32
pppoe-client dial-pool-number 2
interface ATM0/2/0
description ### DSL link 3 to Dialer 3 ###
no ip address
no atm ilmi-keepalive
pvc 1/32
pppoe-client dial-pool-number 3
interface ATM0/3/0
description ### DSL link 4 to Dialer 4 ###
no ip address
no atm ilmi-keepalive
pvc 1/32
pppoe-client dial-pool-number 4
interface GigabitEthernet1/0
description ### Virtual interface to NME-16ES-1G-P ###
ip address 192.168.254.253 255.255.255.254
interface Dialer1
description ### Dialer for line 1 ###
bandwidth 224
bandwidth receive 1728
ip address negotiated
ip mtu 1492
ip nat outside
ip virtual-reassembly in
encapsulation ppp
ip tcp adjust-mss 1452
load-interval 30
dialer pool 1
ppp authentication chap callin
ppp chap hostname
ppp chap password
no cdp enable
interface Dialer2
description ### Dialer for line 2 ###
bandwidth 224
bandwidth receive 1728
ip address negotiated
ip mtu 1492
ip flow ingress
ip nat outside
ip virtual-reassembly in
encapsulation ppp
ip tcp adjust-mss 1452
dialer pool 2
ppp authentication chap callin
ppp chap hostname
ppp chap password
no cdp enable
interface Dialer3
description ### Dialer for line 3 ###
bandwidth 224
bandwidth receive 1728
ip address negotiated
ip mtu 1492
ip flow ingress
ip nat outside
ip virtual-reassembly in
encapsulation ppp
ip tcp adjust-mss 1452
dialer pool 3
ppp authentication chap callin
ppp chap hostname
ppp chap password
no cdp enable
interface Dialer4
description ### Dialer for line 4 ###
bandwidth 224
bandwidth receive 1728
ip address negotiated
ip mtu 1492
ip flow ingress
ip nat outside
ip virtual-reassembly in
encapsulation ppp
ip tcp adjust-mss 1452
dialer pool 4
ppp authentication chap callin
ppp chap hostname
ppp chap password
no cdp enable
interface Dialer5
description ### Dialer for WDSL line ###
bandwidth 10000
bandwidth receive 10001
ip address negotiated
ip mtu 1492
ip flow ingress
ip nat outside
ip virtual-reassembly in
encapsulation ppp
ip tcp adjust-mss 1452
load-interval 30
dialer pool 5
ppp authentication chap callin
ppp chap hostname
ppp chap password
no cdp enable
ip local policy route-map LOCAL-PBR
no ip forward-protocol nd
no ip http server
no ip http secure-server
ip nat inside source route-map NAT1 interface Dialer1 overload oer
ip nat inside source route-map NAT2 interface Dialer2 overload oer
ip nat inside source route-map NAT3 interface Dialer3 overload oer
ip nat inside source route-map NAT4 interface Dialer4 overload oer
ip nat inside source route-map NAT5 interface Dialer5 overload oer
ip nat inside source static tcp 192.168.68.160 22 $$$Dialer5-IP$$$ 2222 extendable
ip nat inside source static tcp 192.168.68.160 22 $$$Dialer2-IP$$$ 2222 extendable
ip nat inside source static tcp 192.168.68.160 22 $$$Dialer3-IP$$$ 2222 extendable
ip nat inside source static tcp 192.168.68.160 22 $$$Dialer4-IP$$$ 2222 extendable
ip nat inside source static tcp 192.168.68.230 21 $$$Dialer1-IP$$$ 21 extendable
ip nat inside source static tcp 192.168.68.160 25 $$$Dialer1-IP$$$ 25 extendable
ip nat inside source static tcp 192.168.68.22 143 $$$Dialer1-IP$$$ 143 extendable
ip nat inside source static tcp 192.168.68.22 443 $$$Dialer1-IP$$$ 443 extendable
ip nat inside source static tcp 192.168.68.160 22 $$$Dialer1-IP$$$ 2222 extendable
ip route 0.0.0.0 0.0.0.0 Dialer1 track 1
ip route 0.0.0.0 0.0.0.0 Dialer2 track 2
ip route 0.0.0.0 0.0.0.0 Dialer3 track 3
ip route 0.0.0.0 0.0.0.0 Dialer4 track 4
ip route 0.0.0.0 0.0.0.0 Dialer5 track 5
ip sla 1
icmp-echo 8.8.8.8 source-ip $$$Dialer1-IP$$$
timeout 1000
frequency 5
ip sla schedule 1 life forever start-time now
ip sla 2
icmp-echo 8.8.8.8 source-ip $$$Dialer2-IP$$$
timeout 1000
frequency 5
ip sla schedule 2 life forever start-time now
ip sla 3
icmp-echo 8.8.8.8 source-ip $$$Dialer3-IP$$$
timeout 1000
frequency 5
ip sla schedule 3 life forever start-time now
ip sla 4
icmp-echo 8.8.8.8 source-ip $$$Dialer4-IP$$$
timeout 1000
frequency 5
ip sla schedule 4 life forever start-time now
ip sla 5
icmp-echo 8.8.8.8 source-ip $$$Dialer5-IP$$$
timeout 1000
frequency 5
ip sla schedule 5 life forever start-time now
access-list 100 permit ip any any
access-list 101 permit ip host $$$Dialer1-IP$$$ any
access-list 102 permit ip host $$$Dialer2-IP$$$ any
access-list 103 permit ip host $$$Dialer3-IP$$$ any
access-list 104 permit ip host $$$Dialer4-IP$$$ any
access-list 105 permit ip host $$$Dialer5-IP$$$ any
access-list 199 permit ip 192.168.68.0 0.0.0.255 any
route-map LOCAL-PBR permit 10
match ip address 101
set interface Dialer1
route-map LOCAL-PBR permit 20
match ip address 102
set interface Dialer2
route-map LOCAL-PBR permit 30
match ip address 103
set interface Dialer3
route-map LOCAL-PBR permit 40
match ip address 104
set interface Dialer4
route-map LOCAL-PBR permit 50
match ip address 105
set interface Dialer5
route-map LOCAL-PBR permit 100
match ip address 100
set global
route-map NAT3 permit 10
match ip address 199
match interface Dialer3
route-map NAT2 permit 10
match ip address 199
match interface Dialer2
route-map NAT1 permit 10
match ip address 199
match interface Dialer1
route-map NAT5 permit 10
match ip address 199
match interface Dialer5
route-map NAT4 permit 10
match ip address 199
match interface Dialer4
control-plane
mgcp profile default
line con 0
line aux 0
line 66
no activation-character
no exec
transport preferred none
transport input all
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
line vty 0 4
session-timeout 15
login local
transport input all
line vty 5 15
session-timeout 15
login local
transport input all
scheduler allocate 20000 1000
end
Show ip route:
sh ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
Known via "static", distance 1, metric 0 (connected), candidate default path
Routing Descriptor Blocks:
directly connected, via Dialer5
Route metric is 0, traffic share count is 1
* directly connected, via Dialer3
Route metric is 0, traffic share count is 1
directly connected, via Dialer4
Route metric is 0, traffic share count is 1
directly connected, via Dialer2
Route metric is 0, traffic share count is 1
Log:
*Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, Stateful Inspection(5), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, Ingress-NetFlow(21), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, Virtual Fragment Reassembly(25), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, Access List(31), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, Virtual Fragment Reassembly After IPSec Decryption(39), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: IP: s=192.168.68.2 (GigabitEthernet0/0), d=8.8.4.4, len 66, input feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, TCP Adjust MSS(82), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: FIBipv4-packet-proc: route packet from GigabitEthernet0/0 src 192.168.68.2 dst 8.8.4.4
*Apr 16 07:04:18.103: FIBfwd-proc: Default:0.0.0.0/0 process level forwarding
*Apr 16 07:04:18.103: FIBfwd-proc: depth 0 first_idx 3 paths 4 long 0(0)
*Apr 16 07:04:18.103: FIBfwd-proc: try path 3 (of 4) v4-ap-Dialer5 first short ext 0(-1)
*Apr 16 07:04:18.103: FIBfwd-proc: v4-ap-Dialer5 valid
*Apr 16 07:04:18.103: FIBfwd-proc: Dialer5 no nh type 3 - deag
*Apr 16 07:04:18.103: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Dialer5 nh none deag 1 chg_if 0 via fib 0 path type attached prefix
*Apr 16 07:04:18.103: FIBfwd-proc: packet routed to Dialer5 p2p(0)
*Apr 16 07:04:18.103: FIBipv4-packet-proc: packet routing succeeded
*Apr 16 07:04:18.103: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Dialer5 nh none uhp 1 deag 0 ttlexp 0
*Apr 16 07:04:18.103: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Dialer5 nh none uhp 1 deag 0 chgif 0 ttlexp 0 rec 0
*Apr 16 07:04:18.103: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, Post-routing NAT Outside(24), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, Stateful Inspection(27), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.103: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.103: UDP src=61183, dst=53, CCE Post NAT Classification(38), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.107: UDP src=61183, dst=53, Firewall (firewall component)(39), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.107: UDP src=61183, dst=53, TCP Adjust MSS(50), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.107: UDP src=61183, dst=53, NAT ALG proxy(55), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.107: UDP src=61183, dst=53, Post-Ingress-NetFlow(68), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.107: UDP src=61183, dst=53, Dialer idle reset(84), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), len 66, output feature
*Apr 16 07:04:18.107: UDP src=61183, dst=53, Dialer idle reset(85), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Dialer5), g=8.8.4.4, len 66, forward
*Apr 16 07:04:18.107: UDP src=61183, dst=53
*Apr 16 07:04:18.107: IP: s=$$$Dialer4-IP$$$ (GigabitEthernet0/0), d=8.8.4.4 (Virtual-Access3), len 66, sending full packet
*Apr 16 07:04:18.107: UDP src=61183, dst=53hi,is this question is ok?
if you forget do this config like below:
pfr master
learn
delay
throughput
periodic-interval 3
monitor-period 1
pfr master
delay threshold 200
jitter threshold 50
mode route control
mode monitor passive
mode select-exit best
i will do like this,four ADSL connect a switch ,this switch connect a router 2911(with data license)
at 2911 do four pppoe
i want to load balance at this four adsl. -
Apache Sling Logging Writer Configuration
Hi,
I'm having an issue where my custom log writer configuration is not being picked up and used by CQ5 sometimes. I've created a custom error log writer based on the example provided at http://helpx.adobe.com/cq/kb/HowToRotateRequestAndAccessLog.html which I've installed on an author, replicated it to the publishers, and all seemed ok and working correctly. The settings are:
Log File: ../logs/error.log
Number of Log Files: 5
Log File Threshold: 200MB
After installing this, the error logs rotated at 200MB resulting in error.log.0, error.log.1 etc as expected.
However after rebuilds on the machines, this configuration was overwritten (as expected). So I've installed and replicated the package again, but now the configuration is not taking effect. I'm using the exact same config package as I was previously, but the logs don't seem to be rotating at all now (not even daily). I've deleted the config from the Felix console on all authors and publishers, reinstalled on the authors, replicated to the publishers, then restarted the CQ5 service on all machines, but it's still not working.
So I have a couple of questions about this:
Is there somewhere else in CQ5 that might be overriding these log writer config settings?
Is ../logs/error.log correct for the standard log file location? A note in step 3 of Creating Your Own Loggers and Writers on http://dev.day.com/docs/en/cq/current/deploying/configure_logging.html states:
Log writer paths are relative to the crx-quickstart/launchpad location.
Therefore, a log file specified as logs/thelog.log writes to crx-quickstart/launchpad/logs/thelog.log.
To write to the folder crx-quickstart/logs the path must be prefixed with ../ (as../logs/thelog.log).
So a log file specified as ../logs/thelog.log writes to crx-quickstart/logs/thelog.log.
The configs in the log rotation example also use ../logs. However when looking at the default/standard logging writer config, it uses logs/error.log. Which one is correct?
Any help on what's going on here would be appreciated!!
Thanks,
KHi,
I am answering your last question and this one here only.
1. Log configuration can be override at project via creating config and overriding factory "org.apache.sling.commons.log.LogManager.factory.config-<identifier>" and writer (if required) "org.apache.sling.commons.log.LogManager.factory.writer-<identifier>". So plz check if you have configure log at project level. Now if you are not able to see then plz recheck you log configuration in felix console http://localhost:4502/system/console/slinglog here you can see entire log configuration for CQ system.
2. both will work but the location will change
i. CQ 5.5 - log file located under "crx-quickstart" ../logs/<filename>.log will create under this
ii. CQ 5.4 - logs creates under "crx-quickstart\logs" also under "crx-quickstart\launchpad\logs" so if you select ../logs/ it will go under "crx-quickstart\logs" only but you can change wherever you want to store. Again you can see this configuration info at http://localhost:4502/system/console/slinglog
3. You can also customize you log via creating at project level and assigning the "identifire" (with all other configure parameters) for more information you can refer http://sling.apache.org/site/logging.html apart from earlier share links.
I hope above will help you to proceed. Please let me know for more information.
Thanks,
Pawan -
How to restrict logging on portal (Performance issue)
Hi guys,
does anyone know how to restrict logging of the portal? Even though I made a change on Visual Administrator -> Services -> Log Configurator setting ALL categories to severity = 'Error', I keep getting 'Info' severity traces logged in defaultTrace.trc (viewed by Logg Viewer). Which in practise means tons of logged trace information! I think this might be one of the reasons we have been experiencing performance issues lately.
Does anyone know how to restrict this logging?
Any help greatly appreciated!
Cheers,
FrankHi,
I would not only set the severity of categories to 'Error' but also locations to 'Error'.
A log controller - can be a "category" or a "location". Categories are used for "logging" and represent problem areas such as network, database, security, user interface, etc. Identified by a slash-separated ('/') path of names, prefixed with an additional slash. Locations are used for "tracing" and correspond to places in the development components. Identified by a dot-separated ('.') path of names, which is often the name of the respective java package.
Greetings,
Praveen Gudapati -
Problem in retriving the realpath from the servlet
Hai All,
I am facing problem in retriving the realpath from the servlet.
I am using the following code in order to retrieve the path.
String prefix = getServletContext().getRealPath("/WEB-INF/classes");
The value returned from above code is null.
I am using Weblogic 8.1 server, and deploying my servlet as WAR file inside
the weblogic server.
Is this the problem with the weblogic server or with the code. Is there any way to over come this.
I need the path as i am implementing Log4j for the servlet and i have to pass the
configuration file in one of the function "PropertyConfigurator.configure(file);"
where the file should include complete path.
My configuration file is in WEB-INF/Classes directory.
Any help is appreciated.
Thanks in advance
Pooja.String realPath = request.getRealPath(request.getContextPath());
That should return the path up to where you have your servlet context. -
Using FMS v4.5.5 with a browser-based audio player running on iPad/iPhone
Hello,
I’m seeking some clarity/guidance on using FMS v4.5.5 (Streaming Edition) with a browser-based audio player running on iPad/iPhone (i.e. under iOS).
Background
I have a Microsoft Windows 2008 R2 Web Server running IIS v7.5 and supporting a website built using ASP.NET and C#. Parts of the website allow a visitor to play a selection of audio clips from our bespoke MP3 library. Due to UK music licencing constraints, we must stream the clip to the client browser – we must not download either part or all of the source MP3 file(s). We therefore had a custom audio player built for us some time ago using Flash/AS3. This has and continues to work very well, and uses RTMP to stream the clips from FMS to the client browser.
As our site has become more established the number of visitors has steadily grown. In the early days the number of visitors from the iOS platform was relatively small but, last month, it had risen to 40%! As Flash is not supported on the iOS platform, this growing group of visitors are unable to fully maximise the benefits offered by the website, which I am now trying to address.
What I’m Trying To Do…
From what I’ve researched and read, I believe that FMS v4.5.5 supports HLS and I need to use this (instead of RTMP) over HTTP between FMS and the iOS Safari client. I have been experimenting with an Open Source player (JPlayer) and a commercial player (JWplayer) and appear to have these playing a MP3 file as a “progressive download” (I think that’s the right term) as all I’m doing is specifying the file path (no HTTP prefix etc.), i.e. the audio is not really being streamed as I require. Unfortunately, I’ve not found / worked out how to configure my FMS to respond to a path request along the lines of:
http://www.myserver.com/live/audio1.mp3
Hopefully someone reading this who is much more expert on FMS, HLS, HDS, HTML5, etc. than me can point me in the right direction!
What I’m confused about…
1) Can all my MP3 assets stay as is and still be streamed to the iOS Safari client? To the best of my knowledge, the key properties of my MP3 files are CBR, 44,100Hz, 320Kbps.
2) If not, can they be converted on-the-fly by FMS or do I need to create additional audio assets to support HLS etc.?
3) If I have to manually create additional audio assets, how do I do that (I’ve seen references to tools from both Adobe and Apple but not actually found the kits)?
4) Some of the Adobe documentation I’ve read implies that FMS support for HLS etc. is only available when FMS is used in conjunction with the bundled Apache web server. As stated earlier, my entire site runs on IIS so does that mean to achieve what I want I’ll have to run two web servers on my physical server – IIS for the website itself and Apache for RTMP/HLS/etc.?
5) What changes do I need to make to my current FMS configuration to get HLS to work? I’m sure someone has been here already and can enlighten me with their experience and hopefully point me to some straight forward documentation to follow!
6) Lastly, and really part of (5), once I’ve got FMS configured correctly, what would be the typical path to a given MP3 audio file that I would give the iOS Safari browser to make this all work.
I appreciate this is rather a lengthy first post but hopefully the background puts my questions (and confusion!) in context. Bottom line is… I simply want to be able to stream audio clips only (no video) to iOS Safari browsers from FMS v4.5.5 running on a Win2K8R2 platform with IIS v7.5, and with no audio content being stored (even temporarily) on the iOS platform.
My thanks and appreciation in advance to anyone who can help me achieve this.
Steve Barker
Business IT SolutionsHi Apurva,
Thank you for your reply. Unfortunately I am not much further forward, despite having read more Adobe documentation (FMS v4.5 Configuration and Administration Guide, FMS v4.5 Developer’s Guide) and trying different configuration options.
First to confirm a point you made when answering point 4 yesterday. Yes, in my current RTMP scenario I have several MP3 assets (let’s call them Audio1.mp3, Audio2.mp3, Audio3.mp3, etc.) that are made available to a bespoke Flash/AS3 player via the LIVE application. I understand that as I purchased the Streaming Edition of FMS v4.5, a Flash-based player is restricted to using the LIVE application. You go on to say that I “publish” these assets to the LIVE application. I set this up a while back but do not recall having to “publish” anything. All I recall doing was to ensure that all the assets (the .mp3 files) were in a single folder and that the folder was identified by the <Streams> tag in the following file (example shown):
Flash Media Server 4.5\applications\live\Application.xml
<StreamManager>
<VirtualDirectory>
<Streams>/;C:\MP3Library</Streams>
</VirtualDirectory>
</StreamManager>
To the best of my knowledge, I didn’t have to do anything else to make the current solution work. Having read more of the documentation I am still none the wiser as to what I need to do (step-by-step) to “publish” my converted MP3 assets (see next paragraph) to the LIVEPKGR application. Please could you explain these steps to me by way of an example.
WRT your answer to point 1 yesterday, I wish to clarify the exact output I need to create when converting my MP3 assets. Am I expected to produce a Audio1.aac file, or a Audio1.mp4, file, or a Audio1.m4a file, etc.? Or am I meant to be using ffmpeg (either directly or indirectly) with a much more sophisticated command line that somehow generates stream-rated info/files as well? An example of how you would use ffmpeg to convert one of my MP3 assets would be very much appreciated.
Lastly, the coexistence of IIS and Apache (ref your answer to point 2 yesterday). That all made sense but given all the testing/changes I’ve been making I thought it wise to start afresh! So I completely removed FMS from my dev server and re-installed Flash Media Streaming Server v4.5.5 with the bundled Apache v2.2 server. When presented with the dialogue “Would you like for Apache to listen on port 80. If not FMS will be using port 80 instead.” I answered NO. When presented with the dialogue regarding FMS server ports, I entered 1935 NOT 1935,80 (should I have done that as the preamble makes reference to HTTP webserver proxy and HTTP Dynamic Streaming origin services?). I then modified the Application.xml file as described above.
To test the new set-up, I did the following. First, the test environment…
DEV Server
Windows Web Server 2008 R2 SP1
IIS v7.5
ASP.NET v4.0
Flash Media Streaming Server v4.5.5
Apache v2.2
IE v9.0
Adobe Flash Player 11 ActiveX v11.5.502.146
TEST Client
Apple iMac (Intel)
Mac OS X v10.6.8
Safari v5.1.7
Adobe Flash Player 11 Plug-in v11.5.502.146
On DEV Server… launched IE and loaded the home page of my website, which has two elements on it – one to load/run our bespoke Flash player, the other to run JPlayer (configured to use HTTP). I selected our bespoke Flash player and it played a MP3 audio file. I verified this in real-time via the FMS Admin Console on the server.
On TEST Client… entered http://192.168.20.250:8134 into Safari – it comes up with the FMS install completed / test your server page. In the middle of the video display area a black box appears saying “10000 OK” – I clicked OK. I then clicked HDS Single Bitrate – the video plays (Not Using Hardware Acceleration is briefly displayed). There is NO activity logged in the FMS Admin Console back on the DEV server under “live”, “livepkgr” or “vod”. I assume this is because I’ve gone straight to the Apache Server via the port reference – is that correct? Next I tried the HLS Single Bitrate – same results.
The HDS Single Bitrate logs the following in the Apache access_log file:
"GET /hds-vod/sample1_1500kbps.f4v.f4m HTTP/1.1" 304 - "-" "Apple Mac OS X v10.6.8 CoreMedia v1.0.0.10K549"
The HLS Single Bitrate logs this:
"GET /hds-vod/sample1_1500kbps.f4v.f4m HTTP/1.1" 304 - "-" "Apple Mac OS X v10.6.8 CoreMedia v1.0.0.10K549"
"GET /hls-vod/sample1_1500kbps.f4v.m3u8 HTTP/1.1" 304 - "-" "Apple Mac OS X v10.6.8 CoreMedia v1.0.0.10K549"
"GET /hls-vod/sample1_1500kbps.f4v.m3u8 HTTP/1.1" 200 816 "-" "Apple Mac OS X v10.6.8 CoreMedia v1.0.0.10K549"
"GET /hls-vod/sample1_1500kbps.f4vFrag1Num0.ts HTTP/1.1" 200 1143416 "-" "Apple Mac OS X v10.6.8 CoreMedia v1.0.0.10K549"
"GET /hls-vod/sample1_1500kbps.f4vFrag1Num1.ts HTTP/1.1" 200 873072 "-" "Apple Mac OS X v10.6.8 CoreMedia v1.0.0.10K549"
"GET /hls-vod/sample1_1500kbps.f4vFrag2Num2.ts HTTP/1.1" 200 1591984 "-" "Apple Mac OS X v10.6.8 CoreMedia v1.0.0.10K549"
etc…
At this point I’m stuck once again since I’m not clear how to construct the JPlayer HTTP reference. You have suggested:
http://192.168.20.250:8134/hls-live/livepkgr/_definst_/livestream/livestream.m3u8
That produces the following in the Apache error_log file:
[error] [client 192.168.20.4] File does not exist: D:/Program Files/Adobe/Flash Media Server 4.5/webroot/hls-live
If I change the JPlayer HTTP reference to:
http://192.168.20.250:8134/hls-vod/sample1_1500kbps.f4v.m3u8
the audio from the video plays.
Also, if I look in the applications\livepkgr folder structure there is only \events (with sub-folder _definst_ and sub-sub-folder liveevent) – there are no _definst_ , livestream , streams folders etc. So besides me not quite understanding the logic/flow here, I seem to be missing a few folders/files too! I’d be very grateful for any light you can shed on all this. Plus an example of what my HTTP string should ultimately look like; for example:
http://192.168.20.250:8134/hls-live/livepkgr/_definst_/livestream/Audio1.m3u8
Apologies for such a long reply but I’ve been at this for over 10 hours today! I feel I’m getting closer but clearly there are still some gaps and configuration errors.
Thanks again for your time, support, patience and understanding.
Kind Regards, Steve -
HOW to include the needed libraries to be copied into the self-cotained app
I'm using: Netbeans 7.2, JavaFX 2.2, JDK 7u7. First, I believe the instructions posted at http://docs.oracle.com/javafx/2/deployment/self-contained-packaging.htm#A1349508 are off (when dealing with NetBeans, at least), as the resulting bundle copies the dependent libraries (3rd party) to the root where the main .jar file is placed, but the MANIFEST gets JavaFX-Class-Path with the lib/ prefix.
This is what I have added to build.xml in the project's folder:
<target name="-post-jfx-deploy">
<fx:deploy verbose="true" nativeBundles="image" outdir="${basedir}/${dist.dir}" outfile="${application.title}">
<fx:application name="${application.title}" mainClass="${javafx.main.class}"/>
<fx:resources>
<fx:fileset dir="${basedir}/${dist.dir}" includes="*.jar"/>
<fx:fileset dir="${basedir}/${dist.dir}/lib" includes="*.jar"/>
</fx:resources>
<fx:info title="${application.title}" vendor="${application.vendor}"/>
</fx:deploy>
</target>This is the tree structure of the dist folder after Clean and Build Project has been triggered by NetBeans:
│ JFXA.html
│ JFXA.jar
│ JFXA.jnlp
│
├───lib
│ log4j-1.2.16.jar
│
└───web-files
dtjava.js
error.png
get_java.png
get_javafx.png
javafx-chrome.png
javafx-loading-100x100.gif
javafx-loading-25x25.gif
upgrade_java.png
upgrade_javafx.pngAnd this is the structure of the created bundle (conents of the JRE runtime omitted):
└───JFXA
│ JFXA.exe
│ JFXA.ico
│
├───app
│ JFXA.jar
│ log4j-1.2.16.jar
│ package.cfg
│
└───runtime
└───jreProblem is, when I run the application (the *.exe* inside the bundle) it tries to run the main *.jar*, but fails due to the inability to locate compile-time libraries. Apparently, this behavior is due to the MANIFEST of the *.jar* being linked to the folder named lib (defaults), but the build script copies the libraries to the output dir where the actual *.jar* resides (dist). How can I fix this? Thanks.
I think I have ran into the same problem as here: javafxpacker - include libs
Edit*:
Upon .jar extraction and further inspection of the MANIFEST file, I see this:
JavaFX-Class-Path: lib/log4j-1.2.16.jar
Currently, as mentioned above, the libraries end up in the root folder where the main .jar resides, due to:
*<fx:fileset dir="${basedir}/${dist.dir}/lib" includes="*.jar"/>*
So, my question is, what do I need to change in order to get the dependent libraries to be copied into the correct path (with lib prefix), when building a bundle? The *<fx:fileset>* does not seem to support anu attribute that would specify the output path structure..Use
<fx:resources>
<fx:fileset dir="${basedir}/${dist.dir}" includes="*.jar"/>
<fx:fileset dir="${basedir}/${dist.dir}" includes="lib/*.jar"/>
</fx:resources>or simply
<fx:fileset dir="${basedir}/${dist.dir}" includes="**/*.jar"/>Filed http://javafx-jira.kenai.com/browse/RT-24757 to update the docs.
Edited by: igor on Sep 5, 2012 2:23 PM -
Pulling a program out of the IDE
I have been playing with pulling small progrograms out of my Integrated development environment (IDE); writing them to CD; and installing them on other desktops, just as an exercise in the case I want to deliver some applications to a friend.
The overall requirements(steps) are not clear to me.
1.the directory organization
2. the file (jar) creation
3. the D0S (java.exe) window
Are some of the issue that come to mind.
I have been able to use a desktop icon and set the path to a program.class file and run it--making the program window appear but the java.exe Dos window also appears.
So far, the number of texts I have give no step by step instructions on how to configure an environment without an IDE with the java VM already intalled, or how to pull a program out of the IDE and install it along with a copy of the VM on another machine.Good question. Lot's of people don't know this, and I can't even say I have all the right answers. There are probably numerous ways you could do this. The best way, if you have the money, is to buy something like InstallAnywhere or Wise that provide professional installations. Not only will your install look like professional installation of stuff like Photoshop, etc but it will also handle issues like OS platform specifics, environment variables, registry entires (if possible), the proper JRE/JDK installed... if not install it, uninstallation features, and so forth. That is by far the best way to go.
However, often you just want to bundle something up and send it out to a few friends, family, etc. You could of course look for an open source or freeware utitlity and no doubt there are some out there. Or, you could do what a lot of people do now, use the Ant tool (written in Java) and have a build script that does everything for you. I have a simple template build script that is used for various tasks. In our work setup, it does local dev (incremental) compiles, and if necessary packaging it up into .jar/.zip files. My single build script can also run junit tests and reports, builds executable packages into .zip and .jar's as necessary, will do a clean build (great for making sure any code changes don't break some code elsewhere, thus ensuring that your normal incremental build process is not missing something), it can FTP or copy files to locations, it can email results, and so forth. If you don't know about ant, I STRONGLY suggest you learn it quickly, and to me there is no better way than buy the book Java Development with Ant. Two of the main Ant developers/committers wrote the book and it does an excellent job of teaching you about all the different uses of Ant, including the template build script I now use. It is well worth the $40 or so you'll find the book for, and within a week you'll have a good build template that you can modify for specific projects.
Now, in terms of the 3 things, well, the directory organization is always changing. Each project may have something different, but here is one that I usually use:
<root project dir>: (below this you'll find)
/src - location of all src files
/src/java - the location of the project specific java code
/src/examples - if need be (especially useful for frameworks and API's you wish to share) show example applications using the output of the /src/java code
/src/test - location of JUnit, jfcUnit and other test files to unit test your code (very important, should be done no matter what!!)
/lib - location of any 3rd party libraries you need, both for compilation and runtime. Keep in mind that your build script may pull only a subset of these libraries in for runtime. For example, the /src/test that uses JUnit will require the junit.jar file. You won't need this for runtime, so your build script sets up a compile classpath with junit.jar, and a runtime classpath that will exclude junit.jar, perhaps others.
/dist - the location that the build script puts all distributable files. This would be any executable .jar file, any .zip file, perhaps other files necessary for distribution. If you were making a large application and planned to burn it to disk, instead of a single .zip file, you may actually build the sub-dirs below the /dist/<your app> type of dir, so that you can simply burn from that <your app> dir to the root of the cd.
/build - location of all compiled classes, including from /src/java, /src/examples, /src/test.
/build/classes - the location of compiled java code
/build/test - the location of test results, including perhaps test data to be used by the test code, and possibly the output dir of test reports
- /build/test/reports for example for output of test reports.
/doc - location of any documentation, including the JavaDoc produced by the build script from your src.
<project root> - this is the location of your build.xml ant build script, if need be. The build script, as you would learn in the book, is set up so that you can move it anywhere and it will still build your project correctly. You may opt to put it in the /scripts dir instead and keep the project root super clean.
/misc or /etc - common location to put things like properties files, misc files used to build projects. For example, in the building of a EJB application (.jar or .ear file), you will no doubt need the META-INF/application.xml file. Or in a .jar file you need a special META-INF/manifest.mf file. The /misc or /etc dir is a good candidate for these types of things. You can even package it up in your app so that in the .jar file you have /etc/properties/somepropertyfile.properties, and in your code do a simple getClass().getClassLoader().getResource("/etc/properties/somepropertyfile.properties") to always ensure you pull it from this directory. OR, your build script can "change" the location this file goes. It is all up to you.
That is what I use for all my projects, the dir structure anyway. What you do to build your .jar/.zip files is up to you. You usually don't need to pull the /src dir, the /dist dir, etc into your .jar/.zip files. Normally you'll have the compiled classes at the root. So in your project dir on your disk, you may have <project root>/build/classes/java/org/mycompany/ui/Main.class, and in your .jar file it would simply be <root of .jar file>/org/mycompany/ui/Main.class, and your build file can easily "change" the root path (using <zipfileset prefix=""> task) to change the path of any file. But more of that can be learned in that book and by looking up resources on the net. The Ant JavaDoc API is very good at explaining most of these as well, and there are TONS of ant scripts in most projects to look at for examples.
The file creation, well, as I said Ant has built in tasks you can use to create .jar files, .zip files, etc. All of that is all built in to how Ant works.
As for java.exe, well, in a professional app, you usually do one of two things. You either write a simple C/C++/Delphi/some other languages .exe wrapper (for windows) that internall executes the java.exe and runs the JVM to hide the window, as well as provide a .exe file to look more "native", or you run javaw.exe, which hides the Console output window for most apps. NOTE: if you create a .bat shortcut on your desktop to javaw.exe, you will STILL get a console window that shows up. ALL shortcuts to .bat files will always create a console window. Many java developers don't understand why they run javaw.exe from a shortcut on their desktop and still see the console window.
Now, hopefully that helped a bit. But if not, or you still have questions, I am watching this thread so fire away and I'll help more. -
[SOLVED] Inkscape and python-numpy problem.
When I'm trying to use the perspective tool in Inkscape I'm getting this message.
Inkscape has received additional data from the script executed. The script did not return an error, but this may indicate the results will not be as expected.
Failed to import the numpy or numpy.linalg modules. These modules are required by this extension. Please install them and try again. On a Debian-like system this can be done with the command, sudo apt-get install python-numpy.
I got python-numpy installed, and was asking around in #inkscape, they think it has to do with a wrong path problem with prefix or exec-prefix(?).
I tried to run Inkscape inside /usr/lib/python3.2/site-packages/numpy, but I'm getting the same message. Also tried to run as root... nothing helped.
Any idea's?
Last edited by Math (2011-10-23 04:45:23)It turned out to be a python2/python3 version problem. I just had to install python2-numpy to fix this.
SOLVED! -
Python, distutils, data_files - Yay! I know where my data files are.
After a long and painful research i have finally found usable way to make distutils propagate location of data files to installed application.
Python's distutils allow user to specify location for data_files but there's no standard way to acess them.
Yes sure ,there are few workarounds :
1) distributing data_files as package_data
- Do you really want to have ie. README.txt in /usr/lib/python/... ?
2) Accessing those data_file using $sys.prefix
- hmm. Here you hardcode $sys.prefix relative path to setup.py like this:
setup(...., data_files=['share/myverycoolpackage/doggie.gif'], ..)
- and access it this way:
os.path.join(sys.prefix, 'share/myverycoolpackage/doggie.gif')
This works fine, but you're making assertions about layout of users $sys.prefix directory. Not talking about possibility to specify --data-dir during installation.
Both are not really usable. Here goes the solution:
Idea: Install additional 'package.ini' file, that will get modified during install and will hold location of data files.
This package.ini will be installed as package_data, so that it will be accessible relatively to sources.
And this is how i did it:
New command to install process:
from os.path import *
import re
class package_ini(Command):
Locate package.ini in all installed packages and patch it as requested
by wildcard references to install process.
user_options = []
def initialize_options(self):
pass
def finalize_options(self):
pass
def visit(self, dirname, names):
packages = self.distribution.get_command_obj(build_py.__name__).packages
if basename(dirname) in packages:
if 'package.ini' in names:
self.patch(join(dirname, 'package.ini'))
def patch(self, ini_file):
print 'patching file' + ini_file
with open(ini_file,'r') as infile:
file_data = infile.readlines()
with open(ini_file,'w') as outfile:
for line in file_data:
_line = self.patch_line(line)
if _line:
line = _line
outfile.write(line)
def patch_line(self, line):
Patch an installed package.ini with setup's variables
match = re.match('(?P<identifier>\w+)\s*=.*##SETUP_PATCH\\((?P<command>.*)\.(?P<variable>.*)\\)', line)
if not match:
return line
print 'Replacing:'+line
line = match.group('identifier')
line += ' = '
data = '(self).distribution.get_command_obj(\''+\
match.group('command')+'\')'+'.'+\
match.group('variable')
line += '\''+eval(data)+'\''
line += '\n'
print 'With:' + line
return line
Apend this package_ini command to install command:
class install(_install):
from distutils.command.install import install as _install
sub_commands = _install.sub_commands + [
(package_ini.__name__, None)
Mention your package.ini in setup():
setup(..., package_data={'myverycoolpackage':['package.ini']}, data_files='myverycoolpackage','doggie.gif',..)
Write your package.ini like this:
__data_dir__ = '../../data' ##SETUP_PATCH(install_data.install_dir)
Package.ini will get patched properly during install, so if i assume that user specified --data-dir=C:/Program Files/ApplicationData/verycoolpackage, package.ini will be:
__data_dir__ = 'C:/Program Files/Application Data/verycoolpackage'
Notice that you can access any property from setup script, so this might be usable for version string or other stuff.
Also notice that in 'develoment environment' location of data files differs from 'installation environment'. Cute, isn't it?.
Now you just have to evaluate package ini (propably in myverycoolpackage/__init__.py):
with open(inipath) as ini:
for line in ini.readlines():
exec(line)
And we're done.I've just checked several versions of Dreamweaver in Windows 7. They all have dotted lines showing the tree structure in the Files panel.
I also checked Dreamweaver CS3 on Mac OS X 10.6, and CS5.5 and CS6 on Mac OS X 10.7. None of the Mac versions have dotted lines. The files are simply indented.
If you're on a Mac, that's the way it has been for a long time. If you're on Windows, the lines should still be there. There is no special setting in Dreamweaver. -
Syntax error when adding variables in recordset (query)
MySql,PHP,Dreamweaver,WindowsVista
Hi I am receiving a syntax error: invalid quantifier ++ $orderNum;s*?> when adding two variables in the recordset (query) dialog box. I get the error when clicking OK.
Here is what is entered:
name: fieldname
type: text
default: -1
runtime value: $_GET['Field']
name: searchvalue
type:text
default: -1
runtime value: $_GET['Search']
Can anyone help with this?That's a completely separate issue. The error message is telling you that you have not defined the testing server correctly in the Site Definition dialog box.
The Host directory field and URL prefix should both point to the same place, in other words, the root of your website. Host directory is the physical path, while URL prefix is the address you would put in a browser address bar.
Select Site > Manage Sites. Select the name of the site, and click the Edit button. In the Site Definition dialog box, select the Advanced tab, and then choose Testing server from the Category list on the left.
Depending on how your remote login works, Host directory should probably be public_html or just /. Use the same value as in the Remote server part of the Site Definition dialog box. The URL prefix should be http://gaylehansen.aisites.com/.
Maybe you are looking for
-
Weblogic 8.1 & Sun Java Studio Creator
I'm in a new position where I need to deploy web apps created in Sun's Java Studio Creator to Weblogic 8.1, that hits an Oracle 8i back end. I'm curious to see if anyone on this board is using a similar mix of technologies. If so, what drivers are yo
-
Hi All, I maintain the Tax in FV12 eg tax in FV12 amount is 12.000 After this if I go to MIRO and putting all necessary input and aftet click on Calculate Tax i get Tax amount as 96.90 for tax which i maintained in FV12. Now I change Condition in FV1
-
Double clicked on iTunesSetup.exe, and nothing happens!
That's it. I double clicked on iTunesSetup.exe, and absolutely nothing happens. I checked Task Manager, and it seems that iTunesSetup.exe executes for a brief second or two, then exits. I checked my Local Settings\Temp folder, and there is a iTunes.e
-
Hi, I need to know what are available modules in SAP. Can any give me a complete list. Thanu
-
Video jumps back of a few frames when adding title or transition in CS6
When adding title or transition in CS6 I get a jump back of a few frames in the main video layer at the in point of the graphics or at the transition ( a film dissolve for instance). If I remove the title or transition the jump goes away. Help Pleas