

My clipboard isn't working right atm, which is why I haven't infodumped.

I am hoping the collective power of Reddit can succeed where all others have failed. netstat -rn does show the IPs corresponding to the vboxnet1 network in the routing table, so clearly they are there and being blocked by some firewall.įor sake of completeness, my OS X firewall is off. Preliminary investigations suggest that An圜onnect isn't actually using pfctl to do its magic. I cannot for the life of me figure out if I have to configure something using pfctl and, if I do, how to do it. I have discovered that Yosemite uses PF instead of ipfw (in Mavericks I fixed this by deleting the deny all rule in ipfw after connecting to the VPN). At the exact instant I fire up the Cisco An圜onnect VPN client and connect, I can no longer ping VirtualBox VMs over their host-only networks.

It would get an A+++++++= for its ability to respond to pings. When I'm not on the VPN, I can ping the packets out of my VM.
