I can't really say how to fix your ISP issue, it may be a DNS issue, use Google's DNS instead, 8.8.8.8 / 8.8.4.4. Disabling bogons may also help.

Oh lawdy I just had to replug the modem while pfsense was on… which is also stupid, because it worked great on my laptop or any other pc, oh well... that's 4 hours wasted  :P

What are the specs of your pfSense box? Then- Id wonder if you have enough states set…  "System/Advanced/Firewall Maximum States" Default is 10,000. Look at "Status/System/State Table Size" and see what that reports during your test.

Hard to say what might have happened. Might need to see a copy of the config from after configuring the VLANs and before rebooting, if there is any way to get it.

@hassankazmi: If i give static IP on client side i remain unable to access internet services. Not a DHCP issue then, unless you have the DHCP server set to only allow certain clients in an 'allow' list.

I decided to just try a fresh install.  Thanks anyways.

Also might be interesting to see if there are errors on the NIC stats.

this appears using a draytek in half bridge mode, but this way will work….... On Pfsense 2.0 it shows the assigned isp gateway that is on a diferent subnet then it doesnt work........ How to put pfsense 2.0 behaving like 1.2.3 i.e show up ""link!" instead of the isp gateway not on the subnet making everything fail.. Regards

Actually, this is hilarious! Thank you very much for the squid advice as well. I'll look into it!

OpenVPN does a keep-alive on its own, IPsec does keep-alive if you fill in an IP of the remote LAN in the keep-alive box on the tunnel config.

If you're bridging 2 interfaces then you must use the same IP range on all interfaces. Can you clarify what you're pinging from where?

Just about all CF cards created in the last few years have wear leveling.  You'll be fine with that card and the 4GB NanoBSD image.

Using beta 2. Dosen't seem to have the problem…  yet :)