Advanced Full Trace Options

The advanced mode has a set of options, which allow more control of what is done during a full trace. The options can be passed as comma separated values.

Examples of options

Following options can be passed to the advance full trace, not all of them are compatible

• mode=basic

• loglevel=d599090

• loglevel=d5:m-:n-

• loglevel=none

• limit_lan=1

• filter_lan=port 5060 or portrange 6000-7000

• limit_lo=0,limit_lan=0,limit_wan=2,filter_lan=port 5060,loglevel=none

mode option

If the option mode=basic is set, the advanced full trace uses the same pcap settings as the basic mode, the filter options won't work, the limits should.

filter and limit options

Each of the currently possible network interfaces can be configured individually in terms of maximum file size and filter options. Following limit and filter options are available:

• limit_lan

• limit_wan

• limit_msp

• limit_lo

• filter_lan

• filter_wan

• filter_msp

• filter_lo

limit options

The limit options take the maximum filesize of the created pcap file and is given im MB. Note since log-rotating is used, two files might be produced, actually doubling the given amount storage. If the value is set to 0, no pcap trace is started for this device.

...

• limit_lan=3 (on a non LAN-WAN device)

• limit_lan=2 (on a LAN-WAN device)

• limit_wan=2 (on a LAN-WAN device)

• limit_lo=1

• limit_msp=0

filter options

The filter options can configure the pcap tracing options for each network device like it would be passed on the command line. If nothing is given, everything is recorded on the given network device. E.g.

...

only the misdn pcap trace should be started, nothing would be logged to the isgw.log, and no tcp pcap trace should be started.

loglevel option

loglevel can take a list of colon separated arguments

...