can pfsense resolve?  Under diag, try to resolve something - if pfsense can not resolve then anything using pfsense as dns is not going be able to go anywhere..

Thank you so much for the verification!!

My ISP attempted to hide the bridged mode setting using the CSS file for their web interface. ???
Like I said, attempted. ;)

That's great, thanks Jimp. I'll take your advice and install a new 64bit appliance with VMXNET adapters.

Much obliged!

I think I was having a problem like yours installing on an old Intel motherboard.  Windows would boot fine off a USB CDROM drive but pfsense would not.  I had to use WinDisk32 and write an image to a small USB memory stick, I want to say 4 GIG or smaller. Once I did this pfsense installed fine.  I downloaded Win32diskimage.exe.

thanks for that,  makes sense.  I had a router I was using as an access point but moved to a Ubiquity.

My laptop is a M SATA laptop with a spare slot. All i did was install the FULL version of PFSENSE to my M SATA drive, then took it out of the laptop then stright into the APU board.

If don rickles knew his shit when it came to IT then sure ;)

Looks like maybe you are using a serial memstick or NanoBSD and it's sending the rest of the output to serial console, not VGA.

Alright, I think I know what to do. Since the pfSense device isn't the DHCP server it needs an internal IP from my modem/router.

Not exactly, on pfSense you setup the WAN interface to use DHCP to automatically get a WAN IP address from the modem.
Because your modem is also a router, the address pfSense gets will be an "internal" RFC1918 address that cannot be routed on the Internet (192.168.x.x for eg.)
You need to make sure the pfSense WAN interface is setup for DHCP on IPv4, None on IPv6 and uncheck the box that says "Block private networks and loopback addresses".

Enabling DHCP on the LAN interface makes it so the rest of my devices can get their IP's from the modem/router and through the firewall (pfSense)? I do have a question about the upstream gateway… is that asking for the local IP of my modem/router? I entered that figuring that's what it meant but it didn't really seem to do much. Is that something that only gets configured for the WAN interface?

pfSense does provide DHCP on its LAN interface (make sure to set it up that way).
DHCP on the pfSense LAN interface is provided to all your attached devices so that they get an "internal" (RFC1918) address that matches the subnet defined for the LAN interface.
They will ask pfSense to tell them how to get "out to the internet" (or anywhere other than their LAN subnet).
The neat thing is they have no idea (nor do they need any) how pfSense does that, they don't know about the modem/router or the WAN IP

They know the address/subnet pfSense gave them and that the pfSense LAN address is where they can go to get "outside".
This why you DO NOT WANT to enter a gateway address anywhere, leave it at default and pfSense can make things work.

Another subtle gotcha in this setup is that the pfSense LAN subnet CANNOT be the same as the subnet handed out by the modem/router.
This goes back to my earlier advice to move off of the "default" RFC1918 addresses (192.168.0.x,192.168.1.x, etc)

As always, the description of these setups is always WAAAAAY longer than actually doing them.

@shoaib2:

what i doafter the installation of pfsense…

You do know this is a firewall, don't you?

It is solved.

The problem was the ISP device.
It was just a coincidence, after the upgrade didn't worked.

:)

Fixed. It helps when you have the wires plugged into the right holes  :-[

You can probably reinstall it from scratch with a stock version and be fine. Your config backup can be restored afterwards.