Wireless Access

last person joined: 15 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

VIA requirement and config.

This thread has been viewed 2 times
  • 1.  VIA requirement and config.

    Posted Dec 01, 2012 02:16 AM

    Hello,

     

    My client have VIA installed on his device and he asked how can he connect to the internal network using it.

     

    I told him you need a Public IP and VPN-PEF License.

     

    Does the public IP need to be installed in the controller or it can be directed from FW IP address ?

     

    What configuration is needed on the controller ?



  • 2.  RE: VIA requirement and config.

    EMPLOYEE
    Posted Dec 01, 2012 07:55 AM

    If the controller has a public interface that will work.

     

    It will also work if your firewall provides a static NAT from a public address to the private address of the controller and then permits the VIA protocols inbounds.

     



  • 3.  RE: VIA requirement and config.

    Posted Dec 08, 2012 11:32 PM

    I think the best way to go is with the firewall option...


    Why i say that?

    Because think about it.

    1-You will then have to do change in the configuration... thinking is on the same subnet(i mean the firewall ip address and the one you want to put on the WC.  Change like the Default gateway of the WC and add internal routes pointing to the switch is routing, that if your controller is not routing because if it routing the wlan then its not possible.

    2-You will have your WC with a public ip address directly whichi dont like too much that idea

    3-You will be totally wasting one of the client ip addresses..  As with the firewall option you could use oneof the ip addresses that he is already using for some other port forwarding....

     

    Anyways personally i dont like that option.... unless i dont have another choice....