`eth0` net. interface IP is not displayed in the home fragment
See original GitHub issueIf an android device is connected by an ethernet adapter (recognized as eth0
in my case) the whole app works perfectly fine, that is you can flawlessly toggle the “Wireless ADB” on/off as you please and it all works well.
This behaviour can be observed on the versions 6.0.0 and 5.1.1 of this app, I haven’t tested the previous ones.
Here’s a logcat which has run since I’ve plugged the ethernet adapter until I’ve toggled “Wireless ADB” by the app itself, run a test command over adb by my pc and toggled it off, I don’t know if it could be really useful but I guess it can’t hurt.
Here’s an eventually(?) useful ip
output:
vayu:/ $ ip -o -4 addr | grep eth
70: eth0 inet 192.168.1.130/24 brd 192.168.1.255 scope global eth0\ valid_lft forever preferred_lft forever
It unfortunately just doesn’t display the correct IP address in the home fragment, it displays “0.0.0.0:5555” instead.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to check whether an ethernet interface is up with some IP ...
If an interface appears in /proc/net/route , then it's in the routing table. Generally any interface that has been assigned an IP address...
Read more >Unable to activate eth0 under RHEL6 - Red Hat Customer Portal
Looking under /etc/sysconfig/network-scripts, there was no eth0 file. So I create the file, however I don't have a UUID in it.
Read more >IP Fragmentation in Detail - Packet Pushers
When a host sends an IP packet onto the network it cannot be larger than the maximum size supported by that local network....
Read more >Troubleshoot Switch Port and Interface Problems - Cisco
This document describes how to determine why a port or interface experiences problems.
Read more >NCC Health Check: cvm_mtu_check - Nutanix Support Portal
The "NIC MTU Ping Check" check tests CVM eth0 MTU settings by way of running ICMP echo (ping) with the DF bit (do...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Oh, that’s because we only retrieve IP addresses from wlan0/wlan1, not eth0.
https://github.com/RikkaApps/WADB/blob/c6fe49938efa35487a075c07b6bf7d63d847799d/app/src/main/java/moe/haruue/wadb/util/NetworksUtils.java#L31-L40
And WADB is “Wireless adb” instead of “Wired adb”,whatever.So maybe we should provide an option to lets you select a customized interface, or just retrieve IP from every interface and display them in the format
"[$interface] $address"
.As of https://github.com/RikkaApps/WADB/commit/212af1d68ec6dcc3ba2b93e37a966a3692a40d2a as these screenshot show I’d say it works perfectly too.