StarOS is NATting at each backbone location - that is why I wanted to put this collection in place between the core router and the NAT router so it can see the customer data in its native (pre-NATted) state.
Matt Larsen vistabeam.com On 3/30/2010 1:34 PM, Josh Luthman wrote: > Scott, > > 4) StarOS routers performing NAT at each backbone location > > It's StarOS NATing the customers off of the backbone. > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > “Success is not final, failure is not fatal: it is the courage to > continue that counts.” > --- Winston Churchill > > > > On Tue, Mar 30, 2010 at 3:32 PM, Scott Reed<scottr...@onlyinternet.net> > wrote: > >> If you can run IPTrack (see some of Marlon's previous posts) you have >> have the MTs report by IP address back to the server. >> I have done this on my network, though it is not running right now. I >> would be glad to help if you opt to go this way. >> >> Matt Larsen - Lists wrote: >> >>> Hello list, >>> >>> I am looking for a solution that will keep track of the monthly >>> bandwidth consumption for all of my broadband customers and am having a >>> hard time coming up with a good solution. >>> >>> Our goal is to collect the traffic flows every 15 minutes and generate >>> three things: >>> >>> 1) Internal reports showing bandwidth consumption by customers and >>> that is in a database form that we can perform queries on >>> 2) Data that can be exported to our customer portal page that will >>> show customers how much bandwidth they have consumed since the first of >>> each month >>> 3) A batch file showing customers over their thresholds that we can >>> import into our billing system (Freeside) at the end of the month so we >>> can bill overages >>> >>> Our system is setup as follows: >>> >>> 1) StarOS access points >>> 2) OSPF backbone back to two separate 50 meg Internet backbone links >>> 3) Mikrotik core routers at each backbone location >>> 4) StarOS routers performing NAT at each backbone location >>> 5) Mikrotik edge routers connected to the Internet backbone >>> >>> Radius accounting is not an option, due to inaccurate IP accounting >>> information returned by the StarOS APs. PPPoE is also not an option as >>> we have 2000+ customers in place and not all of the hardware would >>> easily convert to PPPoE. >>> >>> Ideally, the data should be collectable at the Mikrotik core routers, as >>> that is the place where all of the private IP traffic is still in its >>> pre-NAT status. We have been trying to keep track of it with Netflow >>> data from our Mikrotik core routers, but it does not seem to be accurate >>> and there are documented problems with the Mikrotik Netflow exports. We >>> have confirmed that the data we have been collecting is not accurate, >>> and I have no intention on billing a customer based on inaccurate data. >>> >>> We have a couple of reporting engines that we have tried, with mixed >>> levels of success. I did contact Brandon Checketts about his program, >>> which was close to what we wanted, but it is out of date and he was not >>> responsive so our efforts are focused on either using something open >>> source that we can modify or just buying an appliance that will do what >>> we need. My preference is to go open source because we have multiple >>> backbone connections and also because I have several consulting >>> customers who want to have similar setups put in place on their >>> networks. Also, I want to make sure that this is "revenue neutral" and >>> can pay for for itself in the overage billing after it is installed. >>> >>> We can install either a switch or a transparent bandwidth monitoring >>> server of some kind between the core and NAT servers to collect the data >>> flows. My lead tech and I are both Linux savvy, and would prefer >>> something that runs on Linux. >>> >>> I recall that Travis Johnson posted a description of an open source, >>> linux-based system that he uses to track bandwidth, but I cannot find >>> the email where he lays all of the elements out. Does anyone have any >>> recommendations for this situation? >>> >>> Thanks! >>> >>> Matt Larsen >>> vistabeam.com >>> >>> >>> >>> -------------------------------------------------------------------------------- >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> -------------------------------------------------------------------------------- >>> >>> WISPA Wireless List: wireless@wispa.org >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >>> >>> >>> >>> >> -- >> Scott Reed >> Sr. Systems Engineer >> GAB Midwest >> 1-800-363-1544 x2241 >> 1-260-827-2241 >> Cell: 260-273-7239 >> >> >> >> -------------------------------------------------------------------------------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> -------------------------------------------------------------------------------- >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
