@chrcoluk The number of asterisks shown is no indicator for the real number of password characters.

@bmeeks Thank you sir, for the recommendation. :)

Ooops, missed that! Yeah if you disable pf in the advanced settings that disables NAT and you need outbound NAT for any connection to work from the internal private subnet. Steve

You don't need to have purchased support to open a ticket. I just went thru this myself and they sent me a link for the download in less than 5 min...now if I could just get it working!!!

I edited your post as it was hard to read. I assume he means just in between two switches. Maybe as a layer 2 firewall? Steve

probably there is something wrong with your installation, a factory reset will only reset the config.xml to the default value but it will not correct errors on files. you need to reinstall

there is only one little problem, we can't see the picture

I have CenturyLink fiber, from outside it goes to their ONT that's in my office, then ethernet directly to my PC running pFsense. Centurylink uses PPoe, so I have to enter those credentials in pFsense as well as I needed to VLAN tag the WAN with what Centurylink uses (201). After that no problems. I get 940+ up and down on their gig line.

@dotdash I must admit that you are absolutely right. I am a very impatient person. ;) A couple of minutes ago I finally changed the Payload of the ping (I did it not right at the beginning). Also I inserted a monitoring IP on the interfaces. Now it seems to work but I have absolutely no clue why.

That is a lot of states. Does it make sense that those all exist in your environment?

Probably a difference in the BIOS and how it expects to boot (MBR vs GPT, or BIOS vs UEFI). In most cases you can move a drive around, but at that point it mostly depends on the BIOS settings vs the disk boot layout/partitions.

Cool, thanks for confirming.

Having the same trouble. After upgrading, the second re1 stopped working as soon as bsd loaded. I tried re-installing, but formatting re-installing didn't help because pfsense downloaded the latest version which disabled the second nic, again!. ifup re1 didn't work. I could see that I had a physical link, until bsd loaded and before the firewall software loaded up. The problem appears to be BSD and not pfsense. I can't install packages because 2.4.3 is looking for an upgrade and, frankly, I really don't want suffer the same trouble on a production system. Any help here would be appreciated. Not the way I wanted to spend my saturday afternoon. I ended up installing on a completely different system. Thanks

@Bulldogg said in Bios update: Apr 5 2014 That must be what we were selling as an APU4 right? Which is actually an APU1 with 4GB RAM. You will need to APU1 rom file if so. There is no real reason to update Coreboot on that I'm ware of though. See: https://forum.netgate.com/post/777287 Steve

Hallelujah - its finally working and sorted - follow the OVH links for a server on OVH. I wish i had looked at the articles rather than following a youtube video where i shouldn't have configured pfSense by adding static routes etc. Plus the gateway was set incorrectly. Kom and Awebster - really appreciate your help.

@Gertjan thank you very much sir after I run the fsck -y command the reboot loop stop and it back to its normal operation. I hope i could not see crash report again..

Probably this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215471 Try removing the virtual cd drive. Steve

On install of OS you have options to recover config.xml from previous install before format drive. FYI: now you can auto backup config for free out of box to netgate servers in encrypted way. Or if you have paranoid you can use curl script to download backups on another unix-based machine internally.

I completed the install with pfSense-CE-memstick-2.4.4-RELEASE-p3-amd64.img I put the Allied Telesis 2711FX back in and it goes back into a panic. Seems others have run into no support for this card in freebsd. http://freebsd.1045724.x6.nabble.com/12-STABLE-CURRENT-Dell-PowerEdge-2950-Allied-Telesis-AT-2711FX-SC-100MBit-fibre-NIC-not-recognized-td6328982.html