You can reset the IP from the console with menu option 2. So how is your VM host setup? How does the pfSense VM connect to other machines? Where are you trying to connect to the LAN from? You said that it was working until you added the static WAN address. That implies that you have an IP conflict of some sort. However in that case I wouldn't expect you to be able to connect via SSH.  :-\ Steve

check out this cool video which will help you. http://www.youtube.com/watch?v=Usi195rK35I

YOU ARE GREAT  ;D ;D finally it works ! big thanks to you, you made my day !

If you compile a working kernel module against FreeBSD 8.3 then the procedure for adding it would be the same yes. I'm going to suggest it's not an AR813x or AR815x since those should be supported by the alc(4) driver in FreeBSD 8.3. Steve

Would be nice with a feature on the pfSense to bring interface up and down if there is no traffic…  Anyone tried creating a custom script for this ?

If each app is served internally from a different IP address it doesn't matter if they all use port 80. Steve

Sorry made a mistake, already amended the post: System -> Advanced -> Firewall/NAT NAT Reflection mode for port forwards: Disabled I think this problem is resolved. Please kindly see this thread for a more troublesome problem: http://forum.pfsense.org/index.php/topic,70483.0.html

i had a similar issue. time warner cable modem to a desktop i turned into a pfsense box. the desktop had dual NIC built into the mother board. I used one of them for wan and one for lan. Had it constantly not passing traffic to the internet and could not access the web gui from the lan side. could only fix it by restarting the pfsense box. Finally installed a new pci nic into it and plugged one of the cables into the new nic and reconfigured the interaces and viola! its been running steady without a reboot for over a year now.

Come to find out after I released the supplied KVM, that night 'something' happened and the system was down. The wonderful times when you know you have things setup correctly and cannot connect, but no way to connect top the machine in question to find it's down. The issue with raid cards continues on and I should have known better.

Ah, sorry about that.  :) It's often a delicate balancing act, here on the forum, between coming across incredibly patronising or spouting indecipherable code. Either one can be insulting or confusing or both! Can you show us a screen shot of your firewall rule? If it's working OK for you then don't worry about it. I'm not sure any of the filtering solutions in pfSense will meet your requirements as you have described. All of them would require logging into pfSense and manually making changes, some admin work. I have almost no experience with on device content filtering, none at all on the iPad, but it seems more likely to work in your scenario. Steve

Valid point!!! If doesn't have the ability to do span/mirror ports on his switch - can just install say wireshark on the machine in question to see other traffic it might be sending that is not dest internet.

Thanks guys!  I ended up upgrading to the latest version of pfsense and re-installing the new exported client and it works fine!

@stephenw10: You will see traffic passing between two internal interfaces vlan or not. The only way you wouldn't see that is if your switch is layer 3 and is setup to route between the vlans. Steve thanks.  that does make sense.

Thank you all very much … The way I found to solve it was back a backup that ha had done a month ago ... Being that I have not changed anything in the settings ... Very Strange ... Given as solved then ...

It's not a private IP address. Do you own that IP? Steve

Exactly. 1. All switches default to one VLAN across all ports, almost (?) always VLAN1. 2. Nope but this is the reason some people don't trust VLANs for separating network segments especially, say, WAN and LAN. That and the possibility that your switch firmware has some exploitable bug allowing packets to change VLAN, never seen that either. 3. Some switches have an unmanaged mode they default to that is indicated somehow. The Dell PowerConnect range, for example, have a managed mode LED on the front that tells you the switch has been configured away from it's default state. If it did default back to unmanaged mode the LED would go out, you would know. Steve