Firewalla Tutorial: Expanding With Docker Containers

Follow

Comments

11 comments

  • Avatar
    Alex Kac

    Questions:

    1. How do you keep docker running after a firewalla reboot? Right now I've got to go in and restart docker every time.
    2. How do we get Homebridge to respond or be on the same network as the main LAN?
    0
    Comment actions Permalink
  • Avatar
    Matt Chesler

    Alex, you should be able to keep docker running after reboot by running

     sudo systemctl enable docker
    2
    Comment actions Permalink
  • Avatar
    Michael Bierman

    This isn't working for me.

    Homebridge is running just fine, but can't be added to my homekit. Anyone notice that the WAN address is shown in homebridge when it is running on Firewalla? 

     

     

    0
    Comment actions Permalink
  • Avatar
    Michael Bierman

    Alex, make sure you point at your firewalla. For me, initially the URL given was wrong. Instead of my gateway, which is Firewalla at 192.168.0.1 it gave me my WAN IP. Switch to your Firewalla IP and specify port "8080" and you should see homebridge on Firewalla. for me that is, "http://192.168.0.1:8080/login"

    0
    Comment actions Permalink
  • Avatar
    Michael Bierman

    By the way, some great tutorials about homebridge/docker. It would be great to have a link to that in the tutorial.

    0
    Comment actions Permalink
  • Avatar
    Michael Bierman

    O.K. here is how to get homebridge working on firewalla Gold. After completing the steps above, you must do this:

    0. Confirm the homebridge container is running using the terminal as above or, open the UI

    http://yourfirewallaLANIP:8080

    1.You need to add "mdns": { "interface": "LAN-IP-of-Gold" } to your homebridge config.json file. Check this for more details https://github.com/homebridge/homebridge/issues/1957 For example, 

    {
    "mdns": {
    "interface": "192.168.0.1"
    },

         "bridge": {
         "name": "Homebridge Firewalla",
         "username": "1B:20:2J:1A:1C:4B",
         "port": 52175,
         "pin": "093-48-135"
    },

    Note, the username does not have to be the MAC address of your firewalla.

    2. Change the user name, PIN, and hostname in the homebridge config.json.
    3. Delete “persist” and “accessories“ dirs in homebridge directory.
    4. Restart the docker container.
    5. Open the homebridge UI in a browser,
    5. Add the homebridge accessory to Home by scanning the QR Code.

    Note firewalla will show an IPV6 address in the UI even if you have disabled ipv6. Also, it will report your WAN IP as the ipv4 address which isn’t standard for homebridge. Neither of these seems to impact things working though.

    0
    Comment actions Permalink
  • Avatar
    Michael Bierman

    Added a tutorial on the homebridge github side. 

    0
    Comment actions Permalink
  • Avatar
    Shawn H

    Thanks much! Works great now. 

    0
    Comment actions Permalink
  • Avatar
    BatraD

    thanks. wanted a place to run the Unifi controller since i got rid of the UDM 

     

    0
    Comment actions Permalink
  • Avatar
    Hans Hong (dyndragon)

    @Matt Chesler that command doesn't seem to have any effect. Tried it on my pi-hole docker setup on FWG. I still have to manually start up the pi-hole docker. Everything else inside the pi-hole configuration persists though, which is good.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    @Hans, the persist code will be in 1.971 for the Gold; we will update the document once it is ready.  (as the time of this message, should be very soon)

    0
    Comment actions Permalink

Please sign in to leave a comment.