How do I get HTTPS CP login working across multiple interfaces?



  • Question: How do I get HTTPS CP login working across multiple interfaces?

    I have interfaces:
    WAN: dhcp
    LAN: 10.33.0.0/22 - IP 10.33.0.1 - DHCP serves 10.33.1.1 ->.3.254 - GW 10.33.0.1 - DNS 10.33.0.1; 8.8.8.8
    WAP: 10.33.4.0/24  - IP 10.33.4.1 - DHCP serves 10.33.4.16 ->254 - GW 10.33.4.1 - DNS 10.33.4.1; 8.8.8.8

    From what I can figure…

    Without HTTPS, CP catches traffic at the gateway IP, i.e 10.33.0.1 for LAN, 10.33.4.1 for WAP which works fine.

    But HTTPS login for CP requires a FQDN e.g.: cp.domain.org

    I have TinyDNS running but can only assign one IP to cp.domain.org

    How do I get LAN and WAP to resolve the FQDN to different IP's ???

    Cheers
    ragman



  • You can't make it resolve differently, it should work if you just add one of the internal interface IPs of the firewall as an allowed IP entry in CP and leave the DNS pointed to that.


Log in to reply