Workaround for Login Fail Issue Related to iOS 11.3, 11.4, 12 and above 2018-11-29

    As iOS versions continue to evolve, while we still propose modifying Portal URL Exceptions as a workaround as described in an earlier announcement, now instead of adding 1) “OS 11_4” and “OS 11_3”; or 2) "OS 11_", please add "OS 1" to avoid login fail issues related to iOS 11.3, 11.4, 12 and above due to the limited space in Portal URL Exceptions. Note that this would affect not only affect iOS 11.3, 11.4, 12 and above, but also other versions before or after these versions as long as they start with 1.

  • Workaround:
  • Go to System › General, add “OS 1” to Portal URL Exceptions (User Agent).

  • For more information, please contact 4ipnet Tech Support team at support@4ipnet.com

    Workaround for Login Fail Issue Related to iOS 11.3 and 11.4 2018-08-09

    We have confirmed that the same login fail issue that would occur on iOS 11.3 devices would also occur on iOS 11.4 devices. Regarding the login fail issue on iOS 11.3 devices, we have provided both a patch and two workarounds in earlier announcements, where the first workaround is to set Portal URL of the particular Service Zone to "None" and the second workaround is to add “OS 11_3” to Portal URL Exceptions. Note that uploading the patch achieves the same effect as the second workaround.

  • To avoid the same possible issue with other iOS versions to be released in the future, we recommend using one of the two workarounds:
  • 1. Add “OS 11_4” in addition to “OS 11_3” to Portal URL Exceptions. This would only affect iOS 11.3 and 11.4 devices.
  • 2. Add “OS 11_” to Portal URL Exceptions. This would affect iOS devices running versions starting with 11, including those that came before 11.3.

  • For more information, please contact 4ipnet Tech Support team at support@4ipnet.com

    Patch for Login Fail Issue Related to iOS 11.3 2018-04-24

    Regarding the recent release of iOS 11.3, we have received reports from customers stating that some users cannot login successfully using the web sheet on mobile devices updated to this version, and they would be directed to a page showing “Log in failed”.

    We have confirmed that this issue would occur under the aforementioned condition and is related to the behavior of this new iOS version. We are now releasing a patch for the issue.

    Please contact 4ipnet Tech Support team at support@4ipnet.com or visit 4ipnet Partner Center Portal for patch requests. Note that this patch is only for v3.43 (or above).

    For WHG/HSG models not supported by firmware v3.43, please use the following workaround instead.


    Workaround:
  • 1. Go to SYSTEM > General (Configuration path may be different depending on model)
  • 2. In Portal URL Exceptions, add “OS 11_3” (Note that there is a “space” between OS and 11_3)
  • Note: If using this workaround doesn't solve the issue for your model, please add "11_3" instead. And if the issue still remains unresolved, please refer to the workaround provided in our previous announcement "Workaround for Login Fail Issue Related to iOS 11.3 (2018-04-12)", which disables the Portal URL.

    Last updated: 2018/05/10

    For more information, please contact 4ipnet Tech Support team at support@4ipnet.com

    Workaround for Login Fail Issue Related to iOS 11.3 2018-04-12

    Regarding the recent release of iOS 11.3, we have received reports from customers stating that some users cannot login successfully using the web sheet on mobile devices updated to this version, and they would be directed to a page showing “Log in failed”.

    We have confirmed that this issue would occur under the aforementioned condition and is related to the behavior of this new iOS version. We are providing a workaround for this issue, which is to set the “Portal URL” in the particular Service Zone to “None”. Please see the workaround below.

  • Workaround:
  • 1. Go to SYSTEM > Service Zones > Select Your Service Zone
  • 2. Under Authentication Settings, set “Portal URL” to “None”
  • For more information, please contact 4ipnet Tech Support team at support@4ipnet.com or visit 4ipnet Partner Center Portal to access the firmware.

    New Patch and Updated Instructions for Facebook Login 2018-03-27


    In response to Facebooks’ recent changes to the handling of URI redirects for Facebook Login, 4ipnet is providing a patch as well as updated instructions on how to configure settings on its WLAN controller and in the Facebook Login App for continued support of Facebook Login on the WLAN controller. The technical guide on Social Media Authentication has also been updated and is available for download from the Partner Resources Library.

    Please follow the instructions below for continued support of Facebook Login on the WLAN controller.

    1. In the Facebook Login App, go to “Settings” and enter “https://your-internal-domain-name/loginpages/fb_callback.shtml” as the "Valid OAuth Redirect URIs". If the internal domain name is in the default setting, gateway.example.com is to be used as the internal domain name

    2. If “Enable HTTPS” is turned on, go to “System > General” on the WLAN controller and enable “User HTTPS Login”. To avoid seeing security certificate alerts before redirection to the login page, please obtain a valid security certificate for your domain name.

    3. Upload the patch to the WLAN controller. No rebooting is required. However, note that this patch will clear any existing patch. Please contact 4ipnet Support for further assistance if a patch has already installed on the WLAN controller.

    For more information, please contact 4ipnet Tech Support team at support@4ipnet.com or visit 4ipnet Partner Center Portal to access the firmware.

    Firmware Release v3.43.00 2017-12-19

    4ipnet today released new firmware updates for its WHG-series and EAP/OWL-series v3.43.00.

  • Key features updated in this version:
  • • OTP (One Time Password) Authentication
  • • Social Media VK support in Social Media Login
  • • User Bandwidth Throttling
  • • Per User Bandwidth Control through Split Tunnel
  • • HTTPs Redirection Enhancement
  • For more information, please contact 4ipnet Tech Support team at support@4ipnet.com or visit 4ipnet Partner Center Portal to access the firmware.

    Summary of KRACK WPA2 Vulnerabilities 2017-10-23

    1. As the recently discovered vulnerabilities in WPA2 affect all kinds of Wi-Fi client devices, we recommend installing system updates or patches provided by the respective Wi-Fi device vendors to prevent possible attacks.

    2. 4ipnet access points are affected by these vulnerabilities when in CPE mode (Wi-Fi uplink), but they are not affected when in AP mode and with 802.11r disabled. Thus, we recommend disabling 802.11r before 4ipnet releases its fix for these vulnerabilities.

    3. 4ipnet will include the vulnerability fix for all AP models in the upcoming firmware release (v3.43). Firmware version 3.43 is scheduled for release in the second week of November.

    For more information, please contact 4ipnet Tech Support team at support@4ipnet.com or visit 4ipnet Partner Center Portal to access the firmware.

    Thank you for contacting 4ipnet's support team. Please complete the form below and describe the issues encountered with as much detail as possible, so that we may provide you with better and more timely assistance.

    Contact Your Support Agent





    CAPTCHA Image

    4ipnet stands by the quality of its products - however, sometimes issues may arise. Before submitting an RMA request, please review the policies listed below.

    RMA Agreement

    By requesting an RMA number from 4ipnet, the customer agrees to the following conditions:
    • All returns should be properly packaged to prevent possible damage during shipping (see Packaging and Shipping Requirements below). Please ship with a tracking number in order to ensure the delivery of the product. 4ipnet is not responsible for items that are misdirected, lost, or damaged while in transit.
    • All parts replaced become the property of 4ipnet.
    • Any RMA service performed under warranty will not extend, change the product’s warranty, or create any new warranties.
    • It is the customer's responsibility to backup all configuration data before shipping the product to 4ipnet. 4ipnet is not responsible for any data that is lost during the diagnostic process.
    • Shipping and Processing Fees:
      • Product Under Warranty: If no defect is found, the customer will be contacted before taking further action.
      • Products Out of Warranty: 4ipnet reserves the right to refuse repair of a product for which the warranty has expired or has been voided. In the event that an Out of Warranty Repair is requested, the customer is responsible for all charges associated, including but not limited to the spare parts, processing fee, and shipping costs.

    RMA/DOA Procedure

    To receive RMA or DOA service, the customer must follow the policies listed below:
    1. Fill out all required information on the RMA Request Form and email the form back to support@4ipnet.com.
    2. After the RMA request has been verified by a 4ipnet representative, the customer will receive an email response with a RMA number and any other information associated with the RMA request, including (1) the designated return address of 4ipnet, and (2) the guidelines for documents required for customs clearance.
    3. Package the product to be returned carefully, in accordance to the Packaging and Shipping Requirements.
    4. Ship the product to 4ipnet as soon as possible - the RMA number is only valid for 10 days from the date of issuance. Any shipping costs must be paid upfront.
    5. In order for a product to be classified as DOA (Dead on Arrival), 4ipnet must be notified of the defect within 30 days of purchase date (invoice date).

    Packing and Shipping Requirements

    • Print out the completed RMA Request Form and place it along with the original invoice from 4ipnet inside the shipping box.
    • Ensure that the RMA number is legibly written on the return label affixed to the outside of the exterior packaging (please do NOT write on the original 4ipnet packaging). Returns without a valid RMA number will not be accepted, and 4ipnet is not liable for the loss or damage to unauthorized returns.
    • Follow the guidelines given when preparing the Invoice and Packing List for customs clearance, and list the RMA number legibly on these documents. If delivered via international carriers such as FedEx or DHL, specify “RETURN FOR REPAIR. NO COMMERCIAL VALUE. VALUE FOR CUSTOMS PURPOSES ONLY.” on the carrier’s shipping documents.
    • All DOA products returned to 4ipnet must be complete, in its original state, and in the original 4ipnet packaging (with all accessories intact).
    • Products that are damaged in transit due to insufficient packaging are subject to rejection of warranty repair and/or warranty replacement requests.