Anyway please read about NAT XSEL . On Mon, 2018-05-21 at 15:03 +0100, Simon Mousey Smith wrote: > Hi All > > Im trying to figure out how to use NFSen for NAT purposes > > Brief explain, how do I work out what I client used in download? > > A sample output I have is below: > > 2018-05-21 08:31:15.920 129.050 TCP 192.168.68.15:54355 -> 51.179.201.80:443 > 1720 122920 1 > 2018-05-21 08:31:15.930 129.050 TCP 51.179.201.80:443 -> 217.149.97.xxx:54355 > 3173 4.4 M 1 > > But I cant simply do in the filter ( ip 192.168.68.15 ) because that would > only show the first > line which is the clients UPLOAD in bytes and not there DOWNLOAD in bytes? > > Ive tried bi-directional BUT that simply shows me: > > 2018-05-21 08:31:15.920 199.550 TCP 192.168.68.15:54355 <-> 51.179.201.80:443 > 0 1724 0 123081 3 > > The sample command thats used shown by nfsen is: > > ** nfdump -M /data/nfsen/profiles-data/live/fth -T -R > 2018/05/21/nfcapd.201805210825:2018/05/21/nfcapd.201805211130 -m -c 10000 > nfdump filter: > Any > > > Am I just simply doing something wrong? > > Regards > > Simon > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Nfsen-discuss mailing list > Nfsen-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfsen-discuss mailing list Nfsen-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
