Bounty $200: Monitor bandwidth use on IP adresses. NOW $250

backbone

This looks like a possible solution.

http://bandwidthd.sourceforge.net/

Look okay? I may take this one up.

Thats more like it :)
I just testet the demo….
but I can`t see how I can get how many GB of traffic one Ip have use there? This mnd and last?
I see that it can write to a database, maybe just get the info out from there again?
Can the data be writen to an external mysql db on another server?

If you could do this in one package for pfsense it would be nice.

This is something I would pay to get done ;)

cmb

@sullrich:

This looks like a possible solution.

http://bandwidthd.sourceforge.net/

Except it'll put your interfaces in promiscuous mode, and since he's running VLAN's, it'll kill all his network connectivity because of the VLAN's + promisc FreeBSD bug. Won't work.

The only thing I know of that doesn't use promisc is NetFlow.

backbone: You need to look at what I suggested, as that's the only thing that's going to work for you in the foreseeable future.

omegadraconis

I ran across this: http://www.freebsd.org/cgi/query-pr.cgi?pr=72933
it's a patch to fix the problem for bge module. At the bottom of the page it linked to http://cvsup.pt.freebsd.org/cgi-bin/cvsweb/cvsweb.cgi/src/sys/dev/bge/if_bge.c
"Revision 1.148 / (download) - annotate - [select for diffs] , Mon Sep 18 22:18:21 2006 UTC (3 weeks, 3 days ago) by jkim
Branch: MAIN
Changes since 1.147: +28 -15 lines
Diff to previous 1.147

Do not strip VLAN tag in promiscuous mode."

It would seem to depend on the nic's your using, your going to have to figure out which kernel module your nic uses(http://www.freebsd.org/releases/6.1R/hardware-i386.html#ETHERNET) and see if it has been patched or is a problem.

cmb

Thanks for the pointer to that, omegadraconis. Looks like drivers are getting fixed one by one. We'll have to look at this again once 6.2 is out and we're using it.

Mercredi

i will pay another $50 for a package, that will help me to know how many GB of traffic every Internal IP address is using through my pfsense firewall with possibility to view statistics for a day, week, month, and also configurable local address table to exclude from calculation. i need this for my small office network and home use, there is not so much users and data to deploy NTOP and special accounting servers.

sullrich

Ok, if everyone wants to verify that their nics will work with the package I mentioned earlier, I'll go ahead and get started on bandwidthd.

backbone

@sullrich:

Ok, if everyone wants to verify that their nics will work with the package I mentioned earlier, I'll go ahead and get started on bandwidthd.

I have 2 onboard Broadcom BCM5721 cards, using the bge(4) driver?

Mercredi

@sullrich:

Ok, if everyone wants to verify that their nics will work with the package I mentioned earlier, I'll go ahead and get started on bandwidthd.

i am using intel pro100 management adapters, their name in system are fxp… thank you, sullrich.

sullrich

So we are a go?

Mercredi

sullrich: what do i need to do? i allready need statistics on traffic of each local user :)

backbone

@sullrich:

So we are a go?

If the nics are supported so yes :)

but can this system get info for 1.jan to 2.feb ? I see that it has info for an Interval, but I need to know how many GB traffic it use last mnd and so on…. Maybe the sensor system has what i need? It is the sensor system u want to make then? as a pfsense package?

backbone

@sullrich:

So we are a go?

So what do u say? :)
Something that could be done? :)

sullrich

Yeah, I'll start on it in the next day or so. However, I am not sure your nics work or not, honestly. Thats why i was asking you all ..

narf

Is there a list of drivers that have been patched to work with promisc + VLAN, or is the bge module the only one that has been fixed?

I'm just curious as i should be doing some hardware shopping, and its alot easier to just buy hardware that works, instead of waiting for drivers to be fixed.

//Richard.

sullrich

I would say it is the opposite and that most nics should work fine.

Mercredi

and any updated information?

sullrich

Doubtful. This thread went from promising to dead in the matter of a few days. What was almost 2K is now 250$ .. If I was Bill (which I am not) then I would be less than interested at this point for the amount of work that this entails.

billm

@sullrich:

Doubtful. This thread went from promising to dead in the matter of a few days. What was almost 2K is now 250$ .. If I was Bill (which I am not) then I would be less than interested at this point for the amount of work that this entails.

Wrong thread :) But this did go kind of dead all the same ;)

–Bill

sullrich

@billm:

@sullrich:

Doubtful. This thread went from promising to dead in the matter of a few days. What was almost 2K is now 250$ .. If I was Bill (which I am not) then I would be less than interested at this point for the amount of work that this entails.

Wrong thread :) But this did go kind of dead all the same ;)

–Bill

Second time this has happened to me. Woops ;)

narf

@billm:

Wrong thread :) But this did go kind of dead all the same ;)

–Bill

I was wondering why it went dead? I think we established that this would work with most NICs. I'd appreciate this functionality in pfsense. That way we'd have all the information in one logical place, instead of deploying multiply small appliances. I'd be willing to donate some cash to this effort as well… provided its still considered a possibility...