You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a few docker containers installed on my Firewalla Gold.
I have noticed the following during its installation.
Inability to change the IP address range via the application from the standard docker range. I don't want to break it.
Duplicate bridges created that in my humble opinion are not required complicating the Firewalla Gold configuration.
Suggest solutions.
Docker compose allows for many docker containers to be launched within a single docker compose file
Amalgamation within application of direct manipulation of the "master docker compose file"
This would include the IP Address range of the docker engine, and all services added to the docker compose file along with subsequent changes required to the Firewalla
Docker normally sits way outside of the range most people employ within their networks (assuming router mode in use)
By utilizing an app interface on a master docker-compose file it would be easier to bring docker to heal - so to speak
This in turn could be enabled within the application to steer custom DNS entries - albeit with manual override.
For example - Ubiquiti Console on IP address 192.168.3.1:443 and MISP on 192.168.3.1:4443, or something else.
LAN would exist on 192.168.1.X and Wireshark VPN on 192.168.2.X.
Humble suggestion based on the hardware listing of the Firewalla Gold
Obviously, you don't want to get carried away. We need metrics on loading. These are available via MSP subscription.
Maybe we need a Platinum device (twice the number of ports, larger RAM, more grunt, larger storage - in that order)
The best thing about Firewalla is it is all software mapping as long as you have the grunt, memory and storage.
Yours Sincerely
Leon.
The text was updated successfully, but these errors were encountered:
I have a few docker containers installed on my Firewalla Gold.
I have noticed the following during its installation.
Suggest solutions.
LAN would exist on 192.168.1.X and Wireshark VPN on 192.168.2.X.
Humble suggestion based on the hardware listing of the Firewalla Gold
Obviously, you don't want to get carried away. We need metrics on loading. These are available via MSP subscription.
Maybe we need a Platinum device (twice the number of ports, larger RAM, more grunt, larger storage - in that order)
The best thing about Firewalla is it is all software mapping as long as you have the grunt, memory and storage.
Yours Sincerely
Leon.
The text was updated successfully, but these errors were encountered: