ARRGGGGHHH! Been trying to replace my Linksys Router with a PFsense PC.. Has anyone had any luck with getting PFsense to work with an Etisalat Elife connection as the main router. Under the wan interface IPv4 I've setup PPPOE and I've put my Username and Password, I thought that would be enough but it didn't want to connect, so then under IPv6 I chose DHCP6 and told it to retrieve an IP from the ISP… That worked (somewhat) It shows that the connection is up but no activity and when I go on it does not connect (No Internet) it says... I've heard good things about PFsense that why I want it over Untangled (Tried it, but it started to bog down after sometime) .. So PFsense it has to be... PLEASE HELP These are the settings I use on my Linksys that works : Network Type : PPPOE Username Knightjp Password blahblahblah Service Provider : Etisalat Does anyone have any ideas ?

Hmm. It seems new cables did not help :( And buying a new 2-4 port PCIx card costs almost the same as buying a pfSense hardware in the store, and im not sure if its the nic or not. The WAN card is an Intel PCIx, lan uses the onboard, but im testing the speed with fetch directly at the pfSense ssh console.

I had a Thinkpad R52 (R51 maybe) and a 3com 10/100 card.  It was fine for a 1.5Mbit ADSL link. When I moved to the Australian NBN wireless 25/5 speed, I discovered that it couldn't do it.  It was undoubtedly the 3com card, but I wasn't going to trouble shoot ir.  So I threw it all out and moved to a C2D with 2 intel Gigabit NICs and the speed went up to expected.

i Tuning "kern.ipc.nmbclusters="1000000"" After 15 days of operation,still crash… [zone: mbuf] kern.ipc.nmbufs limit reached [zone: mbuf] kern.ipc.nmbufs limit reached [zone: mbuf] kern.ipc.nmbufs limit reached :'(

I appreciate your help with this. The issue eventually went away when I did a complete reflash of the firmware. Option 8 is now working correctly.

@cmb: @Music: type of Wan you mean what network card is used on the router?  i think it is a realtek. No I meant whether it's PPPoE, DHCP, static IP? Mostly curious if it was PPPoE, did the PPPoE stay up. But you answered that indirectly re: the modem. The type of NIC used won't impact anything like that. The web interface being really slow is probably just a function of DNS being unreachable and some part of it trying to resolve DNS and awaiting timeouts. @Music: Edit: i have a ISP router i cant disable the firewall from and cant put in bridemode and port forwards etc is very very limited. ( experiabox V10) and i put in that router a DMZ to my pfsense box. My first guess was the test was doing something that crashed your modem and something that happened in the process of the reboot of the device plugged into it fixed the problem. well my internet it self is pppoe its KPN-Fiber (dutch provider).  but pfsense isnt directly connected to it. im just using the DHcp server. i get a IP from the ISP modem and then have the dhcp on pfsense enabled. The modem didnt crash internet was still working. i got my TV(IPtv) directly connected to the modem and that just continued so only pfsense itself was without internet. When i log in via SSH the wan IP is just gone. When i try to assign a wan IP again via dhcp it does not give any IP untill i reset the PFsense box. I run the own DNS server in PFsense i dont use the ISP DNS nor anything like google etc.

Thanks for your response.  I killed the proc, made sure all packages are up to date, and it's been fine for several hours now.  I will be scheduling the upgrade to 2.2.6 in the next 14 days - this sits in front of a customer portal, so we have to give them at least 14 days before we interrupt service :)  maybe I'll get the chance to build a redundant unit out of this…..

You know it's getting really bad when you spend sleepless nights desperately trying to solve a tough firewall issue, only to eventually find the most useful information in all of the internet ends up being a solution to your exact problem which you yourself wrote four years ago. https://forum.pfsense.org/index.php?topic=48891.0 The PXE boot still is not working, but the proxy appears to be passing traffic now. I will write this up as a bug/feature this time since I never got any feedback the last time, and then I forgot about it.

Oh yeah this has me drooling!!!  F__K that would be sweet ;) I may have to do this – heheeheh!!! If you want the 3.1.1 version, I compile it all the time for windows both 32 and 64 bit..  Since nobody else seem to be doing it that I could find.. You can grab it here http://files.budman.pw/

Yes. Only DHCP server. Everything else works just fine. I should say that I am running 2.3 so maybe there is a bug?

Dear Jimo and Johnpoz, Thank you for the answers! I totally forgot the caching mechanism. It's clear. Have a nice day!

https://doc.pfsense.org/index.php/Main_Page There are also about a zillion guides, tutorials and videos online about pfSense.

Seems like in 2.2.6 the problem gets worse.

/var/log contains all of the available logs, including system and ipsec.  I'm just guessing with the ipsec log, since it may only have connection-related details and not anything about the plumbing.