MAAS documentation is unclear regarding proxied node traffic

[Nick Niehoff]

The documentation for MAAS is not clear for versions < 2.5 that some node network traffic goes directly to the region controller. Also for 2.5 the documentation is not clear as to what traffic is now proxied through the rack controllers to the region controller.

[Andrew B. (drewboswell)]

+1, this is problematic for knowing what traffic needs to be authorized between network zones/firewalls etc. The information is needed to form a complete view security wise.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

[Igor Gnip (igorgnip)]

Adding note that gateway and dns setup is not documented enough.

In case of evaluating "closest" http proxy, maas evaluates differently when nameserver / gateway is set manually vs left unpopulated.

I believe this deserves another chance to get fixed and documented.

[Igor Gnip (igorgnip)]

in this bug report it was explained how setting of dns servers influences resulting proxy url
thus direct or via proxy communication:

https://bugs.launchpad.net/maas/+bug/1837903

We could really use some clarification on direct vs proxied traffic

[Bill Wear (billwear)]

Yeah, I agree this needs fixing. We have been a little hand-wavy about DNS and DHCP in a lot of places, at least by my standards. It should be crystal clear, down to the protocol diagrams if necessary. Assigning this to me.

[Jerzy Husakowski (jhusakowski)]

Many of these issues have been fixed in MAAS 3.2.7 and MAAS 3.3. Are these problems still reproducible on these versions?