Slow internet!! HELP.
-
I suspect its unlikely that an interface not capable of operating at 1000Mbps would negotiate to operate at 1000Mbps. Regardless, there is almost certainly a problem on your WAN link with that error count. Do you have the correct cable for the link between ONT and WAN interface of pfSense? Should it be crossover or straight through?
-
Have you tried a switch inline between WAN and ONT?
-
@Gob:
Have you tried a switch inline between WAN and ONT?
Assuming you mean directly accessing the ONT or changing the ethernet cable… no. Seeing as it was working 100% fine 3 days ago with untangle. I'm not trying to turn this into a pfsense vs untangle thread, since I like PFSense better then untangle by a mile - it's just I'm getting tired of people assuming the issue is hardware related when I've already said multiple times it worked fine before.
wallabybob:
The network card on pfsense is 100Mbps. The ONT can reach 1000Mbps speeds. PFSense was reporting it was linked at 1000Mbps. Obviously it can't reach those speeds, so its just bad negotiation.
Like I said above, same configuration that I was using for untangle 3 days ago that worked.
Is this a driver problem?.
-
"I had this issue with untangle, and I found limiting both WAN and LAN to 50Mbps total transfer speed (cant remember if it was half duplex or full duplex, I believe half) fixed connection issue."
Your first post tells me you have a hardware problem.
Roy…
-
Seeing as it was working 100% fine 3 days ago with untangle. I'm not trying to turn this into a pfsense vs untangle thread, since I like PFSense better then untangle by a mile - it's just I'm getting tired of people assuming the issue is hardware related when I've already said multiple times it worked fine before.
At least two people have pointed out their pfSense system gets much better bandwidth than you are able to report. So what's different about your configuration that causes you to get much lower bandwidth? pfSense software is common so perhaps its a device driver that you are using that others aren't using. Perhaps its "hardware". Perhaps you can suggest something else.
About working 100% fine 3 days ago with untangle: did you ever check the "wan" error counts in untangle? If not, how can you be sure you didn't just find a mode that worked "well enough" rather than one that worked 100%?
If you are not prepared to allow the possibility that there might be "hardware" error in a configuration that apparently should work correctly in full duplex mode but requires half duplex mode to give "good enough" performance then I think I'm probably wasting my time continuing the conversation. I'm not saying it must be a hardware problem, but it does look like one to me.
Is this a driver problem?.
Maybe. What are your interfaces (e.g. WAN is xl0, LAN is de0)? (This information can be obtained from the WEB GUI: Interfaces -> Assign or Status -> Interfaces or provide the output of the shell command ifconfig -a)
You haven't yet answered my question about the cable to the ONT: are you sure you have the correct cable (including that the cable is not too long etc)?
-
It's a 25 foot ethernet cable, CAT5-E.
LAN sis0 WAN dc0
If it is a hardware error (and I doubt this because I've tried another network card), then I won't mind if I can get it to work "well enough".
-
Could you try calling your ISP and asking them to put the ONT-downlink port you are using to 100MBit FDX static instead of autonegotiate perhaps ?
-
Please try a new network cable, just to rule it out.
And route it differently than you have now.
-
Why is everyone here so useless?. I might just try endian.
I wonder which part of "WORKED 100% FINE THREE DAYS AGO ON ANOTHER ROUTER SOFTWARE" people failed to understand. This is getting me nowhere.
-
thanks for sharing your supreme knowledge with us menial people.
-
darksoul - it's simple - you've already highlighted that the original platform had problems and since then you've switched OS (and hence drivers etc). According to your own posts it hasn't worked "100% fine".
So, if you're unwilling to accept that you may be wrong and unwilling to work with us to help find the problem I don't think anybody's going to miss your attitude ::)
If on the other hand you're willing to work with us and accept that we need to rule out hardware issues, feel free to stay and be constructive.
-
just out of curiosity, you do not have squid installed. Now I want to do ping the dns server of your internet when downloading and published when the latency.
-
"Why is everyone here so useless?"
We now know you have an unknown technical problem and at least one known person problem. A good start to repair the later would be to apologize to all the good folks that took the time to try to help you fix your technical problems.
As far as your Internet speed problems go, you might want to spend less time defending your take on the problem and more time on trying to understand the advise other folks are offering you.
It's OK to get frustrated when you're trying to resolve a stubborn problem but it's not OK to take out that frustration on the good folks that are volunteering to help.
Grow Up, Man Up and Wise Up.
Roy…
-
As usual, very familiar …. good debuggers look, touch, move, change and swap everything to found where the problem is. Cables, plugs, sockets, hardware, software ....
And hey ... everyone knows that network errors are also caused by cables or connections ... worth giving it a try and let everyone try to help you the way they knows?
One more cause: a wrong IP would also give such error statistics ;)
I have a problem. It's not a unknown problem - I had this issue with untangle, and I found limiting both WAN and LAN to 50Mbps total transfer speed (cant remember if it was half duplex or full duplex, I believe half) fixed connection issue.
Ohhh 50mbps half duplex? sounds to me hardware or cable … are you sure you are not using a cat5?
if you are using a cat5e ... did you tried to use a straight-pair and a crossover? ... sorry question have been asked few times and we had no answer on this, yet ...The problem is, I tried that with pfsense. And while I was definitely able to limit WAN, LAN never showed up as half-duplex. When I attempted to do this, it just removed the half-duplex and full-duplex from the LAN details and slapped on 100Mbps with nothing else.
Auto-negotiation on the LAN side its working properly and this proves that issues are on the WAN side.
The question here is only one. Why untagle want WAN and LAN speed negotiation to be the same? Two different cards for two different networks … wooohhhh lol
I see your point, you refuse to understand its a hardware issue because you got it working with untangle and now you having issues with pfsense .... but you are missing the whole point here.
You have hadrware issues!And by the way with a cat5e cable forget about 1000mbps since 100mpbs its all you going to get.
Why is everyone here so useless?. I might just try endian.
Haven't noticed this before … good on ya
-
one correction: A good CAT5E cable will run just fine at 1,000 mbps.
Roy…
-
::)
Good luck on your next venture.
Like we said… Hardware problem
http://forums.untangle.com/networking/15423-slow-download-upload.html
-
Sorry to bump in on this thread, but where do you find the WAN and LAN errors? Are they viewable in the GUI?
I am having trouble with slow internet browsing at times and wanted to see if anything looked a miss there.
-
http://192.168.1.1/status_interfaces.php
Roy…
-
+1 for chpalmer
-
Thanks - sorry so obvious!
I guess 0/0 and 0/0 with an uptime of 2 days, 18:31 is a good thing :D
