To add to this, as I also am experiencing this problem: My maas has 2 nics and 2 networks: Outbound eth1: talks to the world (or in thsi case my partner OEM's lab network Private eth0: talks only to maas-create nodes. Call it 10.0.0.0/24 .
I've set up maas as DHCP & DNS manager for eth0. I have *not* NATed eth0 as the Partner OEM does not like private NATs on its lab network. My /etc/resolv.conf, /etc/maas/dhcp.conf and /etc/dhcp/dhclient.conf are saying the right things. When I create node1 (using fastpath install) I can ping other things on the 10.0.0.0/24 network (by name or address) but cannot ping google.com (even though the name resolves correctly). If I turn on NAT this works. This makes post-node-startup installation and configuration very problematic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304613 Title: nodes can't get out to the internet beyond the maas server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
