Security

last person joined: an hour ago 

Enterprise security using ClearPass Policy Management, ClearPass Security Exchange, IntroSpect, VIA, 360 Security Exchange, Extensions and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

Using HTML5 video on Captive Portal

Jump to Best Answer
  • 1.  Using HTML5 video on Captive Portal

    Posted Jan 20, 2016 01:00 AM

    Our client requires to play a video on Captive Portal.

     

    I uploaded an advertisement video and tried to use html5 video tag, but it didn't work.

     

    I found a topic related to my problem, but I didn't force them watch,

     

    Here's my code.

     

    <center><video width="880" height="500" autoplay>
    <source src="movie.mp4" type="video/mp4">
    Your browser does not support the video tag.
    </video></center>

     

    Thanks for your help



  • 2.  RE: Using HTML5 video on Captive Portal

    Posted Jan 20, 2016 09:58 AM

    What are you seeing on the client?

     

    HTML renders client side so the controller is just serving up the HTML page.



  • 3.  RE: Using HTML5 video on Captive Portal

    Posted Jan 21, 2016 08:01 PM

    It didn't work on Android platform and iOS.

     

    The video frame shows black. 

     

     



  • 4.  RE: Using HTML5 video on Captive Portal

    Posted Jan 21, 2016 08:58 PM
    Where is the video hosted?


  • 5.  RE: Using HTML5 video on Captive Portal

    Posted Jan 21, 2016 09:10 PM

    I uploaded a video to my aruba 7210.

     

    The filename extension is MPEG4.



  • 6.  RE: Using HTML5 video on Captive Portal
    Best Answer

    Posted Jan 23, 2016 09:12 AM

    You should do a decrypted packet capture on the client to see what is being communicated:

     

    (Aruba7640-US) #packet-capture destination local-filesystem                     
    (Aruba7640-US) #packet-capture datapath wifi-client <mac address of client> decrypted 
    (Aruba7640-US) #show packet-capture datapath-pcap

    The "show packet-capture datapath-pcap" command will show you the traffic going back and forth to see what is being transmitted and the port.  For the actual packet capture, you will need to take the logs.tar with tech support from the controller and look for the datapath.pcap for the actual packet capture so you can see what the client is communicating back and forth.

     

    When you are done, make sure you type "

    no packet-capture datapath wifi-client <mac address of client>