![]() If you made it a child, you'll see a bunch of apps greyed out, those are inherited from the parent. At this point you can click the back to apps button, and now if you click that default rack drop down you'll see the new rack you made and you can select it. Once you SAVE (bottom right), the new rack will be created. You can make that policy a child of a parent rack, this makes the child inherit all the modules and settings from the parent. ![]() You'll need to create a policy, that will make the new "rack" along with it. So on the apps tab of your Untangle UI, click that drop down in the top left that says default rack, and hit manage policies. So given the current version rack and policy are interchangeable, and you use Policy Rules to define what policies (racks) are used in any given circumstance. Now the jargon gets a little muddy because Untangle refers to things as racks on one side, and policies on the other. With Policy Manager you can make more, as many more as you want. When you log into your Untangle, and click the apps tab, you see a list of applications that each looks like a racked server, that's not accidental! It's literal! Each application is a separate virtual server operating in side a virtual rack, that rack is the default rack. ![]() Untangle uses a concept known as the virtual rack. ![]() I suspected as much but I try to limit the hand holding unless specifically indicated otherwise.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |