Results 1 to 5 of 5

Thread: Restricting viewers by IP using wildcards using Streaming Engine

  1. #1
    Join Date
    May 2010
    Posts
    2

    Default Restricting viewers by IP using wildcards using Streaming Engine

    I have been asked to restrict a VOD file to our organization only. We have a class B block of addresses.

    I scoured the forums and articles and saw that the Streaming Engine allegedly has this built in, so I just upgraded from Server 3.1.1 to Streaming Engine 4.04 on a Windows Server based on an article that said that the Streaming Engine incorporated this function in its core.

    However, when I try to use an IP restriction using wildcards (ie: XXX.YYY.*.* where XXX and YYY are part of our organizations IP address block) on a VOD application, I get a message that I am using an invalid IP addresss.

    A comma separated list could have a huge number of IP addresess, so the wildcards are essential.

    Is this an implemented feature? I see a comment that says it may be imlemented in the future, but that doesn't help me now.
    Last edited by vmsvid; 07-01-2014 at 02:41 PM.

  2. #2
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    There is a customer contributed version of limit playback by IP that should work with wildcards here

    You would have to build this in the IDE. I will put it in the backlog to add to the version in the module collection.

    Richard

  3. #3
    Join Date
    May 2010
    Posts
    2

    Default

    I believe it is solved. I did send in a support request and the recommendation was to manually edit the application.xml file to include the wildcard string, instead of using the GUI to add it.

    By manually editing the applications .xml file using the wildcard string, the Engine Manager GUI for Outgoing Security sees the string as valid, and some preliminary testing indicates that the wildcard string is used as I hoped.

    People outside our network, who have tested this, cannot playback the test file. If they VPN into the network, they can. I have tested from within the network and playback is fine. I have access to a guest network, with a different IP address block, and the restriction kicks in.

  4. #4
    Join Date
    Sep 2011
    Posts
    1,920

    Default

    Hi,
    That's great news, thanks for the update.

    Regards,
    Jason

  5. #5
    Join Date
    Apr 2016
    Posts
    1

    Default

    Hi vmsvid,

    Can you share the code?

    Thanks

    Quote Originally Posted by vmsvid View Post
    I believe it is solved. I did send in a support request and the recommendation was to manually edit the application.xml file to include the wildcard string, instead of using the GUI to add it.

    By manually editing the applications .xml file using the wildcard string, the Engine Manager GUI for Outgoing Security sees the string as valid, and some preliminary testing indicates that the wildcard string is used as I hoped.

    People outside our network, who have tested this, cannot playback the test file. If they VPN into the network, they can. I have tested from within the network and playback is fine. I have access to a guest network, with a different IP address block, and the restriction kicks in.

Similar Threads

  1. Google Compute Engine trouble when trying to set up wowza streaming engine
    By CBBrewCo in forum Wowza Streaming Engine in the Cloud
    Replies: 1
    Last Post: 06-27-2014, 02:55 PM
  2. Monitoring & Restricting Server Connections & Altering Video Bitrate
    By sgopalkr in forum Performance Tuning Discussion
    Replies: 15
    Last Post: 10-22-2012, 04:43 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •