What's the CPU and RAM utilization on the switch? What's its spec'd packet forward rate?
It sounds to me like this is where the problem is. Sent via BlackBerry from T-Mobile -----Original Message----- From: Adam Piasecki <[email protected]> Sender: [email protected]: Thu, 12 Sep 2013 13:40:33 To: <[email protected]> Reply-To: pfSense support and discussion <[email protected]> Subject: Re: [pfSense] pfSense and Cable Modem Throughput On 9/12/2013 1:25 PM, Matt Smith wrote: > On Sep 12, 2013, at 10:28 AM, Adam Piasecki <[email protected]> > wrote: > >> First I'm almost certain this is a cable modem/provider problem. We have a >> 20mb ethernet circuit that works fine with the same pfSense. >> >> We upgraded to a 100/10mb cable modem, when we put this on the WAN of the >> pfsense, we are getting major packet loss during peak times, and speed test >> sites that won't even load. Non-peak times we get no packet loss, good speed >> tests (50+mb) >> >> The problem I'm having is that when we take the pfSense out and plug a PC >> directly into the cable modem, the speedtests look fine and the dropped >> packets go away. Both during peak times and non-peak. >> >> My thought is the number of packets going over the cable modem with the >> pfSense is a lot greater then just one PC doing a speedtest, and the cable >> modem can't handle it. We have about 100 clients behind the pfSense trying >> to access the internet during peak times. The traffic graphs on pfSense only >> indicate we are doing 5-10mbs download and 1-5 upload, so we are no where >> near maxing out the cable modem bandwidth wise. >> >> I've checked wan ethernet settings 1gig full duplex, no collisions or errors >> on the pfSense side. I don't see any problems in the log, we are not doing >> any traffic shaping. >> > What's the MTU set to on the WAN interface of the pfsense box? The cable > modem may be encapsulating traffic in PPP or doing some other form of > tunneling. You might check if large packets are being dropped somewhere > upstream. You can run ping with a large packet size and the do not fragment > bit set to check this. E.g. 'ping -s 1472 -D <some_internet_host>'. > > -Matt Smith > > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list Okay, i'll try this, it's 1500 the default. _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
