This post is to explain a solution to a problem I encountered when using an Astaro VirtualBox VM to filter internet traffic for other VirtualBox VMs on a VirtualBox "Internal Network".
I recently installed Astaro version 8 in a VirtualBox VM. In VirtualBox, I assigned two NICs to Astaro: One "attached to" "NAT" and one "attached to" "Internal Network" that I named "astaro". I then had other VirtualBox VMs connected only to the "astaro" VirtualBox internal network. This allowed Astaro to get Internet access through my host computer from the "NAT" interface and for the other VMs on the "astaro" internal network to access the Internet through the Astaro VM.
However, even though I could access the Astaro WebAdmin from one of the other VMs, I could not access the Internet. I discovered that DNS queries were resolving to an IP, but no other traffic would pass through. Ultimately, I changed both network cards for the Astaro VM in the VirtualBox configuration from the default PCnet-Fast III to Intel PRO/1000 MT Server, which miraculously solved the problem, although I don't know why.
Prior to discovering this solution, I had ensured the VirtualBox NICs were assigned to the appropriate Astaro NICs (i.e., the virtual NICs were appropriately assigned to the WAN and internal NICs as shown by Astaro WebAdmin). I also ensured the appropriate rule sets were configured, which they were since I configured the Astaro via the installation wizard.
This thread was automatically locked due to age.