Relay mode enables the user to relay NFC traffic over the network. All traffic on the ISO 14443 layer can be relayed, along with initial tag information. Please see clone mode for more information.
- Two Android devices that will perform the relaying (called relay devices). A device cannot be used as both the reader and the tag (HCE) when participating in relaying.
- Reader and tag whose traffic should be relayed (called relayed devices). These devices can be Android devices.
- Any device running the NFCGate server application. This can also be one of the Android devices running Termux.
Relay devices:
- Android 4.4+ (API level 19+)
- EdXposed or Xposed
- Architecture: ARMv8-A, ARMv7
- The device acting as tag (in "tag mode") requires HCE support.
- Networking connectivity with the server application, more specifically a TCP connection is required.
Relayed devices:
- No special configuration required.
On both relay devices:
- Switch to
Settings
in the navigation drawer. - Specify
Hostname
andPort
andSession
. - Make sure the server application is running and accessible over the network.
- Switch to
Relay Mode
in the navigation drawer. - Click
Reader
orTag
depending on device: For a relay, one device in "reader mode" and one device in "tag mode" is required. - When the connection has been successfully established, the app will show a green status indicator.
Relaying traffic:
- Place the relay device in "reader mode" to read the tag that you want to relay.
- Place the second relay device in "tag mode" on the relayed reader.
The NFC traffic is captured and available in Logging
for later use.
If the relayed reader and/or tag have constrained requirements for communication time, timeouts can occur. In addition to that, poor network connectivity might also negatively affect performance and reliability.