cannot access bandwidthd from other pc on la

  • George Papadopoulos

    Hello to everybody,

    I have installed bandwidthd on my zentyal( machine. Although it is working just fine when i access it from the same machine on address http://localhost/bandwidthd, i cannot acces this from any other pv on my lan.

    This machine has 3 nis's, one for connecting it to the lan (ip and two for accessing our two routers(ip' for thgese two nic's are and

    I try to access bandwidthd from a amachine in our lan with an ip of

    Can anyone help me an that please?????

    Also another question.

    In the graphs, very often i get these thin-long staright lines of red colour(icmp i think it counts) and they are so high that all other traffic ends up very "low" on the chart(i mean the other colours, counting other protocols traffic can bearly seeing. Is there a way to disable the counting of icmp traffic?Why is this so high?Is it logical?

    Thnk u…

  • George Papadopoulos

    ok i found what was the problem for accessing bandwidthd only from localhost. The zentyal machine had a rule in it's firewall that was resrticting http access…Everything ok now.

    So as far as my other concern, about the huge traffic in icmp making the rest traffic almost invisible in graphs. Can somebody help me hoe to disable it?

  • Alestan

    Alestan - 2011-04-11

    I am going to assume you are storing the information in a postgres database, not using the graph as you go method.  That said, in your /var/www/bandwidthd/htdocs or equivalent there should be a graph.php, in there you'll find a line that reads 'while ($row = pg_fetch_array($result))', add after that, inside the {} a line that reads '$row=0;'.  This will still have the icmp data store in the database, but hide it from the graphs.  If you are not washing it through a database, you'll need to recompile bandwidthd and have it blank the icmp amount as it goes.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks