# Perform Ethernet operations

The mezzanine board adds support for additional Ethernet interfaces, each accessible through standard RJ45 connectors. These interfaces enable robust, high-bandwidth connectivity suited to complex data transfer needs and multi-device environments.

The additional Ethernet ports facilitate use cases such as server networking, IoT aggregation, and high-speed local communication. Consider the following points about Ethernet interfaces:

- Alongside the mainboard’s Ethernet connection, three supplemental ports are available on the mezzanine board.
- Standard RJ45 connectors activate each interface.
- All Ethernet interfaces are enabled by default from device bootup.

## Dragonwing IQ-8275 mainboard

The following table lists the mainboard Ethernet component.

Mainboard Ethernet

| Board/card | Component | Supported speeds | Validated on | Connector |
| --- | --- | --- | --- | --- |
| IQ-8275 | QEP8121 PHY | 10M/100M/1G/2.5G | Dragonwing IQ-8275 EVK | RJ45 |

For more information on mainboard Ethernet enablement, see the [Qualcomm Linux Ethernet Guide](https://docs.qualcomm.com/doc/80-80021-26/topic/perform-ethernet-operations.html).

## Mezzanine board or card for Ethernet

The following table lists the mezzanine board or card components for Ethernet.

Mezzanine board or card: Ethernet

| Board/card | Component | Supported speeds | Validated on | Enabled by |
| --- | --- | --- | --- | --- |
| Mezzanine card | QEP8121 PHY | 10M/100M/1G/2.5G | Dragonwing IQ-8275 EVK with mezzanine kit | RJ45 connector |
| QPS615 PCIe switch | AQR113 PHY | 10M/100M/1G/2.5G/5G/10G | Dragonwing IQ-8275 EVK with mezzanine kit | RJ45 connector |
| QPS615 PCIe switch | QEP8121 PHY | 10M/100M/1G/2.5G | Dragonwing IQ-8275 EVK with mezzanine kit | RJ45 connector |

## Manage network interfaces

Perform basic operations such as configuring addresses, viewing the status of links, monitoring connections, and debugging connection failures using various tools.

### Verify data connectivity

To verify connectivity between the device interface and the interface that’s connected remotely, run the following command:

ping <ip-address>
    Copy to clipboard

Note

The client IP address must be in the same subnet as that of the device IP address.

**Sample output**

The following sample output shows the network connectivity of the Dragonwing IQ-8275 EVK with mezzanine kit to the host PC:

> 
> 
> sh-5.2# ping 169.254.198.80
>     PING 169.254.198.80 (169.254.198.80) 56(84) bytes of data.
>     64 bytes from 169.254.198.80: icmp_seq=1 ttl=64 time=0.561 ms
>     64 bytes from 169.254.198.80: icmp_seq=2 ttl=64 time=1.58 ms
>     64 bytes from 169.254.198.80: icmp_seq=3 ttl=64 time=1.88 ms
>     64 bytes from 169.254.198.80: icmp_seq=4 ttl=64 time=1.75 ms
>     64 bytes from 169.254.198.80: icmp_seq=5 ttl=64 time=1.84 ms
>     64 bytes from 169.254.198.80: icmp_seq=6 ttl=64 time=1.09 ms
>     ^C
>     --- 169.254.198.80 ping statistics ---
>     6 packets transmitted, 6 received, 0% packet loss, time 5011ms
>     rtt min/avg/max/mdev = 0.561/1.450/1.883/0.476 ms
>     Copy to clipboard

### Configure the NIC settings

To view the network interface controller (NIC) parameters and configure the NIC settings such as speed, port, and auto-negotiation, run the following command:

ethtool <eth-number>
    Copy to clipboard

**Sample output**

The following sample output shows the status of a link:

> 
> 
> ethtool eth0
>     Settings for eth0:
>        Supported ports: [  ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>                                2500baseT/Full
>        Supported pause frame use: Symmetric Receive-only
>        Supports auto-negotiation: Yes
>        Supported FEC modes: Not reported
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>                                2500baseT/Full
>        Advertised pause frame use: Symmetric Receive-only
>        Advertised auto-negotiation: Yes
>        Advertised FEC modes: Not reported
>        Link partner advertised link modes:  100baseT/Full
>                                            1000baseT/Full
>                                            2500baseT/Full
>        Link partner advertised pause frame use: Symmetric Receive-only
>        Link partner advertised auto-negotiation: Yes
>        Link partner advertised FEC modes: Not reported
>        Speed: 2500Mb/s
>        Duplex: Full
>        Auto-negotiation: on
>        master-slave cfg: preferred slave
>        master-slave status: slave
>        Port: Twisted Pair
>        PHYAD: 24
>        Transceiver: external
>        MDI-X: on (auto)
>        Supports Wake-on: g
>        Wake-on: d
>        Current message level: 0x0000003f (63)
>                             drv probe link timer ifdown ifup
>        Link detected: yes
>     Copy to clipboard

### Configure the network interface

To assign an address to a network interface and configure the interface with additional parameters like MTU, run the following command:

ip <options>
    Copy to clipboard

For more information about the `ip` command, see [ip(8) - Linux manual page](https://man7.org/linux/man-pages/man8/ip.8.html).

For more information about configuring the network interface, see [Bring up Ethernet](https://docs.qualcomm.com/doc/80-80021-26/topic/bring_up-ethernet.html#bringup-qcs9075).

**Sample output**

The following sample output shows the network interface information:

> 
> 
> ip a
>     lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
>        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>        inet 127.0.0.1/8 scope host lo
>        valid_lft forever preferred_lft forever
>        inet6 ::1/128 scope host noprefixroute
>        valid_lft forever preferred_lft forever
>     
>     end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
>        link/ether 8c:fd:f0:ae:cb:44 brd ff:ff:ff:ff:ff:ff
>        altname enx8cfdf0aecb44
>        inet 192.168.245.11/24 brd 192.168.245.255 scope global dynamic end0
>        valid_lft 68211sec preferred_lft 68211sec
>        inet6 fe80::f3e9:48b1:6bf6:8f82/64 scope link noprefixroute
>        valid_lft forever preferred_lft forever
>     
>     eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
>        link/ether 8c:fd:f0:ae:cb:46 brd ff:ff:ff:ff:ff:ff
>        altname enx8cfdf0aecb46
>     
>     enp5s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
>        link/ether 10:22:33:44:55:66 brd ff:ff:ff:ff:ff:ff
>        altname enx102233445566
>     
>     enp5s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
>        link/ether 10:22:33:44:55:66 brd ff:ff:ff:ff:ff:ff
>     
>     docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
>        link/ether 5e:70:16:a1:cd:07 brd ff:ff:ff:ff:ff:ff
>        inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
>        valid_lft forever preferred_lft forever
>     Copy to clipboard

### Analyze the network traffic

To analyze the network traffic by intercepting and displaying packets that are created or received by a network interface, run the following command:

tcpdump <options>
    Copy to clipboard

**Example**

To analyze the network traffic, run the following command:

tcpdump -i any -s 0 -w /data/tcpdump.pcap
    Copy to clipboard

### Identify and read the network route

A routing table has the parameters necessary to identify and read the network route. To retrieve information on a routing table, run the following command:

ip r s
    Copy to clipboard

For more information about the `ip` command, see [ip(8) - Linux manual page](https://man7.org/linux/man-pages/man8/ip.8.html).

**Sample output**

The following sample output shows the retrieval of the IP routing table:

> 
> 
> ip r s
>     default via 192.168.245.1 dev eth0 proto dhcp src 192.168.245.31 metric 10
>     default via 192.168.245.1 dev eth0 proto dhcp src 192.168.245.31 metric 101
>     172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
>     192.168.245.0/24 dev end0 proto kernel scope link src 192.168.245.11
>     192.168.245.0/24 dev end0 proto kernel scope link src 192.168.245.11 metric 100
>     192.168.245.0/24 dev eth0 proto kernel scope link src 192.168.245.31 metric 101
>     192.168.245.1 dev eth0 proto dhcp scope link src 192.168.245.31 metric 10
>     Copy to clipboard

## Next steps

- [Perform Bluetooth GAP functions.](https://docs.qualcomm.com/doc/80-80022-44/topic/iq8-ifp-ug-bt-gap.html#perform-bluetooth-gap-functions)
- [Configure Wi-Fi.](https://docs.qualcomm.com/doc/80-80022-44/topic/iq8-ifp-ug-config-wifi.html#configure-wifi)
- [Set up the LVDS display panel.](https://docs.qualcomm.com/doc/80-80022-44/topic/iq8-ifp-ug-set-up-display.html#set-up-lvds-display-panel)

Last Published: May 12, 2026

[Previous Topic
Validate USB and PCIe](https://docs.qualcomm.com/bundle/publicresource/80-80022-44/topics/iq8-ifp-ug-validate-usb-and-pcie.md) [Next Topic
Perform Bluetooth GAP functions](https://docs.qualcomm.com/bundle/publicresource/80-80022-44/topics/iq8-ifp-ug-bt-gap.md)