In need of help to solve a bandwidth issue
-
Three of your top 4 lines refer to 65.54.93.42 (cds39.mia9.msecn.net.). I don't know what that is - does it make sense to you?
-
No.. not at all.. Currently it is chewing up 20mb.. and that IP is no longer there in the pftop output.
-
Also, i should add that this just became more confusing.. i thought it would be some clients doing alot of ptp or torrenting or something, but i just completely turned all the clients off for 10 minutes and the bandwidth never changes, was still max'd at 20mb with no one using the box..
-
Try to change admin passwords and disable outbound ssh connection for testing
-
Ok, just changed passwords and disabled SSH.. will report back in a little while
-
Ok, so its currently back up stuck at 20mb usage.. this just makes no sense.. the LAN traffic is only 2mb usage.. Can i have been hacked or something? Is it even possible that squid or something else is using up all the bandwidth?
-
Ok, so its currently back up stuck at 20mb usage.. this just makes no sense.. the LAN traffic is only 2mb usage.. Can i have been hacked or something? Is it even possible that squid or something else is using up all the bandwidth?
Did you try and disabling squid and see if that cuts the bandwidth down?
-
Thats the only thing i havent already done.. as i am a little worried if this will delete my cache or something? Cache is something that i really need running as i havent got a great deal of bandwidth.. If its ok to disable it and then re-enable it then i'll give it shot
-
It has been a long time since I used squid. I don't think I remember if it clears it or not.
-
Just quickly.. what do you mean by 'disable' squid? I dont see a disable check bo like some other packages have.. do you mean just stop int binding to the interface? Mine currently binds to my LAN and OPT1 interface, and not my WAN interface..
-
Sorry, just stopping it will disable it until reboot or until you start it again.
-
Any idea how to STOP it? i have just done it a few times via the dashboard 'Services" widget, but it keeps just turning itself back on..
-
Stop it and then remove the package. That will certainly keep it stopped ;)
-
Um.. removing it is definately what i want to do.. i need squid running.. i am just trying to stop it so i can see if it is the problem, then i'll have to work out how to fix it..
As far as i know, squid is the only way i can cache alot of my clients usage and save bandwidth, that i desperately need to.. cause the costs of Bandwidth here in Brazil is really high.. need all the help i can get to save on bandwidth
-
Um.. removing it is definately not what i want to do.. i need squid running.. i am just trying to stop it so i can see if it is the problem, then i'll have to work out how to fix it..
As far as i know, squid is the only way i can cache alot of my clients usage and save bandwidth, that i desperately need to.. cause the costs of Bandwidth here in Brazil is really high.. need all the help i can get to save on bandwidth
-
There should be a disable or enable check box in the config. check or uncheck it depending, save, and then stop the service. Once BW has seen to gone down, or stay the same, then reverse the steps.
-
Have looked over and over and there isnt a disable or anything like that in the Proxy Server settings..
I have stopped the service with the widget on the dashboard, and straight away the WAN usage goes back down to match the LAN.. so i now know that it is somehow Squid causing the issue.. no idea why though. But, after a few seconds the bandwidth goes back up as the service restarts itself..
-
Try the Allow users on interface checkbox on the Proxy Server.
If you have squidguard, try to disable it also.
-
No squidguard.
Wont the Allow users on interface stop the users from being able to access the web? And squid would still be running.. so probably still updating or doing whatever it is that is eating bandwidth
-
AFAIK, the Allow users on interface (if LAN is the selected interface) will only bypass the proxy if uncheck.
If this field is checked, the users connected to the interface selected in the 'Proxy interface' field will be allowed to use the proxy, i.e., there will be no need to add the interface's subnet to the list of allowed subnets. This is just a shortcut.
