ncurses6
by Jan Engelhardt
The following changes since commit 8143dabb91939f8731853981528a7cdc460768a1:
iptraf.c: fix displaying long interface names (2012-11-28 10:20:30 +0100)
are available in the git repository at:
git://git.inai.de/iptraf master
for you to fetch changes up to ed6b73679dac063ef91c96e21aef26ca06e990b5:
build: prefer ncurses6 and wide (2013-03-28 20:56:11 +0100)
----------------------------------------------------------------
Jan Engelhardt (1):
build: prefer ncurses6 and wide
Makefile | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
10 years, 5 months
- 2
- 6
forward dns lookup
by hamann.w＠t-online.de
Hi,
I am currently trying to use iptraf logging in order to discover unwanted
network traffic on one machine
Now, the reverse lookup means that I get
bigsite.com - reverse matches the site (and is meaningful)
somehost.com - this could be goodsite.com or badsite.com hosted in the same
datacenter
1.2.3.4 - no reverse possible
Without extra research it is not possible to detect whether an ip address is
near (in the same /24) as another one previously resolved
So I would like to ask
a) is it possible to log 1.2.3.4 (somehost.net)
b) since iptraf looks at the interface anyway, would it be possible to
capture dns traffic and use that instead of reverse lookup (or in addition)
i.e. if machine has asked for badsite.com, show that name along with the ip
address?
Regards
Wolfgang Hamann
10 years, 6 months
- 1
- 0
- ← Newer
- 1
- Older →