Commit 3f5ee02f authored Aug 17, 2021 by Mike Yu

Remove the confusing log in getPrefix64

This log can sometimes confuse people. A common case where this
log is printed is that an app specifies AF_UNSPEC but there are
no resolved IPv6 addresses for the hostname.

ResolverController: No valid NAT64 prefix (106, <unspecified>/0)

After this change, the resolver logs will still be enough for us
to infer if DNS64 synthesis is performed.

Bug: 196888805
Test: build dnsresolver pass
Change-Id: Ic06299d1a0c6526e7ed1a0a418a8da19dbf2b6da

parent b6e255d1

ResolverController.cpp

+0 −2

Original line number	Diff line number	Diff line
		@@ -294,8 +294,6 @@ void ResolverController::stopPrefix64Discovery(int32_t netId) {
		int ResolverController::getPrefix64(unsigned netId, netdutils::IPPrefix* prefix) {
		netdutils::IPPrefix p = mDns64Configuration.getPrefix64(netId);
		if (p.family() != AF_INET6 \|\| p.length() == 0) {
		LOG(INFO) << "No valid NAT64 prefix (" << netId << ", " << p.toString().c_str() << ")";

		return -ENOENT;
		}
		*prefix = p;