This is the method I prefer: https://www.infotechwerx.com/blog/Prevent-Any-Traffic-VPN-Hosts-Egressing-WAN

I found that under gateway > settings > advanced options I enabled it and I got net access in ma pfsense machine. But for lan its not loading any web pages. I cant ping to the given gateway (via pfsense console), but can ping Google. and when I traceroute  Google, It shows * after the public ip (in the gateway portion) and then traced Google.

You seriously broke something in the process. You'll have to reinstall via USB. If you're getting the same end result screen as what you show there when booting from USB, then you aren't actually booting from USB. Probably because it's not a properly written bootable USB drive.

That's almost certainly your modem. 4 ms is too low for it to be traversing the coax and looks to be too consistently 4 ms for that as well. I haven't heard of anyone else seeing anything like that. Though there is some buggy firmware going around on TWC for SB6183 modems, I'd only heard of it breaking IPv6, not doing stupid things with IPv4. See this thread for instance, and the links to dslreports there. https://forum.pfsense.org/index.php?topic=108971.0

@Clouseau: Okey - I have the same problem than diablo266 - should I start a new thread? Not if you actually have the same problem. At this point, this is a well-established known issue, and we don't need any further specifics as we have a replicable test case and are working on finding the root cause. Can follow here for updates: https://redmine.pfsense.org/issues/6296

as my daughter would say "like a boss" worked a treat,  many thanks to you sir :)

If you upgraded from 2.3 beta, you may still have 250ms as the polling interval. This was the default earlier in the beta process. The current default is 500ms. FWIW, by default dpinger uses a data payload of 0 bytes, so the packets are much smaller than a standard ping which is a 56 byte payload.

Thank you. I will read and try it. Best,

I had no problem with this board. I followed an instruction in the forum. Gently –-- <soapbox>Just because it worked and you "had no problem" doesn't mean it's a good idea.</soapbox>

I guess that's why people have been asking for the ability for that screen to "remember" what you last used.

Yep, memory test is another good suggestion. Along those lines, you might look in the GFX section of the BIOS, see if you can decrease the shared memory usage (for Video) down to as little as possible. pfSense is a text only console, it doesn't need large amounts of memory for graphics.

Have you tried to shell into the box? Will it respond to pings on either LAN or WAN? Do you have access to the console? Is this bare metal (what type?) or VM?

@cmb: No change between versions there. Guessing maybe you have manual outbound NAT configured and it doesn't cover that VLAN's subnet out WAN. Hmm you are correct, 1 rule has been missing from outbound NAT, must have been due to new GUI and I probably hit the wrong icon to copy+add new. I have another issue I'm investigating, I will update once I figure out if it's a true bug or not.