from a sysadmin point of view it doesnt matter. not very helpful.
from a vagrant task, a shell provisioner should do the trick. shutdown firewall and disable if you are happy with this. and also is the option you disable the firewall, and repackage, or with packer you create your own. seems hfm4/centos7 is not longer a public box. On Tue, Sep 23, 2014 at 2:12 AM, Nick Howes <[email protected]> wrote: > Hi > > I've recently been doing multi-VM setups with Ubuntu boxes and a private > host-only network, so the boxes can talk to each other and the host can > talk to the boxes. Then I moved to CentOS 7 and suddenly the boxes wouldn't > communicate. It turned out to be the default firewall in CentOS 7, or at > least in the "hfm4/centos7" base box I'm using. I disabled the firewalld > service and it works fine. > > My question is: do you think this is something that the user of a base box > should care about and deal with in their provisioning step, or should there > be something in the base boxes documentation about the recommended default > firewall configuration? Or should Vagrant itself even handle this as part > of network configuration? The latter sounds like a pain as there are as > many firewall setups as there are Linux distributions. > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
