PF 2.2 Fresh install - limited WAN connectivity.

KDog

Hello all,

Dell R210 running HyperV server core 2012r2, only guest is the PFsense 2.2 machine. Fresh install, not an upgrade. I have no "internet" and limited IP connectivity on the wan.

PFsense diagnostics ping - source address WAN I can ping the following (everything IPv4):
ISP Gateway address
ISP DNS address
8.8.8.8

From a computer on the LAN I can only ping ISP GW. I cannot ping the ISP DNS, 8.8.8.8 or any other public IP.

I have turned off the firewall using netsh in hyperV.
I created a Firewall rule to enable incoming ICMP on the WAN address and I receive a response when the rule is enabled.

From this is it safe to assume that my hypervisor network config is all ok (as I can ping my ISP and 8.8.8.8 from the WAN interface, and receive a ping response from the WAN)?

I have been trying to work out what the issue is, at first I thought maybe DNS, but if I can't ping IPs then I haven't got to that stage yet.

At the moment I am back to my 2.1.5 release on bare metal.

The DNS resolver seems to have a few issues. During boot I get the following message:


Starting DNS Resolver...calcru: runtime went backwards from 3596 usec to 1818 usec for PID 13485 )rrdtool)
calcru : runtime went backwards from 1980 usec to 1001 usec for pid 10697 (inetd)
""pid 6772 php-fpm
""pid 5646 mpd5
""pid 5646 mpd5
""pid 5226 syslogd
""pid 277 devd
""pid 268 php
""pid 268 php
""pid 265 check_reload_statur
""pid 245 php-fpm
""pid 245 php-fpm
""pid 60 md0
""pid 21 sh
""pid 21 sh
""pid 7 sctp_iterator
""pid 5 fdc0
""pid 4 cam
""pid 14 geom
""pid 13 ng_queue
""pid 12 intr
""pid 1 init
""pid 0 kernel
done.
Starting NTP time client...done.
Starting............... All good after this

Even though this is a DNS resolver issue could this be effecting IP address pings etc?

Does anyone have an idea of what could be going on? Should I just delete the VM and try a fresh?

Any help appreciated.

KDog

Whoa,

Got this working.

The interface used for WAN under hyperV (sconfig, not vswitch in VMMC) was set to DHCP.
I set this interface to static:
IP = ISP Gateway ip (don't think IP matters)
Gateway = ISP gateway IP
DNS = ISP DNS ip

So in CMD prompt it appears as going to my ISP. LAN interface was already set to the same subnet range as PFsense LAN.

So now everything it working fine for internet traffic etc.

What do I do about the DNS resolver issue in bootup? Should I still go for a reinstall with regards to this?