hey, i happily use iftop for months
i now recognize some strange behaviour
using iftop on an wireguard vpn tunnel (layer3) if i can easily see all
the endpoints for IPv4 . they are shown as they should
in that case 192.168.99.something
if i use v6 inside this wireguard tunnel .. so the IPs are more like
fdf1::16:3e75:72af (/64) than there is only one ip shown all the time -
or one dns entry (from /etc/hosts)
but strangely iftop get the streams right ... so i have plenty of
connections from
fdf1::16:3e75:72af
to
fdf1::16:3e75:72af
they all show the correct amount of traffic, but the naming/display
"error" makes it difficult to use or understand whats going on.
if i restart iftop, it may be so that another of the involved ipv6(or
dns) is showed for all involved endpoints
any idea if i do something wrong,or where the error origin is?
thx a lot
fuzzle/freiburg
Example (where rauberhaus-v6 is just one of the ipv6 involved, if
restartet it could be any other too)
rauberhaus-v6 =>
rauberhaus-v6 167Kb 114Kb
93.5Kb
<= 162Kb
110Kb 89.0Kb
rauberhaus-v6 =>
rauberhaus-v6 8.16Kb 7.07Kb
7.06Kb
<= 160Kb
107Kb 87.5Kb
--
make the world nicer, please use PGP encryption
