On Sat 18 May 2013 13:24:52 NZST +1200, Jim Pingle wrote: > Why "host only"? That may not let it go out.
It doesn't need to on LAN. DNS queries are resolved from WAN, and that is bridged in VB, and DNS servers on the Internet can be queried by dig on pfsense correctly. The VB interface used for pfsense-LAN is host-only, and it works fine for the webconfigurator. I had removed the RFC-private and bogon blocks from WAN too. > > I conclude that dnsmasq is not functional inside virtualbox, making > > pfsense config testing impossible. > > Not true, I do almost all of my testing locally here with pfSense in > VirtualBox and it has zero issues. That's what I was expecting, but fact is dig @localhost on pfsense does nothing, but web servers on the Internet can be reached (by their IP), and [email protected] google.com works. > Any issues you're seeing are likely > with the network config or NIC config, VM resources, etc, but not > VirtualBox in general or pfSense. Hmm, where do I look? 512MB RAM, default pfsense config, no packages ought to be enough. > I use bridged NICs for WANs and then Internal Network setups for the LAN > side. My VB config is the same except I have host-only for LAN. As the webconfig traffic goes in and out OK I see no problems here. How/where is dnsmasq configured to pick its servers from? > There are so few postings about VirtualBox because in general there > aren't many/any issues with it. It works fine. Well damn it, after the "windows-solution" (aka reboot) it works fine now. Hmmm. There isn't anything I can think of that I changed, I changed very little from the default. Looks like dnsmasq need a restart for some reason. Never mind. Thanks muchly Jim, Volker -- Volker Kuhlmann is list0570 with the domain in header. http://volker.dnsalias.net/ Please do not CC list postings to me. _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
