Re: [bwm-tools-tech] Not shaping anymore (Where to troubleshoot)

[Larry S. <le...@ec...>]

On Thursday 21 June 2007 16:33, pra...@gm... wrote:
> Can anyone consult for us in getting the bw tool build and work pls?
> Rates open.
> Thanks,
> Prab Balasubramanian
> Sent via BlackBerry from Cingular Wireless
>
> -----Original Message-----
> From: "Andrew Niemantsverdriet" <and...@gm...>
>
> Date: Thu, 21 Jun 2007 15:31:31
> To:bwm...@li...
> Subject: [bwm-tools-tech] Not shaping anymore (Where to troubleshoot)
>
>
> I had bwm-tools running in production for about 5 months. I had a
> harddrive go bad in the box last night. So lucky for me I had backups.
> I run my server in bridge mode so traffic continued to to flow so I
> don't think I made any stupid mistakes restoreing the backup because I
> was in a rush. Here is what I have found so far no shaping is occuring
> for any IP's listed, bwm-monitor will not work over ssh and traffic is
> for sure flowing through the bridge again.
>
> The box is bridged and has an IP of 192.168.100.10. The clients all
> connect using the 10.1.1.x subnet. The client "Office" should be
> limited to about 256k both directions and total bandwidth usage should
>  be about 256k.
>
> What is wrong? What won't bwm_monitor work? bwm_montior will just sit
> there when I run it no user interface appears, the only way to get
> back to the console is to 'ctrl c' which causes a segmentation fault.
> Where do I start to troubleshoot? It appears that everything starts
> fine. I did upgrade from Fedora Core 4 to CentOS 4.3 on the new drive
> but other than that everything should be identical.
>
> My once working config is pasted below (minus some unimportant data):
> <firewall>
>  <global>
>   <modules>
>    <load name="ip_queue"/>
>   </modules>
>
> #Begin Access Classes
> <class name="AllowSSH">
>   <address dst="192.168.100.10" proto="tcp" dst-port="22"/>
> </class>
> <class name="AllowHTTP">
>   <address dst="192.168.100.10" proto="tcp" dst-port="80"/>
> </class>
>
> #Begin Traffic Classes
> <class name="Office_out">
>   <address src="10.1.1.253"/>
> </class>
> <class name="Office_in">
>   <address src="! 10.1.1.253" dst="10.1.1.253"/>
> </class>
> </global>
>
> #Access Control Lists
> <acl>
>   <table name="filter">
>    <chain name="INPUT" default="DROP">
>     <rule name="allowed_traffic" target="ACCEPT">
>      AllowSSH
>      AllowHTTP
>     </rule>
>    </chain>
>    <chain name="FORWARD" default="ACCEPT">
>     <rule name="controlled_traf" target="bwmd">
>      Office_in
>      Office_out
>     </rule>
>     <rule name="disabled_traf" target="DROP">
>     </rule>
>    </chain>
>    <chain name="OUTPUT" default="ACCEPT">
>    </chain>
>   </table>
> </acl>
>
> #Traffic Flows
> <traffic>
>   <flow name="traffic_total" max-rate="7680000" queue-len="5"
> queue-size="4500" report-timeout="60">
>  <flow name="flow_Office_total" max-rate="32000" report-timeout="60">
>    <flow name="flow_Office_out" max-rate="32000" report-timeout="60"
> nfmark="101">
>      Office_out;
>    </flow>
>    <flow name="flow_Office_in" max-rate="32000" report-timeout="60"
> nfmark="102">
>      Office_in;
>    </flow>
>  </flow>
>
>   </flow>
> </traffic>
> </firewall>
>

While definitely not qualified to speak for BWM-Tools, I highly suspect (from 
doing similar myself) that you are going to have to actually compile the 
bwm_monitor, bwmd, etc on the new OS (Centos) versus just copying it over 
from backups (if this is actually what you did).

If you compiled bwm from source on the Centos box, and simply copied your 
configs in, then something did not go right in the compile, go back and do it 
again and pay particular attention to the configure logs and the output of 
the make, make install.

-- 
Larry Smith
SysAd ECSIS.NET
sy...@ec...