If you want to access services running on your development machine's loopback interface (a.k.a. For information about how to let emulator instances communicate over TCP/UDP, see Connecting Emulator Instances.Īlso note that the address 127.0.0.1 on your development machine corresponds to the emulator's own loopback interface. The instances are isolated by a router and can not see each other on the same network. That means that if you have two instances running concurrently on your machine, each will have its own router and, behind that, each will have an IP address of 10.0.2.15. Note that the same address assignments are used by all running emulator instances. The emulated device's own loopback interface The emulated device's own network/ethernet interface Optional second, third and fourth DNS server (if any) Special alias to your host loopback interface (i.e., 127.0.0.1 on your development machine) Addresses within this space are pre-allocated by the emulator/router as follows:

The virtual router for each instance manages the 10.0.2/24 network address space - all addresses managed by the router are in the form of 10.0.2., where is a number. Instead, it sees only that it is connected through Ethernet to a router/firewall. An emulated device can not see your development machine or other emulator instances on the network. Network Address SpaceĮach instance of the emulator runs behind a virtual router/firewall service that isolates it from your development machine's network interfaces and settings and from the internet. The sections below introduce the emulator's network architecture and capabilities. The emulator provides versatile networking capabilities that you can use to set up complex modeling and testing environments for your application.

Android emulator hosts mac