DEV Community

screensforme
screensforme

Posted on

Android NSDService can resolve link local IPV6 address ?

I am trying to resolve a service in the network. NsdService/MDnssd discovers IPV4 and IPv6 addresses but finally it returns the resolves the service with IPV4 address, but it need it to be resolved with the IPv6 address. Am I missing anything.

05-25 10:19:53.930 16116 16116 D NsdManagerServiceResolver: Starting service resolution for 'E4B75FF5A2A4E172-0000000000000005'
05-25 10:19:53.930 1225 1767 D NsdService: Resolve service
05-25 10:19:53.930 1225 1767 D NsdService: mdnssd [resolve, 27, E4B75FF5A2A4E172-0000000000000005, _xxxxxx._tcp, local.]
05-25 10:19:53.931 713 732 D MDnsDS : resolveService(27, (null), E4B75FF5A2A4E172-0000000000000005, _xxxxxx._tcp, local.)
05-25 10:19:53.931 713 732 D MDnsDS : startMonitoring 27
05-25 10:19:53.931 713 732 D MDnsDS : triggering rescan
05-25 10:19:53.931 713 732 D MDnsDS : resolveService successful
05-25 10:19:53.931 713 731 D MDnsDS : Monitor poll got data pollCount = 2, 1
05-25 10:19:53.931 713 731 D MDnsDS : controlSocket shows revent= 1
05-25 10:19:53.931 713 731 D MDnsDS : MDnsSdListener::Monitor got 1
05-25 10:19:53.931 713 731 D MDnsDS : MDnsSdListener::Monitor poll rescanning - size=10, live=2
05-25 10:19:53.931 713 731 D MDnsDS : Going to poll with pollCount 3
05-25 10:19:54.209 713 731 D MDnsDS : Monitor poll got data pollCount = 3, 1
05-25 10:19:54.209 713 731 D MDnsDS : Monitor found [1].revents = 1 - calling ProcessResults
05-25 10:19:54.209 713 731 D MDnsDS : resolve succeeded for 27 finding E4B75FF5A2A4E172-0000000000000005._xxxxxx._tcp.local. at 240AC4EE3854.local.:5540 with txtLen 21
05-25 10:19:54.209 713 731 D MDnsDS : controlSocket shows revent= 0
05-25 10:19:54.209 713 731 D MDnsDS : Going to poll with pollCount 3
05-25 10:19:54.210 1225 1767 D NsdService: Native daemon message SERVICE_RESOLVED: 608 27 "E4B75FF5A2A4E172-0000000000000005._xxxxxx._tcp.local." "240AC4EE3854.local." 5540 21 "CENSST01MDAwB0NSQT0zMDADVD0x"
05-25 10:19:54.211 1225 1767 D NsdService: mdnssd [stop-resolve, 27]
05-25 10:19:54.211 713 732 D MDnsDS : Stopping resolve with ref 0x78704175e8
05-25 10:19:54.211 713 732 D MDnsDS : freeServiceRef 27
05-25 10:19:54.211 713 732 D MDnsDS : triggering rescan
05-25 10:19:54.211 1225 1767 D NsdService: mdnssd [getaddrinfo, 28, 240AC4EE3854.local.]
05-25 10:19:54.212 713 731 D MDnsDS : Monitor poll got data pollCount = 3, 2
05-25 10:19:54.212 713 732 D MDnsDS : getAddrInfo(28, (null) 0, 240AC4EE3854.local.)
05-25 10:19:54.212 713 731 D MDnsDS : Monitor found [1].revents = 32 - calling ProcessResults
05-25 10:19:54.212 713 731 D MDnsDS : controlSocket shows revent= 1
05-25 10:19:54.212 713 731 D MDnsDS : MDnsSdListener::Monitor got 1
05-25 10:19:54.212 713 731 D MDnsDS : MDnsSdListener::Monitor poll rescanning - size=10, live=1
05-25 10:19:54.212 713 731 D MDnsDS : Going to poll with pollCount 2
05-25 10:19:54.212 713 732 D MDnsDS : startMonitoring 28
05-25 10:19:54.212 713 732 D MDnsDS : triggering rescan
05-25 10:19:54.212 713 732 D MDnsDS : getAddrInfo successful
05-25 10:19:54.212 713 731 D MDnsDS : Monitor poll got data pollCount = 2, 1
05-25 10:19:54.213 713 731 D MDnsDS : controlSocket shows revent= 1
05-25 10:19:54.213 713 731 D MDnsDS : MDnsSdListener::Monitor got 1
05-25 10:19:54.213 713 731 D MDnsDS : MDnsSdListener::Monitor poll rescanning - size=10, live=2
05-25 10:19:54.213 713 731 D MDnsDS : Going to poll with pollCount 3
05-25 10:19:54.213 713 731 D MDnsDS : Monitor poll got data pollCount = 3, 1
05-25 10:19:54.213 713 731 D MDnsDS : Monitor found [1].revents = 1 - calling ProcessResults
05-25 10:19:54.213 713 731 D MDnsDS : getAddrInfo succeeded for 28: 28 "240AC4EE3854.local." 120 192.168.1.25
05-25 10:19:54.213 713 731 D MDnsDS : getAddrInfo succeeded for 28: 28 "240AC4EE3854.local." 120 fe80::260a:c4ff:feee:3854
05-25 10:19:54.213 713 731 D MDnsDS : getAddrInfo succeeded for 28: 28 "240AC4EE3854.local." 120 2401:4900:1f25:7281:260a:c4ff:feee:3854
05-25 10:19:54.213 713 731 D MDnsDS : controlSocket shows revent= 0
05-25 10:19:54.213 713 731 D MDnsDS : Going to poll with pollCount 3
05-25 10:19:54.213 1225 1767 D NsdService: Native daemon message SERVICE_GET_ADDR_SUCCESS: 612 28 "240AC4EE3854.local." 120 192.168.1.25
05-25 10:19:54.214 1225 1767 D NsdService: mdnssd [stop-getaddrinfo, 28]
05-25 10:19:54.214 713 732 D MDnsDS : Stopping getaddrinfo with ref 0x78704175b8
05-25 10:19:54.214 713 732 D MDnsDS : freeServiceRef 28
05-25 10:19:54.214 713 732 D MDnsDS : triggering rescan
05-25 10:19:54.215 713 731 D MDnsDS : Monitor poll got data pollCount = 3, 2
05-25 10:19:54.215 713 731 D MDnsDS : Monitor found [1].revents = 32 - calling ProcessResults
05-25 10:19:54.215 713 731 D MDnsDS : controlSocket shows revent= 1
05-25 10:19:54.215 1225 1767 E NsdService: id 28 for SERVICE_GET_ADDR_SUCCESS has no client mapping
05-25 10:19:54.215 713 731 D MDnsDS : MDnsSdListener::Monitor got 1
05-25 10:19:54.215 713 731 D MDnsDS : MDnsSdListener::Monitor poll rescanning - size=10, live=1
05-25 10:19:54.215 713 731 D MDnsDS : Going to poll with pollCount 2
05-25 10:19:54.215 1225 1767 E NsdService: Unhandled { when=-1ms what=393242 obj=com.android.server.NsdService$NativeEvent@3104a54 target=com.android.internal.util.StateMachine$SmHandler }
05-25 10:19:54.215 1225 1767 E NsdService: id 28 for SERVICE_GET_ADDR_SUCCESS has no client mapping
05-25 10:19:54.215 1225 1767 E NsdService: Unhandled { when=-1ms what=393242 obj=com.android.server.NsdService$NativeEvent@58d6dfd target=com.android.internal.util.StateMachine$SmHandler }
05-25 10:19:54.215 16116 17047 I NsdManagerServiceResolver: Resolved service 'E4B75FF5A2A4E172-0000000000000005' to /192.168.1.25

Top comments (0)