Everything works fine except browsing the web
-
Hi,
I recently installed pfsense 1.0beta on a Celeron 400mhz with 192MB SD-RAM, an 8GB HDD (installed on the HDD). My ISP is 'Bredband2' which goes through our city net (fiber) called Hitnet (typing from Sweden here). We get five (5) IPs. It's a 10/10 line, although we can max it out on approx. 15/15Mbit (yes, 15mbit down and 15mbit up stable, at the same time). That is when we are directly connected to the RJ45 jack in the wall, or through pfsense (i.e. no difference in throughput). However, browsing the web is horribly slow when we're surfing through pfsense.
It doesn't matter if we're downloading/uploading or not, browsing is slow anyway. Even on very local pages (in the same country, like SUNET (Swedish University NETwork)). Again, however, throughput to the server is fine, it's great. Any ideas on what could cause this problem?The computer is as said an Intel Celeron 400mhz, two Netgear FA311 NICs, 64+128MB SD-RAM, an Xbox HDD where pfsense is installed. Oh, and another thing. The pfsense interface is REALLY slow!! It takes 25 seconds to open the system_advanced.php page (I just timed it). Here are some entries in the system log, if that's of any help:
Feb 1 01:31:07 kernel: sis0: Applying short cable fix (reg=e8) Feb 1 01:30:43 dnsmasq[1125]: using nameserver 192.168.254.12#53 Feb 1 01:30:43 dnsmasq[1125]: using nameserver 192.168.254.11#53 Feb 1 01:30:43 dnsmasq[1125]: using nameserver 192.168.254.12#53 Feb 1 01:30:43 dnsmasq[1125]: using nameserver 192.168.254.11#53 Feb 1 01:30:43 dnsmasq[1125]: reading /etc/resolv.conf Feb 1 01:30:38 php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 82.209.173.155. Feb 1 01:30:37 kernel: sis0: Applying short cable fix (reg=e8) Feb 1 01:23:14 last message repeated 5 times Feb 1 01:21:17 last message repeated 2 times Feb 1 01:20:48 kernel: sis0: Applying short cable fix (reg=e8) Feb 1 01:20:47 dnsmasq[1125]: using nameserver 192.168.254.12#53 Feb 1 01:20:47 dnsmasq[1125]: using nameserver 192.168.254.11#53 Feb 1 01:20:47 dnsmasq[1125]: using nameserver 192.168.254.12#53 Feb 1 01:20:47 dnsmasq[1125]: using nameserver 192.168.254.11#53 Feb 1 01:20:47 dnsmasq[1125]: reading /etc/resolv.conf Feb 1 01:20:43 php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 82.209.173.155. Feb 1 01:16:13 kernel: sis0: Applying short cable fix (reg=e8) Feb 1 01:14:36 kernel: sis0: Applying short cable fix (reg=e8) Feb 1 01:10:57 kernel: sis0: Applying short cable fix (reg=e8)The surfing is extremely slow regardless of traffic shaper on/off or with other settings. There's no packages installed.
Any ideas? Thanks!
-
64 megs of ram is under our minimum of 128. It will be slow. Get some more ram.
-
64 megs of ram is under our minimum of 128. It will be slow. Get some more ram.
Am I misinterpreting something in his post cause he did say he got 192 Mb of SDRAM. 64+128.
The computer is as said an Intel Celeron 400mhz, two Netgear FA311 NICs, 64+128MB SD-RAM, an Xbox HDD where pfsense is installed.
In any case I installed pfSense on a 366 Mhz 64 MB ram pc yesteraday and the interface wasn't slow neither was browsing, I upgraded that box today to 192 like his by getting a 128Mb stick to throw in.
Sorry for hijacking this thread, hope you get that problem sorted out.
-
Woops, that he did. For some reason I read that as CF 128 megs and 64 megs of ram.
At any rate, that changes everything. I would double check that you're interfaces are auto-negotiating speeds correctly, duplex, etc.
-
Woops, that he did. For some reason I read that as CF 128 megs and 64 megs of ram.
At any rate, that changes everything. I would double check that you're interfaces are auto-negotiating speeds correctly, duplex, etc.
Duplex and speeds are fine :(. This is very strange indeed. Could it be that the computer is too slow?
-
Doubt it. I push 20 megabit through a 133mhz.
-
Actually now that I read your log output more closely I have an idea:
How long are your cables between the pfSense at WAN and to the LAN switch? You have sis chips and older sis chips had problems with short cables. I have seen problems with these as well in the past (links coming up and going down every few seconds, bad performance, links not coming up at all). Try longer cables (5 or 10m should be fine) and see if that makes a difference. -
One way to tell if this is happening is that you will loose you're ethernet sync light every second or so. Its pretty noticable if there is a problem.
That SIS chipset bug has caused way more damage than good. Really sucks when there are bugs in hardware chips.