Thanks for response Steve. No traffic shaping, running Squid and Light Squid only. It looks all the issues were Squid related. I found bunch of errors in log, where system was continuously trying to start squid service. I removed Squid which resolved all other issues I mentioned. The Packages are available now and GUI is responsive again. I tried to reinstalling Squid packages multiple times but cannot get Squid service to start. I will do some research around Squid, now that I know what the main issue is. Thanks again, GBR

Hmm. Bizarre. Is it possible you've somehow changed the LAN address but still have the firewall rules set for the old address? No idea how you might do that, it shouldn't be possible. presumably you have access to the console? Try looking at the firewall and system logs using clog: https://doc.pfsense.org/index.php/Why_can%27t_I_view_view_log_files_with_cat/grep/etc%3F_(clog) You may just have a very flaky Realtek NIC that is crapping out on you. You should see something in the system log if that's the case. If the pfSense box is blocking access to LAN for some reason your attempts to access it should appear in the firewall log. Steve

The original install I wasted 8 hours on was a 100 gig SSD. For the sake of these screenshots it was a 30 gig SSD, yet had the same errors as the 100 gig SSD and the 64 gid USB thumb drive. The machine I installed on is temporary until APU boards start to ship. I didn't think I would need to pull memory out to load PFsense.

fxp is an Intel 10/100 NIC. What hardware are you using? Steve

@jimp: Try it again. That particular server had an issue but it should be back to normal now. Looks good.

Bad punctuation.  Pretty cool though.

Ok, I dont know what is going on. Its working fine now. I changed nothing at all. I released and renewed a ton of times the WAN interface, unplugged and plugged back in the modem power. It seems to be having a hard time obtaining an IP address from my ISP. When it finally came back up with an IP address, the number had changed from a 71.x.x.x value to a 97.x.x.x value and now all is working fine. Wish I had more info, just glad its working.

hi I have the same problem with ntp kernel: pid 71748 (ntpd), uid 0: exited on signal 11 (core dumped) I upgraded from 2.0.3 to 2.1 (amd64) on physical machine with Xeon X3430 @ 2.40GHz 4GB The only solution on my system is go to System > Generel Setup > Click on 'Save' After this the NTPd starts automatically and peers are present under Status > NTP My System log: (this happens every morning after periodic reset) Jan 21 01:00:18 kernel: pid 25498 (ntpd), uid 0: exited on signal 11 (core dumped) Jan 21 01:00:16 check_reload_status: Reloading filter Jan 21 01:00:16 check_reload_status: Starting packages Jan 21 01:00:16 php: rc.newwanip: pfSense package system has detected an ip change x.x.x.179 -> x.x.x.179 … Restarting packages. Jan 21 01:00:14 php: rc.newwanip: Creating rrd update script Jan 21 01:00:14 php: rc.newwanip: Resyncing OpenVPN instances for interface WAN1. Jan 21 01:00:09 php: rc.newwanip: Removing static route for monitor 8.8.4.4 and adding a new route through x.x.x.x Jan 21 01:00:09 php: rc.newwanip: Removing static route for monitor 8.8.8.8 and adding a new route through x.x.x.x

@mattb253: i run pfsense on a pair of dl360 G5s dual quad cores with extra NICs for CARP, i love them also running it on a pair of bl450c g5 blades w/ CARP you should get a 1u 360, i feel like a 380 could still be used for something better  ;) That's the plan… but for now the 380G5 does just fine :P

I am not sure about the NAT situation as of yet since the Entrasys L3 switch is a new device and IOS to me and it also has some awesome NAC software controls. Initially I just want PFSence to function as a firewall between my internal & external networks. With the L3 switch bare to the internet the Chinese IP's have been pounding me relentlessly. Thank goodness I use 24 character passwords!!!

did you download the pfsense .iso w/ the modified kernel for hyper-v? i use this with no problem in 2008 and 2012 hyper-v http://forum.pfsense.org/index.php/topic,56565.msg362435.html#msg362435 i use the one for 2.1 and just give them 3GB for HDD and 1024MB of RAM and I get 100 up and down

There is no reason why it shouldn't work with static IPs. There are many people using just such a setup. Using pfSense as a dhcp server does reduce the possibility of making a configuration error on an individual client. The most common configuration would be to use pfSense as a DHCP server though it's possible to have the LAN as static or to receive it's address from some other DHCP server on the LAN side. For testing you can set the WAN interface to dhcp and set it up behind some other router. You will probably be double NATing and you have to ensure that the WAN and LAN subnets are different but for basic connectivity testing that's fine. Steve

You must have a different subnet on each interface. So if your LAN is still using 192.168.1.1 (the default) you will have to change both OPT subnets to something different. Steve

Check the Status: Interfaces: page for errors on any interface. If you do have a duplex mismatch it will show there. Some of what you are saying is not translating well.  ;) You may get better help in the German subforum. Steve

You do know there also a BIND package now ;) Question for you - how many hosts on your lan.. Are you talking a handful or 1000's What do you expect your dns to do for you other than look up google.com and your hosts?

@opjohnny: Since when is a crossover cable needed for this?  I'm basically doing exactly what I did on the x700e Since always.  ;) To connect two Ethernet clients directly you need to cross the Tx and Rx pairs. This has always been the case for 10/100 Ethernet. When you connect to a switch the connectors are wired appropriately so you can use standard (non crossed) cables but they usually also provide a straight through connector so that two switches can be connected directly. More recently ethernet equipment has had auto-MDIX capability where it can sense which type of cable/connector is in use and configure itself appropriately. All Gigabit Ethernet is auto-MDIX so you may never have come across this problem unless you've been doing it for years or are working with older equipment. The X750e (I assume you typo'd X700e) is all Gigabit NICs so you can connect to it directly. See: http://en.wikipedia.org/wiki/Medium_Dependent_Interface @opjohnny: I'm not sure how to move webGUI access from re1 to re5.  Am I missing something here? Not sure if you fixed this or not. The webgui listens on all ports so the only thing that governs access to it are the firewall rules on that interface. The LAN interface has a default rule allowing access to the webgui on port 80 or 443, dpending if you chose SSL or not. So to get access on re5 you can either add a rule to that interface allowing traffic on port 80 or you could reassign LAN to be re5. If you reassign LAN you'll likely be disconnected until you move the client to re5. Watch for watchdog timeouts on the re interfaces in the logs. Steve

The auto-detection is to help you when you don't know which RJ45 Ethernet socket corresponds to which FreeBSD device name. Start with the cables unplugged, get going on the auto-detect bit, then insert the cable when it tells you. pfSense will see which device just came "online" and suggest to use that for WAN, then LAN… The cable from your ISP device connects to WAN, and the cable to your private network (switch, access point, client computers...) connects to LAN.

Hmm, google tells me your system has two SATA-150 HD controllers, but the CD is still an IDE connection, so it makes sense why a CD could work if the sata subsystem is failing or failed. Try the drive in the other sata connection, otherwise dig through your junk pile for a IDE hard drive.