mDNS for device discovery in IOT Protocols - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the mDNS library for device discovery.

IOT Protocols

import [1]

Drag options to blanks, or click blank then click option'

Ahttp

Bjson

Czeroconf

Dsocket

Attempts:

3 left

💡 Hint

Common Mistakes

Importing unrelated libraries like socket or http.

Using json which is for data formatting, not discovery.

The zeroconf library is commonly used in Python for mDNS (multicast DNS) service discovery.

2fill in blank

medium

Complete the code to create a Zeroconf instance for mDNS service discovery.

IOT Protocols

from zeroconf import Zeroconf

zeroconf = [1]()

Drag options to blanks, or click blank then click option'

AZeroconf

BServiceInfo

CServiceBrowser

DSocket

Attempts:

3 left

💡 Hint

Common Mistakes

Using ServiceBrowser instead of Zeroconf to create the instance.

Trying to instantiate Socket which is unrelated here.

The Zeroconf() class creates an instance to manage mDNS services.

3fill in blank

hard

Fix the error in the code to correctly browse for HTTP services over mDNS.

IOT Protocols

from zeroconf import ServiceBrowser, Zeroconf

zeroconf = Zeroconf()
browser = ServiceBrowser(zeroconf, [1], None)

Drag options to blanks, or click blank then click option'

A_ftp._tcp.local.

B_http._tcp.local.

C_http._udp.local.

Dhttp._tcp.local.

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong protocol like UDP instead of TCP.

Missing underscore at the start of service type string.

The correct service type string for HTTP over TCP in mDNS is _http._tcp.local..

4fill in blank

hard

Fill both blanks to create a ServiceInfo object for advertising a printer service.

IOT Protocols

from zeroconf import ServiceInfo

info = ServiceInfo(
    [1],
    "MyPrinter._ipp._tcp.local.",
    addresses=[[2]],
    port=631,
    properties={}
)

Drag options to blanks, or click blank then click option'

A"_ipp._tcp.local."

Bb"\xc0\xa8\x01\x64"

C"_http._tcp.local."

Db"\x7f\x00\x00\x01"

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP service type instead of IPP.

Passing IP as a normal string instead of bytes.

The service type for IPP printers is "_ipp._tcp.local.". The address must be a byte string representing the IP, here b"\xc0\xa8\x01\x64" is 192.168.1.100.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps device names to their IP addresses for devices with port above 8000.

IOT Protocols

devices = {
    [1]: [2] for [3] in discovered_devices if [3]['port'] > 8000
}

Drag options to blanks, or click blank then click option'

Adevice['name']

Bdevice['ip']

Cdevice

Ddevice_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using device['name'] as the loop variable instead of key.

Mixing up keys and values in the comprehension.

The comprehension iterates over discovered_devices as device, uses device['name'] as key and device['ip'] as value. device is the dictionary for each device.

Practice

1. What is the main purpose of mDNS in device discovery?

easy

A. To assign IP addresses to devices on the internet

B. To allow devices to find each other automatically on the same local network

C. To encrypt communication between devices

D. To connect devices over long distances using satellites

Solution

1. Step 1: Understand mDNS function

   mDNS stands for multicast DNS and is used for local network device discovery without a central DNS server.

2. Step 2: Identify the correct purpose

   It helps devices find each other automatically on the same local network using multicast messages and .local names.

3. Final Answer:

   To allow devices to find each other automatically on the same local network -> Option B

4. Quick Check:

   mDNS = local device discovery [OK]

Hint: mDNS is for local network device discovery only [OK]

Common Mistakes:

• Confusing mDNS with DHCP for IP assignment
• Thinking mDNS encrypts data
• Assuming mDNS works over the internet

2. Which of the following is the correct syntax to query a device named printer.local using mDNS on a Linux terminal?

easy

A. mdns-query printer.local

B. mdns-scan printer.local

C. dnslookup printer.local

D. ping printer.local

Solution

1. Step 1: Identify common mDNS query commands

   On Linux, mDNS names like printer.local can be resolved using standard commands like ping or avahi-resolve, but ping is simplest.

2. Step 2: Check command validity

   Only ping printer.local is a valid and common way to test mDNS name resolution; others are not standard commands.

3. Final Answer:

   ping printer.local -> Option D

4. Quick Check:

   Use ping with .local names for mDNS queries [OK]

Hint: Use ping with .local names to test mDNS resolution [OK]

Common Mistakes:

• Using non-existent commands like mdns-query
• Confusing DNS lookup tools with mDNS
• Forgetting the .local suffix

3. Given this Python snippet using zeroconf library to discover mDNS services, what will be printed if a device named 'lamp.local' is found?

from zeroconf import Zeroconf
zeroconf = Zeroconf()
services = zeroconf.get_service_info('_http._tcp.local.', 'lamp._http._tcp.local.')
if services:
    print(services.server)
else:
    print('No device found')

medium

A. No device found

B. lamp.local

C. lamp.local.

D. lamp._http._tcp.local.

Solution

1. Step 1: Understand zeroconf get_service_info output

   The get_service_info method returns a ServiceInfo object with a 'server' attribute that ends with a dot, e.g., 'lamp.local.'

2. Step 2: Analyze the print statement

   If the device is found, services.server prints the full hostname with trailing dot, so output is 'lamp.local.'

3. Final Answer:

   lamp.local. -> Option C

4. Quick Check:

   zeroconf server attribute ends with dot [OK]

Hint: zeroconf server names end with a dot '.' [OK]

Common Mistakes:

• Omitting the trailing dot in hostname
• Confusing service type with hostname
• Assuming no device found when device exists

4. You tried to discover devices using mDNS but got no results. Which of these is the most likely cause?

medium

A. The devices are on a different subnet without multicast routing

B. The devices have static IP addresses

C. The devices use HTTPS instead of HTTP

D. The devices have firewalls disabled

Solution

1. Step 1: Understand mDNS network scope

   mDNS works only within the same local network segment (subnet) because multicast packets are not routed across subnets by default.

2. Step 2: Identify why no devices found

   If devices are on a different subnet, mDNS queries won't reach them, causing no discovery results.

3. Final Answer:

   The devices are on a different subnet without multicast routing -> Option A

4. Quick Check:

   mDNS limited to local subnet without routing [OK]

Hint: mDNS only works within the same subnet [OK]

Common Mistakes:

• Thinking static IPs block mDNS
• Confusing protocol type with discovery issues
• Assuming firewalls off always helps discovery

5. You want to set up a smart home device to be discoverable via mDNS with the name smartlight.local. Which configuration step is essential to ensure correct mDNS discovery?

hard

A. Configure the device to advertise its service using the mDNS protocol with the hostname smartlight.local

B. Assign a public IP address to the device

C. Disable multicast on the device's network interface

D. Set the device's DNS server to 8.8.8.8

Solution

1. Step 1: Understand mDNS advertisement

   For a device to be discoverable via mDNS, it must broadcast its hostname and service on the local network using mDNS protocol.

2. Step 2: Identify correct configuration

   Setting the device to advertise as smartlight.local via mDNS is essential; public IP or external DNS settings do not affect local mDNS discovery.

3. Final Answer:

   Configure the device to advertise its service using the mDNS protocol with the hostname smartlight.local -> Option A

4. Quick Check:

   mDNS requires local service advertisement [OK]

Hint: Device must advertise its mDNS hostname locally [OK]

Common Mistakes:

• Assigning public IP instead of local mDNS name
• Disabling multicast which breaks mDNS
• Using external DNS servers for local discovery