Hi Luca
I try this:
tcpdump -w radius.pcap -i ens192f0 port radius or port radius-acct or port
> radius-dynauth
and radius.pcap file is healthy and readable in wireshark.(except a few
packets )
I think this issue related to new updates.
On Wed, May 16, 2018 at 1:25 AM, Luca Deri
Hi Simone,
Here the ntopng and nNrobe configuration used.
Ntopng:
--interface eth0
--interface tcp://127.0.0.1:5556
--local-networks 172.22.9.0/24,192.168.0.0/16,172.22.0.0/16,10.0.0.0/8
--daemon
--user ntopng
--pid /var/run/ntopng/ntopng.pid
--http-port 0
--https-port :3001
--data-dir
> On 17 May 2018, at 14:30, Gerhard Mourani wrote:
>
> Hi Simone,
>
> Here the ntopng and nNrobe configuration used.
>
> Ntopng:
> --interface eth0
> --interface tcp://127.0.0.1:5556
> --local-networks 172.22.9.0/24,192.168.0.0/16,172.22.0.0/16,10.0.0.0/8
> --daemon
>
Yes
On May 17, 2018, at 9:03 AM, Simone Mainardi
> wrote:
On 17 May 2018, at 14:30, Gerhard Mourani
> wrote:
Hi Simone,
Here the ntopng and nNrobe configuration used.
Ntopng:
--interface eth0
please see this
https://asciinema.org/a/182023
On Thu, May 17, 2018 at 2:13 PM, Milad Arabi wrote:
> Hi Luca
> I try this:
>
> tcpdump -w radius.pcap -i ens192f0 port radius or port radius-acct or port
>> radius-dynauth
>
>
> and radius.pcap file is healthy and readable