Need help getting pfsense to work properly
-
As i mentioned before no bridge used. I have an username and a password; and the connection is pppoE.
-
The hardware:
Mobo: MSI using G31 chipset (https://www.msi.com/Motherboard/G31TMP21#hero-overview)
CPU: E8500 (https://ark.intel.com/products/33911/Intel-Core2-Duo-Processor-E8500-6M-Cache-3_16-GHz-1333-MHz-FSB)
RAM: 1*2gb 800mhz Kingston
HDD: 80gb IDE hdd 7.2k rpm -
You should bridge it. what is the lan IP you given to pfsense ?
-
192.168.1.1/24
-
and whats the ip you are getting from your modem to pfsense wan?
-
I can't tell you that, but starts with 85 or 89 if i remember correctly.
-
if your modem is not bridged you should be getting a internal IP like 192.168.x.x on wan so if you are getting external ip your modem is bridged.
-
hmmm… man learns every day, thanks for the info. is that good or bad news?
-
What should i do now?
-
try turning off the modem and pfsense for a while maybe you got multiple IPs queued from your ISP or try Intel nics
-
The modem can't be turned off because it is outside extremely high and gets power from the street. I tryed again today and same behaviour. Any tips left? I tryed disabling some driver features then enabling them they had 0 impact on performance… CPU usage is still between 1 and 3 percentage.
-
At this point im giving up and calling pfsense is still in beta access. Barely works and full with bugs which can't be fixed…
It is quite sad that an 3usd cheap router outperforms pfsense... -
Today i gave a try to 2.4 but seems same… Download speeds locked at 2mb/s and whatever i do i can't exceed 3% cpu usage...
I started using steam for testing speeds because speedtest.net started giving me download test error messages.
If anyone could help me, i would greatly appreciate it... -
Just got a bootloop when i tryed to reboot the pfsense… So back to 2.3 but this time i'll try to use the 32bit version.
-
Okay, same behaviour with 32bit version… download speeds locked at 2mb/s and cpu usage locked at 3%...
I think the only thing left is to sell the hardware... -
Don't know why YOU are locked on the fact that the CPU only uses 3 %.
Look at mine : https://www.test-domaine.fr/munin/brit-hotel-fumel.net/pfsense.brit-hotel-fumel.net/processes.html - the green part (approx. 3 %) is the same and everything works fine - ISP gives me about 25 Mbit, and that comes through.Don't tell us you have problems, tell about the problem, describe it. Copy past settings, screen, your findings.
Don't tell us that you can't find your IP "Internet", that's like saying that you driving a car, but are not aware that some where i the same car an engin must be running …
Check out other forum threads about how to question and ask so feedback can be given that can help you.
Btw : pfSense 2.3.4 is not buggy, very stable and work great for years now for me
-
Dude it has something to do with your Hardware or setup, look at my results pfsense 2.3.4
-
I tried different NICs, even Intel ones and always the same results: download speed locked at 2mb/s and upload speed is random but between 1.5 and 3.5mb/s.
While on my 3usd cheap router i get 10.5mb/s download and 5mb/s upload easyly…
No idea what the problem is... -
Is that possible that i have to change some buffer sizes or something? Because RAM usage never exceed 7% and CPU usage is hardlocked at 3%.
The HDD is 80Gb if i remember correctly…
Maybe i should install windows and test it there too... hmm... i remember using this PC on windows 8.1 64bit and i got correct speeds... so definitelly pfsense issue... -
@speter2:
I tried different NICs, even Intel ones and always the same results: download speed locked at 2mb/s and upload speed is random but between 1.5 and 3.5mb/s.
While on my 3usd cheap router i get 10.5mb/s download and 5mb/s upload easyly…
No idea what the problem is..." I have a cheap 2usd router laying around and using that i get 75mbps download speed while on pfsense it is hardlocked at 20mbp"
Am I missing something? speeds have changed since your first post.
You might have some driveR problems, just cos windows plays nice does not mean BSD will, try a different machine
