@jimp hello sir, i have 4 ports NIC card and 2 ports NIC card attached to my box, and i have also 8GB RAM installed on it, installed ome packages on it like pfblocker, squid and so on., and when i look at yesterday morning, i saw Watchdog error in box, then i rebooted it twice, so far i didnt see those error as of now. Thanks jimp

Hard to say. I would simulate it virtually and see. What happens if you install 2.4.4-p3 in a VM and then restore your old 2.2.4 config?

So you have this [image: 1565369485140-setup.png] Not sure which network you have were exactly.. But if you don't want 192.168.2/24 (bottom network) from talking to 192.168.1 you would block it on the lan interface of pfs2 You would have allow rule to talk to pfs2 lan addres for dns, ping for example on the pfs2 lan rules Then you would have a block rule to 192.168.1/24 Then you would have a any rule to allow clients to talk to the internet.. Blocking 192.168.2 on pfs1 lan would be completely pointless and never happen, since pfs2 is directly connected to it. edit: Ah @KOM beat me too it, but he didn't draw a pretty picture like I did ;) heheheh

So I just found out that the problem isn't from PfSense. Everything is working ok. I get IPs and internet connection if i plug an ethernet cable in the computer. The problem is probably at my wireless access point. Thank you for your help.

Okay Thanks ....I will update when I will do it ....

@stephenw10 said in How to get Huawei E3372 working with pfSense?: Nice work.  :) FreeBSD does have an rndis driver now. It's not included in pfSense by default (yet) but you can load the module to test it if required. Steve Hi , I got my e3372 and switch it in stick mode.my problem is I've got a pfsense 2.3.5 on my alix 2d13 board..It doesnt show the NCM interface..How can I load rndis driver on 2.3.5??

Tons of php errors are normal for that upgrade and the release notes warn you to expect those. https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html If you're convinced that it's somehow badly broken, then install fresh and restore your config.xml. No idea about your custom auth script.

Ok, you are passing only TCP/UDP so you will not be able to ping anything from the LIBRAY_NET subnet. Other traffic should pass though as long as it's not in those deny aliases. What's actually failing and how is it failing? Steve

https://docs.netgate.com/pfsense/en/latest/backup/automatically-restore-during-install.html

Mmm, sounds like a bad connection there somewhere. Glad you were able to install though. Steve

That's great. Thanks for the reply.

That sounds like a better setup.

Normally that would happen automatically. But depending on the WAN type, rebooting the modem/CPE would probably help.

You can use something like wget. Navigate to pfsense.org/download select the file, right click save the URL. For the AMD ISO image: wget https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-2.4.4-RELEASE-p3-amd64.iso.gz

@KOM Yes sir. I may do that eventually. Thanks again for your patience with my questions.

@hannes-hutmacher I think will be better if you save your config to xml file and then make fresh install including xml import option. Please see https://docs.netgate.com/pfsense/en/latest/backup/index.html

@Oidar said in System update showing 2.3.4_1 as "up to date": I have to admit I'm ashamed not following up of this earlier... Well, if it works for you there is no obligation. Not upgrading has a small list of advantages. But keep in mind that you can only decide to not to upgrade when you know all the disadvantages. And that list is big. Just to name some of them : Packages are always developed against the latest version (pfSEnse doesn't keep packages for old pfSense versions) so thee can't be upgraded neither. Security issues !? Functionality issues ! Often forgotten : old pfSense are not available anymore. When your system has a hardware failure, you have to reinstall - on another device probably. This forces you to make a major upgrade, and review the entire setup without really knowing what changed. All the time you gained by not upgrading becomes now a triple pay-back. Etc etc ^^

tl;dr check if file format is .iso not .iso.gz I'll reply to this thread even when it's old as it was one of the first which came up when googling "Operating system not found". I spent quite awhile searching for an answer and then I realised that the pfSense ISO file, which I downloaded from official site, is in iso.gz format. I didn't notice this first as I'm working with small laptop screen and the file format was always cut from the screen. You have to extract the .iso.gz file so you have only .iso file. I installed pfSense CE 2.4.4 with Guest OS: Other and Guest OS Version: FreeBSD 11 (64-bit) on ESXi 6.7 U2, though I used VM compatibility ESXi 6.7.

Known by who? Is there a redmine about this? Dozens of systems?