[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

[Evan Dandrea]

[11:52:24] <apw>	 ok there are a continuious stream of updates from the kernel
[11:52:37] <apw>	 becasue link level mappings are in the routing table, and they appear and dissapear
[11:52:39] <apw>	 all the time
[11:53:04] <apw>	 try sudo ip monitor
[15:12:24] <ev>	 so basically this approach is bogus then?
[15:13:46] <apw>	 well it needs consideration whether it is being selective enough
[15:14:14] <apw>	 as as a naive user i look at the raw stream it changes whenever an arp entry appears or dissappears
[15:14:30] <apw>	 now they mey be doing it 'righter' by trying to select specific subsets of
[15:14:42] <apw>	 the messages, or not, one wuold need to emit the ones they keep/drop to see
[15:14:52] <apw>	 it is possible they have not adapted to the new world order
[15:16:41] <ev>	 new world order?
[15:19:05] <apw>	 when the link level addresses got promoted from another separate cache into the
[15:19:13] <apw>	 routing table, which sped things up
[15:19:53] <apw>	 so ipv6 neibour discovery results, and ipv4 arp results get put in as a real 'host route' now
[15:20:01] <apw>	 and then removed when they time out
[15:20:09] <apw>	 which might mean things looking for route changes would see both
[15:20:22] <apw>	 of those, and think networking changed, but you would need to shove a print in there
[15:20:24] <apw>	 to be sure me thinks

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/991481

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in “glib2.0” package in Ubuntu:
  Confirmed

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions