Instant On - Wireless

 View Only

Mesh setup not working because of limited DHCP ?

  • 1.  Mesh setup not working because of limited DHCP ?

    Posted 04-12-2023 12:32 PM

    Hello Aruba gang,

    Im trying to setup a small Aruba instant on setup to deliver internet via Startlink for  a remote /temporary reconstruction site

    One central AP is connected to a Peplink router that's connected to the starlink and then 2 AP'S in mesh

    The startlink reseller owns the peplink and only wants to hand off 2 IP's via DHCP 172.16.99.10 and .11

    I connect my Central AP to the peplink and it gets IP 172.16.99.10 , the other AP's are never able to connect, But if I connect 2 android phones as a test one gets 172.16.99.11 the other gets nothing from PEPLink DHCP

    So to have my clients work I need to enable IP assignment specific to this network (I chose 172.16.17.0), and that's fine

    When I set this up with a regular internet router for home use , it works perfectly to mesh the 2other AP's

    At the moment  I assume that the mesh AP's also want an IP in the 172.16.99.0/24 but are not reaching the outside?

    Is there a way to force them into a mesh mgt vlan or something to connect to the aruba portal via a range and IP defined by and the central AP ?

    I was doing some googling and its also unclear to me if my central AP is already in Routing mode or stuck in network in private mode is this somewhere clearly defined in the portal ?

    Thx for reading and possible feedback



    ------------------------------
    Rue
    ------------------------------