Pfsense Struggling big time.

x2rl

Not likely. It's not like it writes every packet to disk. Check your System log for CAM Status errors if you suspect disk problems.

Think about it. If you run an app that sucks up all your bandwidth, then everyone else on your network is going to have a bad day.

Yea I do get that, its just odd that if I remove pfsense and just use a router I don't have the problems.

KOM

if I remove pfsense and just use a router I don't have the problems.

This information would have been nice to know much earlier in this thread. While I can't speak for your other router, you need to find the source of your issue. You said your link is 350/100? When you are having these issues, how saturated is your pipe? Is it mainly download traffic or are you mainly seeding? How full is your state table? Anything in your System log? What happens if you turn off Snort and pfBlockerNG which are two notoriously heavy packages?

x2rl

@KOM:

if I remove pfsense and just use a router I don't have the problems.

This information would have been nice to know much earlier in this thread. While I can't speak for your other router, you need to find the source of your issue. You said your link is 350/100? When you are having these issues, how saturated is your pipe? Is it mainly download traffic or are you mainly seeding? How full is your state table? Anything in your System log? What happens if you turn off Snort and pfBlockerNG which are two notoriously heavy packages?

Sorry yea I should of said that at the start.
The main leeching seeding is done on my other server (which is not on this network)

saturated pipe? sorry no idea what that means.
State table? no clue ill see if I can find something on pfsense for that ( from what I can see is there is lots if its (Diagnostics-States-States)
snort and pfblocker off deleted clean isntall still do the same.
I can;t seem to find where the logs are ill look

ankitagupta

I was about to create a thread but luckily found this thread.
I am facing this same issue. Someone help me please.

KOM

saturated pipe?

That's another way of saying you're using all of your bandwidth.

The main leeching seeding is done on my other server (which is not on this network)

Is it using pfSense as its gateway?

State table? no clue ill see if I can find something on pfsense

Look on the dashboard for the System Information widget which has a section titled State table size.

I can;t seem to find where the logs are ill look

Status - System logs.

SammyWoo

I dunno why you are looking north when the problem is south.

Bandwidth Saturation is common in every installation, not unique to pFsense, and on your first post u disclose starting this deluge thing on the media PC does it, so THAT is your problem.

When an App takes up all available bandwidth, the network is not smart enough, by default, to say, hold it, I got other clients to service so u can't have the whole "pipe." Fortunately you have the power to change this. Pfsense solution is: TRAFFIC SHAPER.

KOM

Bandwidth Saturation is common in every installation, not unique to pFsense

He said that the problem goes away if he swaps out pfSense for a consumer-grade router.

x2rl

That's another way of saying you're using all of your bandwidth.

Not really thought I would says its alot of connections if that means anything

Is it using pfSense as its gateway?

No its not even in my house.

Look on the dashboard for the System Information widget which has a section titled State table size.

1% (3423/401000) with deluge off
5% (21722/401000) with it on

Status - System logs.

I see this every few lines

Apr 5 10:22:09 check_reload_status updating dyndns WAN_DHCP
Apr 5 10:22:09 check_reload_status Restarting ipsec tunnels
Apr 5 10:22:09 check_reload_status Restarting OpenVPN tunnels/interfaces
Apr 5 10:22:09 check_reload_status Reloading filter
Apr 5 10:25:24 rc.gateway_alarm 20213 >>> Gateway alarm: WAN_DHCP (Addr:81.107.216.1 Alarm:1 RTT:87812ms RTTsd:49587ms Loss:21%)

He said that the problem goes away if he swaps out pfSense for a consumer-grade router.

Well its better other computers don't drop but do run slow

Harvy66

It's possible the consumer grade router is so limited that it is unable to saturate the internet connection or a limited number of states.

I actually had the inverse issue. I went from a 60/3 cable connection to a 50/50 dedicated fiber connection and when downloading torrents, I found that my Netgear suddenly started to puke. I had to limit the number of connections my torrent client could make to keep it from dying. But prior to fiber, I could use torrent just fine.

x2rl

@Harvy66:

It's possible the consumer grade router is so limited that it is unable to saturate the internet connection or a limited number of states.

I actually had the inverse issue. I went from a 60/3 cable connection to a 50/50 dedicated fiber connection and when downloading torrents, I found that my Netgear suddenly started to puke. I had to limit the number of connections my torrent client could make to keep it from dying. But prior to fiber, I could use torrent just fine.

Seems to be the other way around for me pal.

KOM

Apr 5 10:25:24 rc.gateway_alarm 20213 >>> Gateway alarm: WAN_DHCP (Addr:81.107.216.1 Alarm:1 RTT:87812ms RTTsd:49587ms Loss:21%)

This isn't good. pfSense gateway quality detection thinks your WAN is really flaky. What does it say under Status - Gateways?

x2rl

@KOM:

Apr 5 10:25:24 rc.gateway_alarm 20213 >>> Gateway alarm: WAN_DHCP (Addr:81.107.216.1 Alarm:1 RTT:87812ms RTTsd:49587ms Loss:21%)

This isn't good. pfSense gateway quality detection thinks your WAN is really flaky. What does it say under Status - Gateways?

WAN_DHCP 81.107* 81.107* 12.19ms 4.111ms 0.0% Online Interface WAN_DHCP Gateway
WAN_DHCP6 fe80::201:5cff:fe80:1447 Pending Pending Pending Pending Interface WAN_DHCP6 Gateway
with deluge off

On

WAN_DHCP 81.107.* 81.107* 598.681ms 216.247ms 38% Offline Interface WAN_DHCP Gateway
WAN_DHCP6 fe80::201:5cff:fe80:1447 Pending Pending Pending Pending Interface WAN_DHCP6 Gateway

KOM

Try going to System - Routing - Gateways. Edit your gateway and check the Disable Gateway Monitoring checkbox and try again. It seems that your torrent app is filling your pipe to the point that the upstream monitor thinks your link is dying.

x2rl

@KOM:

Try going to System - Routing - Gateways. Edit your gateway and check the Disable Gateway Monitoring checkbox and try again. It seems that your torrent app is filling your pipe to the point that the upstream monitor thinks your link is dying.

Seems to be the same Kom. Thanks again for the help.

Jailer

Hmmm, crapping out under heavy traffic. What hardware is pfsense installed on?

I'm betting there's a Realtek NIC in there.

x2rl

@Jailer:

Hmmm, crapping out under heavy traffic. What hardware is pfsense installed on?

I'm betting there's a Realtek NIC in there.

Smoothwall SWG700 I think its called

SammyWoo

@KOM:

This isn't good. pfSense gateway quality detection thinks your WAN is really flaky. What does it say under Status - Gateways?

Flaky or stuffed to the gill.

KOM

While we may never get to the bottom of your actual issue, you would still be best served by some traffic shaping so that your torrent traffic doesn't hog all your bandwidth.

x2rl

@KOM:

While we may never get to the bottom of your actual issue, you would still be best served by some traffic shaping so that your torrent traffic doesn't hog all your bandwidth.

Thanks is there some kind of guide on how you do this which you know of KOM

KOM

Traffic shaping is probably THE hardest element of pfSense to figure out. Try:

https://www.youtube.com/watch?v=it_5xvC28vs

https://www.youtube.com/watch?v=rF46PNid1Mo