You don't see any packages? Can the pfSense box check for updates? If your clients behind the box can get general internet access but the box itself can't it's usually one two problems: 1. You are using policy based routing so the clients get a connection but the box always uses the default gateway and it's misconfigured. 2. You have a limited or bad IPv6 config to the box and it defaults to using that first. See: https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference Steve

Should be true for either one, but there is code that alters the ttys file that may overwrite changes if you're not careful, and on nano I don't think /boot/device.hints is copied from slice to slice.

Duplicate id attributes are violation of html standard. http://www.w3schools.com/tags/att_global_id.asp The id attribute specifies a unique id for an HTML element (the value must be unique within the HTML document). As Phil Davis noted this should be corrected by updating the id values in www/javascript/row_tggle.js to match the field ids of the html.  That would be the proper fix to retain html standards compliance. See attached row_toggle.js file for 3 method examples for handling the unique id values. row_toggle.js.XHTML_Compliance_Firewall_Rules.Patched.txt

I'm in the same situation.  I was wondering if it is best to take a backup of the old PF1 and then restore that to the new PF1 (after modifying the file for the changed interfaces). And then do the same with the old and new PF2 servers. Is there a preferred way to actually swap out the equipment?  I'd love to do this with no downtime and hopefully that should be possible with the CARP failover.  But I'm not sure if it makes any difference to swap the Master or Backup units first. Echoranger, did you successfully make this change?  Do you have any hints to offer? Thanks!

Who do I need to report this to or what do I need to do to get this resolved? Thanks!

Thanks for the tip! The receiver itself is freaking awesome. Picture quality and sound are superb and the DLNA function is also handy :)

@lsense: @blewis: I sure WISH I could use the two USB port but it's an Alix 2D3 board… Somehow, the BIOS only allows booting from CF card... Anyone knows of a workaround...  :( you may build your own image. here is a post about building custom images: https://forum.pfsense.org/index.php?topic=57666.msg307994 Since they sill have not removed the "download" selection menus for the 512MB image from their Download page… I had wrongly thought it was still available somehow... I noticed someone else at the pfSense 2.1.3 Blog was also asking for it...  It would have been great if it was somehow offered on its download mirrors in a separate directory with a text file stating its limitations and inability to use upgrades...

Default config is missing on my home box but /usr/local/etc/rc.d is there and has start up scripts in it. I have some packages installed which might generate it I guess. Steve

You will probably see the same as I got and as such am still stick at 2.0.3 The fresh image booted fine but after I applied the backup and rebooted I got External config loader 1.0 is now starting… Launching the init system... done. Initializing............................. done. Starting device manager (devd)...done. Loading configuration......done. Updating configuration...ERROR: Dangling Comment Warning: rename(/cf/conf/rrd.tgz,/cf/conf/backup): Is a directory in /etc/inc/upgrade_config.inc on line 2660 Migrate RRD database lan-traffic.rrd to new format for IPv6. Migrate RRD database lan-packets.rrd to new format for IPv6. Migrate RRD database ipsec-traffic.rrd to new format for IPv6. Migrate RRD database ipsec-packets.rrd to new format for IPv6. Generating RRD graphs...ERROR: Dangling Comment done. pid 558 (rrdtool), uid 0 inumber 6015 on /var: filesystem full /var: write failed, filesystem is full pid 562 (php), uid 0 inumber 3997 on /var: filesystem full /var: write failed, filesystem is full

@Hobby-Student: @cromero: …I changed $path_to_files in xmlrpc.php and correct '../packages/' but not work. ¿Any ideas? xmlrpc.php, line 45: $path_to_files = './xmlrpc/'; xmlrpc.php, line 124: $path_to_files = './packages/'; This should do the trick. Thanks.Problem solved.

Yes, it's permanent as far as I'm aware. It was done on purpose as a part of some recent work on the tools repository to streamline things and remove some external dependencies. There shouldn't be any functional difference.

Since 2.0 (I think) there hasn't been a choice of single or multiprocessor kernels. Not because there's some auto-detecttion but because the SMP kernel (multi CPU) is now able to run on single core systems so it's used by default. Steve

You could edit the topic title to "SOLVED: …" for better viewing :)

Glad it worked out I still find the recovery tools built into pfsense saving my butt from time to time as well  :D The lesson I've learned (the hard way) is to make backups - often.

Google results where it shows up in dmesg with no related problem.

Not sure what you are suggesting here. My problem is not with blocking it, but with logging it, since it kinda makes my log useless when it is filled with stuff I don't care about. I suppose I could put a specific rule in to block it without logging; but one wonders why the traffic is being generated in the first place, after a minor release. Why do we need to change our rule sets after a minor release? Maybe that's just normal, and I incorrectly assumed otherwise.