Index Page
Our Thought in One Place

  • We are happy to introduce our Radius Authentication and Captive Portal Service for Wireless providers. We offer this policy service so that  wireless providers  can customize their captive portals to fit their customer needs. VNE’s radius service also has the ability to decode Custom AVP’s in the radius message and change the Policy per Subscriber based on these custom variables.

    Screen Shot 2016-12-09 at 9.59.22 AM

    Here are some of the features of our Service.

    One of  the unique features of our service is to visualize the subscriber interactions using Ladder Diagrams in real time, this helps us in identifying signaling problems, inter-operability between vendors and the various systems that the end-subscriber goes thru before getting the Service.

     radius_ladder

    Customers can customize their captive portal from the browser. We are planning to make this complete configurable including the fonts, css and other options. We would love to hear your feedback on this feature.

    Screen Shot 2016-12-09 at 9.49.16 AM

    Corresponding Captive Portal Snapshot,

    Screen Shot 2016-12-09 at 9.51.54 AM

    You can add the subscribers using our REST API or using the Bulk additions using CSV file uploads.

    Screen Shot 2016-12-09 at 9.54.05 AM

    You can simulate the signaling and do the end-to-end testing for your service using our simulation stack.

    Screen Shot 2016-12-09 at 9.55.57 AM

    Finally, we have complete support for Diameter stack (All Interfaces) where we can Inter-operate with 3G/4G Service Providers for seamless mobility into your wireless network.

    If you are interested in testing our service with your network, please contact us  radius@vne.io

  •  

    Built on Micro-Services.

    vne.io’s  SDN controller is built on loosely coupled  components like Redis, Clojure Eco System for API, Graphite and Graphana. Our main controller component is built on Intel DPDK and automated protocol encoders and decoders. We use Redis DB features to connect diverse technologies to work in a cohesive and well integrated environment. This also opens the door for customization where developers can plug in their custom graphing and data collection eco system in to the controller’s output.

    DPDK Integration.

    We wanted our controller to scale to large number of  end points (both white box switches and vSwitches). We leveraged the Intel DPDK technology to handle large number of concurrent TCP sessions and also to handle very high number of messages per session. In our preliminary testing, we could easily get 20K messages/sec handling capacity per CPU thread.

    CM automation with NERD API and  how to get started.

    Our SDN controller has support for NERD Client and API. NERD is our custom API that is a combination of Netconf. and Redfish protocols. We have complete support for Netconf. concepts like Running Configuration and Candidate Configurations. At anytime, there is only one Running Configuration and multiple Candidate Configurations. Users can clone an existing configuration, modify it and activate the configuration as a transaction. As of now our controller supports Openflow1.3, LLDP and STP protocols. We plan to support OVSDB, Openstack ML2 pluggin, BGP-LS with PCEP in future iterations.

    To get started, please visit our github page  and see the above video for the quick demo on our SDN controller. We plan to provide complete support and many other features on our controller, please stay tuned to this blog or follow our Linkedin page.