ifconfig lists IPv6 twice for one WG interface

* ifconfig lists IPv6 twice for one WG interface
@ 2019-03-05  9:50 Roman Mamedov
  0 siblings, 0 replies; only message in thread
From: Roman Mamedov @ 2019-03-05  9:50 UTC (permalink / raw)
  To: wireguard

Hello,

I'm facing a strange issue where "ifconfig" shows the IPv6 twice for one
particular WG interface. Other similar interfaces on the same machine aren't
affected. Can't pinpoint what's special about this one yet.

The IP is not added twice during interface setup. Adding it once more, as
expected results in

  # ip -6 addr add fd39:aa:3dc2:a78a:7900:fcd:12a3:6181/64 dev wgw
  RTNETLINK answers: File exists

The "ip" tool doesn't list the address twice:

  # ip a l dev wgw
  44: wgw: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1432 qdisc noqueue state UNKNOWN group default qlen 1000
      link/none 
      inet6 fd39:aa:3dc2:a78a:7900:fcd:12a3:6181/64 scope global 
         valid_lft forever preferred_lft forever

But please no comments about "ifconfig" being deprecated, I prefer to keep using
it for certain tasks.

Now adding some debug print to my interface creation script, with:

  ifconfig $IFACE
  ip -6 addr add $MYIP/64 dev $IFACE || exit 1
  ifconfig $IFACE

This results in such output:

  wgw       Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
            POINTOPOINT NOARP  MTU:1420  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000 
            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  wgw       Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
            inet6 addr: fd39:aa:3dc2:a78a:7900:fcd:12a3:6181/64 Scope:Global
            inet6 addr: fd39:aa:3dc2:a78a:7900:fcd:12a3:6181/64 Scope:Global
            POINTOPOINT NOARP  MTU:1420  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000 
            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Overall this doesn't seem to break anything, but might be a sign of something not gong
entirely right under the hood. Anyone seen the same thing?

-- 
With respect,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

^ permalink raw reply	[flat|nested] only message in thread