Firewalla's IP address

Comments

5 comments

  • Avatar
    Firewalla

    Make sure you don't have another dhcp server running, it is pretty rare (unless you use static IP) to have firewalla having the wrong address and still operational

    0
    Comment actions Permalink
  • Avatar
    Philip Weissman

    Thanks. I think my Fios ONT may be a dhcp server. This would be news to me but it's the only thing that makes sense. Other than devices, I only have a Unifi managaged PoE switch, APs, and a Cloud Key. The reason I suspect the Fios ONT  is that the IP address 192.168.1.1 takes me to a Verizon router loggin page. I don't have a Verizon router and my ONT does not have password information written on a label. 

    I have my old ORBI RBR50 sitting around, set in AP mode. Tomorrow, when I can disconnect the internet without getting screemed at, I'll connect it directly to the ONT and see what happens. 

    0
    Comment actions Permalink
  • Avatar
    Philip Weissman

    The IP address of my LAN is 192.168.66.1 I created a VLAN on the Purple with the ID 76. I then created the VLAN network, IoT, in the Unifi app with the same ID and name. Then I changed the Network associated with a second SSID to IoT. After I save, clients in the Firewalla app disappear after a reconnect. The IP addresses on the Unifi app change to addresses with the subnet, 169.254.0.0. This indicates that the DHCP server isn't reachable? DHCP settings (none/server/relay) in the Unifi OS didn't help.

    Wondering if this can be caused by the Firewalla having the wrong IP address.

    I've think I followed the Firewalla documentation properly and did my best with the Unified app. Need help.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    When you define a VLAN on the firewalla, did you do the same on your switch? and also, did you connect a trunk port (tagged port) from the managed switch to firewalla? 

    0
    Comment actions Permalink
  • Avatar
    Philip Weissman

    Thanks. Yes, the problem was the port to the Firewalla got auto-set to the LAN. I just had to turn it back to a trunk port and now WVLANs and port-based VLANs are working.

    Also think I resolved the firewalla IP address issue or at least have a better handle on it. The IP address from my Failover wifi WAN is 192.168.1.164. I'm accessing a neighbor's wifi. This IP address appears as the Firewalla IP address which seems a bit strange since my LAN IP is 192.168.66.1. So I think this means that I do have a second DHCP server on my system? Is this a problem?

    0
    Comment actions Permalink

Please sign in to leave a comment.