I would recommend using loose-mode reverse path filtering on the MAAS
server for now.
Strict reverse path filtering seems like it would make a lot of sense
for a border router, but little sense for an internal MAAS server.
But I agree that it makes sense to supply a cloud-config-url (and
related URLs) using a directly attached subnet if possible. Right now we
use the subnet to select a rack controller, and we use the rack
controller to select the appropriate rack-facing subnet on the region.
But I like the idea of taking a simpler approach and using an on-subnet
IP address if possible.
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Wishlist
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665680
Title:
Deploying nodes in multiple VLANs fails due to RPF filtering
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1665680/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
