Thank you! Accidentally had Stable (2.4) set as the target while upgrading from an older 2.3.X release. Had to run the pkg-static clean / install commands to get things back on track from a partial 2.3.2 -> 2.4.X upgrade attempt in console. I rebooted after switching the update branch to "Security/Errata" to get to latest 2.3.X, and ran the update in the console and was able to get to the latest 2.3.5.  Then switched back to Stable update branch, before finally upgrading to the latest 2.4. A reboot between setting the update branch each time seemed to help, but maybe wasn't needed.

@Nhiel23: After configuration my computer connected to pfsense can access to Internet but the problem is I can't ping yahoo or even my LAN-gateway. The first four words indicate a potential problem factor. Every PC on planet earth has a DHCP client activated by default. The 99 % other devices also. So it will obtain an IP/DNS/Gateway as soon as plug in the Ethernet cable. Why did you have to configure your computer ? What is your LAN-Gateway ? 192.168.3.1 ? If not, detail your config - show us an image - do not hide details. Show also the result of a ipconfig /all from your PC. pfSense : Interfaces => WAN, Block private networks and loopback addresses must not be checked (192.168.1.0/24 is a reserved for private network)

Thanks Gertjan, after applying the patch error seams to be gone.

@yarick123: Hi, I had also some troubles during upgrading i386 NanoBSD from 2.3.4_1 to 2.3.5 . One of them was missing "Legacy stable version (Security/Errata only 2.3.x)" branch. Solution: I switched the Firmware Branch to "Development Snapshot (Experimental 2.3.x)", saved the changes and checked for upgrades. After this procedure I could select "Legacy stable version (Security/Errata only 2.3.x)" branch. After saving the configuration, new updates were recognised. Regards yarick123 P.S. Yes, I got 2.3.5 and 2.3.5_1 on my i386 NanoBSD.

@Gertjan: @Waqar.UK: I understand, the Asus is in the front line. Also, why I cannot connect my pfsense box to my wan port instead of lan port? Where did you hook up this Asus box (the AP) ? I understood : on the pfSense LAN - as one of the devices on your LAN - like PC's, printers, etc. It's an AP, thus that is where it belongs. On the pfSense WAN side you have tour "ISP" box (also a router), that's it. pfsense LAN port to Asus.

@jarmentrout@kidsrsu.org: it booted, now on 2.3.6-Development There is nothing newer then that version - if you use the 32 bit version.

Undoubtedly it's a hardware problem of some sort. It could be having trouble reading the disc, there could be a memory or other problem causing a corrupted read, or corrupted data in memory, or any number of other issues. That hardware is probably far too old to be used effectively.

You don't do anything with the modem apart from disconnecting your home hub and connect the modem in its place. Then change the pfSense WAN connection to PPPoE, but I think you'll need a BT ID & password. https://forum.pfsense.org/index.php?topic=136545.msg747008#msg747008 << maybe look at this for the userid & password.

^^that. You might want to exchange the Realtek for an Intel NIC and speed should go up. At least if your CPU can still cope with it.

Thanks man, this is exactly what I was looking for. This entire forum is great. Thanks all

But the wrt3200acm is capable of switch and wifi at the same time it can be done but I am new on this Cain of things

i have 2 netgate xg-2758 linked together in high availability sync. Both were on 2.3.4, tried upgrading straight to 2.4.2.  Errored out, was then able to upgrade backup Xg-2758 from 2.3.4 to 2.3.5 then to 2.4.2.  So I'm confident the upgrade will work but not at all familiar with command line options. Can still putty into primary xg-2758 and everything is still working.  I need to be either to change the update branch to legacy stable version so I can then run the update command or download 2.3.5 and install from shell. Thanks.

And you upgraded from what version of pfsense.. If really old maybe you were not using dnssec, and whatever it is your trying to go to doesn't pass dnssec so you get no answer.. Really going to need more to go on vs kodi/flawless hosting.. Addon to what?  A browser, your roku?  Plex server - some other sort of media stick.. Impossible to even help you figure what is wrong if don't know what your even using.. Here let me give you an example.. My car is broken, after I filled up the washer fluid..  What is wrong with it - it use to be not broken, but now its broken.

Thanks Per Hansson! Now I can read most of the pfsense startup messages, do a useful pftop, display the firewall log, etc. I know some active members of the forum have a different opinion about implementing the console interface, but my experience has always been, better safe than sorry.  

Figured some kind of typo ;) hehehe

Hi all, I followed the suggested approach (removing packages on old system, create config backup on old system, restore config backup on new system, reinstall packages on new system). All worked fine but I overlooked one thing… Thanks to a prompt reply fro Netgate support I managed to resolve this. The issue was that the network card configuration (the network interface naming in the config backup was not compatible with the new system) and the device got stuck in the console waiting for network card assignment. Connecting through a serial connection with the console I could select interfaces and proceed. Thanks for the support! regards.

Thank you very much. What remains is to see what are the recommended NIC cards for the software to run omptimally. To make the story short, I just plan to use its QoS feature. And read a little more about LAN/WLAN/VLAN or whatever they call it. Sorry if my english isn't that good. It's just my 4th language (learning order not preference order lol)