I have bridged the interfaces and it is running (with squid as well at the moment) not sure if the VPN will work but will give it a go

so this actually seems to be a nano related upgraded; i had similar behavior when upgrading another non-alix box running nano. in any case, i just decided to wipe and start fresh with 2.1. all is well.

^^agreed get a real nic eg. intel pro server nic,  imho easier to setup and  in the long run easier to maintain and troubleshoot

pfSense uses that hostname and domain for the system itself. The domain gets used in various places like DHCP and DNS as the default domain. The FQDN of the firewall is used to validate that the referer matches when using a hostname, and also for DNS rebinding checks. The hostname is also used in various aspects of logging. There are probably dozens of other little places it gets used in various daemons or config files or graphs, but it's best to always have it set right.

There is no supported upgrade path from embedded 1.2.x to anything. You have to rewrite the CF. Even to go from 1.2.2 to 1.2.3 you had to rewrite the CF. 1.2.3 and later use NanoBSD which does support upgrades. You can take your older configuration and restore that to a newer 2.0.x or 2.1 in most if not all cases.

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