(SOL16495) The following table contains base operating system information for the LineRate system:
Note: Some versions may use components from multiple versions of the base operating system.
LineRate version
Base operating system
2.0.0 - 2.5.1
FreeBSD 9.1, 64-bit
1.6.0 - 1.6.4
FreeBSD 7, 64-bit
Important: F5 has modified the LineRate base host operating system, and responds to all reported vulnerabilities for that base operating system. You must install only the patches that F5 supplies.
Supplemental
↧
Informational: Base operating system information for the LineRate system
↧
Informational: Base operating systems of F5 products
(SOL121) All F5 products run a base operating system, and F5 responds to all reported vulnerabilities for that base operating system.
Important: F5 has modified these base operating systems. Therefore, you must install only the patches that F5 supplies.
The base operating systems for F5 products are as follows:
F5 Product
Base Operating System
Reference
BIG-IP TMOS products 10.1.0 - 11.6.0
CentOS Linux
SOL3645
FirePass 6.1.0 - 7.0.0
Slackware Linux
SOL2253
Enterprise Manager 2.0.0 - 3.1.1
CentOS Lin
↧
↧
Release Note: LineRate Release Notes, version 2.5.1
This release note documents LineRate version 2.5.1.
↧
Manual: LineRate Open Source License Notice
↧
null: End User License Agreement Change Notice
(SOL12902) During the course of normal business, the F5 Legal department may modify the End User License Agreement (EULA). F5 presents the EULA during the initial system license activationand any license re-activation. Customers are expected to accept the EULA or contact our Legal department for further compliance and contractual efforts.
In June 2014, F5 changed the EULA. The new EULA will be presented and it requires acceptance when any new system is initially activated or when an existing system's licen
↧
↧
Known Issue: Power supply information and status may be incorrectly reported by certain platforms
(SOL16028) Description
Power supply information and status may be incorrectly reported by certain platforms.
This issue occurs when all of the following conditions are met:
After the BIG-IP system has booted, you add or remove a power supply.
Your BIG-IP system uses one of the following platforms:
BIG-IP 2000 series (C112)
BIG-IP 4000 series (C113)
BIG-IP 5000 series (C109)
BIG-IP 7000 series (D110)
BIG-IP 10000 series (D113)
Impact
If a power supply is added or removed after the BIG-IP system is alr
↧
Change in Behavior: BIG-IP APM connectivity license use
(SOL13267) Old Behavior
Previously, the BIG-IP APM system consumed a User Connectivity License (CCU) for all BIG-IP APM connection types.
New Behavior
Beginning in BIG-IP APM 11.1.0 and 11.0.0 HF1, CCU utilization has changed as listed in the following table:
APM Concurrent User Licensing
Access category
Specific access
CCU utilized
Full Network Access (L3 SSL VPN)
Any access (Edge Client, browser, API)
Yes
Application Access (port forwarding)
App Tunnel
<
↧
Security Advisory: Linux kernel vulnerabilities CVE-2014-8159 and CVE-2014-8369
(SOL16478)
↧
Security Advisory: Linux kernel vulnerability CVE-2009-4537
(SOL16479)
↧
↧
Known Issue: The Configuration utility may not display SAML IdP configuration information
(SOL16498) Description
The Configuration utility may not display Security Assertion Markup Language (SAML) Identity Provider (IdP) configuration information.
This issue occurs when all of the following conditions are met:
You attempt to view a BIG-IP APM SAML IdP configuration from the Configuration utility.
You use one of the following BIG-IP access role configurations:
Auditor
Guest
Impact
You are unable to access the SAML configuration details.
Symptoms
As a result of this issue, you may encount
↧
Security Advisory: Linux kernel vulnerability CVE-2010-0415
(SOL16471)
↧
Security Advisory: Linux kernel vulnerability CVE-2010-2524
(SOL16477)
↧
Known Issue: The BIG-IP APM Custom Report may not display assigned values
(SOL16485) Description
The BIG-IP APM Custom Report may not display assigned values.
This issue occurs when all of the following conditions are met:
You create a BIG-IP APM Custom Report containing theuser report field Assigned IP.
You run the custom report.
Impact
The custom report field for Assigned IP does not show the IP address assigned to user sessions.
Symptoms
As a result of this issue, you may encounter one or more of the following symptoms:
When you run the custom report, the Assigned IP value
↧
↧
Known Issue: A memory leak may occur when using Diameter based iRule commands
(SOL16491) Description
A memory leak may occur when you use Diameter based iRule commands.
This issue occurs when all of the following conditions are met:
You have configured a virtual server to process Diameter messages.
The virtual server references an iRule that uses Diameter based commands. For example, AVP::insert, AVP::replace, AVP::codes.
Impact
The Traffic Management Microkernel (TMM) may become unstable and possibly produce a core file as a result of exhausted memory.>
Symptoms
As a result of
↧
Known Issue: Trunks with LACP enabled may remain down after restarting mcpd on the 2000 and 4000 series platforms
(SOL16493) Description
Trunks with Link Aggregation Control Protocol (LACP) enabled may remain down after you restart the master control process (mcpd) on the 2000 and 4000 series platforms.
This issue occurs when all of the following conditions are met:
You have either a BIG-IP 2000 or 4000 series platform.
You have configured the BIG-IP system to use a trunk or a logical grouping of interfaces.
You have enabled LACP on the trunk.
You have restarted only mcpd using one of the following commands:bigstart
↧
Known Issue: TMM may produce a core file and restart when certain ICMP packets classified by BIG-IP AFM match the rules at the Global and Route Domain contexts
(SOL16490) Description
When BIG-IP AFM classifies certain ICMP packets that match the rules at the Global and Route Domain contexts, the Traffic Management Microkernel (TMM) may produce a core file and restart.
This issue occurs when all of the following conditions are met:
You have configured BIG-IP AFM with a Logging profile in which both Rule Logging and Log Translations are enabled.
From the Security > Reporting menu, the server-side AVR Statistics collection is enabled.
Certain ICMP packets (for e
↧
Known Issue: Mac OS devices may be unable to establish a BIG-IP APM access session
(SOL16496) Description
Mac OS devices may be unable to establish a BIG-IP APM access session.
This issue occurs when all of the following conditions are met:
Your access policy is configured with one or more of the following endpoint security (client-side) agent checks:
Antispyware
Antivirus
Firewall
Hard disk encryption
Your BIG-IP APM uses the OPSWAT library version 3.6.8642.2.
Users attempt to establish a session using a Mac OS X device.
Impact
The session fails to establish.
Symptoms
As a res
↧
↧
Security Advisory: NTP vulnerability CVE-2015-1798
(SOL16505)
↧
Known Issue: NTLM authentication may not function as expected
(SOL16499) Description
NT LAN Manager (NTLM) authentication may not function as expected.
This issue occurs when all of the following conditions are met:
You have configured the BIG-IP APM system with an NTLM Auth configuration.
You have configured the NTLM Auth configuration without defining at least one domain controller fully-qualified domain name (FQDN).
You configure an access policy that references the NTLM Auth configuration.
A user attempts to establish a session with the access profile configured
↧
Known Issue: Connection distribution may be skewed when a virtual server is associated with the OneConnect profile and the Least Connections (member) load balancing mode
(SOL16487) Description
Connection distribution may be skewed when a virtual server is associated with the OneConnect profile and the Least Connections (member) load balancing mode.
This issue occurs when all of the following conditions are met:
Your BIG-IP system is running the affected versions with the following hotfixes:
BIG-IP 11.4.1 HF6, HF7, or HF8
BIG-IP 11.2.1 HF11, HF12, HF13, or HF14
The affected virtual server uses the OneConnect profile.
The resource pool associated with the affected vi
↧