Yes that is what I am referring too. I think that would make editing
the colors from the Web UI a bit more practical. Thanks.
Adam Osterlund
Network Engineer
Wi-Fi Guys, LLC.
Office: 218-353-7798 x 107
On 7/22/2010 12:46 AM, Peter Haag wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 7/20/10 19:02, Adam Osterlund wrote:
>
>> Thanks for the comments.
>>
>> For the colors, I just find it a pain to change around the colors after
>> setting up the sources. I mention this because we currently have 50
>> different sources, and having to go to each one to change the colors
>>
> So, you refer to a new 1:1 profile, where channels are taken from the live
> profile?
> If so, I can make a patch, which inherits the colour settings from the live
> profile.
>
> Regards
>
> - Peter
>
>
>
>> around after the initial setup took me a while, where as if I did the
>> colors from the config file initially it would have saved me a lot of
>> time, hence why I said to do it at the file level. I also noticed that
>> these colors aren't saved when you go to make a new profile, and it
>> falls back on the ones specified in the file, so when putting multiple
>> sources into a new profile, you need to edit the colors again.
>>
>> Adam Osterlund
>> Network Engineer
>> Wi-Fi Guys, LLC.
>> Office: 218-353-7798 x 107
>>
>>
>> On 7/20/2010 11:55 AM, Peter Haag wrote:
>> Hi Adam,
>>
>> Just a few remarks:
>>
>> snipp ..
>>
>>
>>>>> === Step 6.3 ===
>>>>> Still in the nfsen.conf we add in our sources of netflows so it knows
>>>>> what ports to listen on. Keep in mind there is a 19 character limit on
>>>>> what you can specify for source names. Each new source needs it's own
>>>>> unique port number to listen on.
>>>>>
>>>>>
>> As of nfdump 1.6.x and nfsen-1.3.4, this is no longer required. If you
>> configure
>> more sources for the same port, nfcapd automagically separates them
>> correctly.
>> However, for heavily loaded systems, it's still recommended to use different
>> ports.
>>
>>
>>
>>>>> # Netflow sources
>>>>> # Define an ident string, port and colour per netflow source
>>>>> #
>>>>> # Required parameters:
>>>>> # ident identifies this netflow source. e.g. the router name,
>>>>> # Upstream provider name etc.
>>>>> # port nfcapd listens on this port for netflow data for this
>>>>> source
>>>>> # set port to '0' if you do not want a collector
>>>>> to be started
>>>>> # col colour in nfsen graphs for this source
>>>>> #
>>>>> # Optional parameters
>>>>> # type Collector type needed for this source. Can be 'netflow' or
>>>>> 'sflow'. Default is netflow
>>>>> # optarg Optional args to the collector at startup
>>>>> #
>>>>> # Syntax:
>>>>> # 'ident' => { 'port' => '<portnum>', 'col' =>
>>>>> '<colour>',
>>>>> 'type' => '<type>' }
>>>>> # Ident strings must be 1 to 19 characters long only, containing
>>>>> characters [a-zA-Z0-9_].
>>>>>
>>>>> %sources = (
>>>>> 'upstream1' => { 'port' => '9995', 'col' => '#0000ff',
>>>>> 'type' =>
>>>>> 'netflow' },
>>>>> 'peer1' => { 'port' => '9996', 'IP' => '172.16.17.18'
>>>>> },
>>>>> 'peer2' => { 'port' => '9996', 'IP' => '172.16.17.19'
>>>>> },
>>>>> );
>>>>>
>>>>> You can change the colors later on within nfsen but those changes won't
>>>>> be reflected in this file. And whenever you use that source for a
>>>>> different profile it will revert back to it's color in this file. So
>>>>> makes things a bit easier on yourself and choose the colors as you enter
>>>>> them in. It is a massive pain to change them from the web UI.
>>>>>
>>>>>
>> ?? What is a massive pain ?? Click on the edit button of the source you want
>> to change
>> and choose either from predefined colour palettes of use the colour picker.
>> It's as simple as that!
>>
>>
>>
>> Thanks and regards
>>
>> - Peter
>>
>>
>>
>>>>> Adam Osterlund
>>>>> Network Engineer
>>>>> Wi-Fi Guys, LLC.
>>>>> Office: 218-353-7798 x 107
>>>>>
>>>>>
>>>>> On 7/19/2010 12:03 PM, Adam Osterlund wrote:
>>>>>
>>>>>
>>>>>> I believe I worked out what was causing my issues.
>>>>>>
>>>>>> The the folder that nfsen was installed in belonged to root. So I
>>>>>> changed the user and the group of the folder over to www-data
>>>>>> (Ubuntu's apache user) and it began to work fine for me. I modified
>>>>>> the nfsen configuration to run under the www-data user as well.
>>>>>>
>>>>>> If interested I can post my step by step guide I worked up for Ubunutu
>>>>>> to get it running.
>>>>>> Adam Osterlund
>>>>>> Network Engineer
>>>>>> Wi-Fi Guys, LLC.
>>>>>> Office: 218-353-7798 x 107
>>>>>>
>>>>>> On 7/19/2010 11:17 AM, Benjamin . wrote:
>>>>>>
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I have the problem you mentionned in the first part of your email. My
>>>>>>> live pipe is populated
>>>>>>> and displays data, but my profiles, whatever theirs configuration are
>>>>>>> (shadowed etc...), are not populated.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I'm currently running Ubuntu 9.10 as well and NfSen 1.3.4. NfProfile
>>>>>>> and NfDump seems to be working fine.
>>>>>>>
>>>>>>> Any help would be much appreciated.
>>>>>>>
>>>>>>> Benjamin,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>>
>>>>>>> This SF.net email is sponsored by Sprint
>>>>>>> What will you do first with EVO, the first 4G phone?
>>>>>>> Visit sprint.com/first --http://p.sf.net/sfu/sprint-com-first
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Nfsen-discuss mailing list
>>>>>>> [email protected]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by Sprint
>>>>> What will you do first with EVO, the first 4G phone?
>>>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Nfsen-discuss mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
>>>>>
>>>>>
>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> Nfsen-discuss mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
>>
> - --
> _______ SWITCH - The Swiss Education and Research Network ______
> Peter Haag, Security Engineer, Member of SWITCH CERT
> PGP fingerprint: D9 31 D5 83 03 95 68 BA FB 84 CA 94 AB FC 5D D7
> SWITCH, Werdstrasse 2, P.O. Box, CH-8021 Zurich, Switzerland
> E-mail: [email protected] Web: http://www.switch.ch/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iQCVAwUBTEfbQ/5AbZRALNr/AQLdlAP9FhY/CsCj0rrRJbbxcjDThOzMKUeY0r1L
> xD6o2qg3v8L5THncb9VRF4K5/tqzDKWLJW2EFCDZfPN7KylWmR25vXqu2YiHxvgF
> iwZBSOFvSrDAOCwQiudZR6/+y6rp2liBY9cxZ9r+h9zLAhs56RUbEBTghe4Sg/rT
> 1d/DSLwgyyA=
> =ckGl
> -----END PGP SIGNATURE-----
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
