nerves_init_gadget is most useful for projects on gadget capable hardware like the Raspberry Pi Zero. The Pi 3 can’t do gadget mode, which would give you the networking over usb that I think you may be expecting.
Can you describe a little more about your project setup? Namely, what’s your host OS and how are you networking the two devices together? If it’s over WiFi, there may be some additional things your DNS server or host OS need in order for mdns to work so it’s delpful to know more context.
understood about nerves_init_gadget, I used it because it set up all the network and mdnds. Do you recommend me to use those packages instead of nerves_init_gadget?
My test setup is using wifi, but I haven’t decided yet if on production will be via wifi or ethernet. Probably a mix of them depending on my customer’s networks.
My host OS is ArchLinux, the host is connected via ethernet, and the Raspberry Pi over wifi as I mentioned.
My idea is to connect the device in my customer’s location and ask use mdnds to setup a hostname like: http://myapp for using it. I’d need to know what changes I need on the router or the hosts. For my customers I could have windows, macOS and Linux hosts.
I use a very similar config, and i get mdns on my rpi3 via wifi, and i also run arch linux. Have you tried getting Mdns working before this? I found i had to change a few configurations and install a few packages to get mdns to work.
but where? I can’t find an example of how to use it.
Once the device starts, I can connect to a iex shell with ssh nerves.local. Is it possible to access the started mddns server that nerves_init_gadget started?