The WiFi diagnostic does not work if there is another operational network interface #41
Assignees
Labels
Comments
|
Ah ha! I was bound to miss a use case scenario. Appreciate it. Confirming, there are two network interfaces on this unit? You title "The WiFi diagnostic does not work if there is another operational network interface" indicated there may be? Ethernet? I can adapt the script accordingly, but just wanted to clarify. Appreciate it. :) |
|
Don't feel bad. I'll bet that it never occurred to the guys who designed
the 737 MAX that the angle of attack sensors would fail. That oversight
led to the deaths of 384 people. Funny, sometimes, how the real world
breaks our software.
In my case, the WiFi is broken. I have a USB to Ethernet adapter that
looks like an Ethernet and that is working. The WiFi looks like a WiFi in
a place where is no WiFi, none at all. It thinks it's working, but it
isn't. So it depends on your definition of "operational". The WiFi think
it is working, but because the RF side is broken, it isn't/
One way to test the WiFi is to run the iw dev wlp2s0 scan | fgrep
SSID: command.
If it sees 2 or more SSIDs, then the WiFi is probably working. Similarly,
if the ip --stats link list command shows that the counters are
incrementing in, say, 10 seconds, then the Ethernet is probably good. The ip
link list command will also tell you if the NIC sees a carrier.
I hope this answers your question. I'd love to beta test it for you.
Jeff
…On Thu, Oct 31, 2024 at 6:26 PM Matt Hartley ***@***.***> wrote:
Ah ha! I was bound to miss a use case scenario. Appreciate it. Confirming,
there are two network interfaces on this unit? You title "The WiFi
diagnostic does not work if there is another operational network interface"
indicated there may be? Ethernet? I can adapt the script accordingly, but
just wanted to clarify.
Appreciate it. :)
—
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEGDBYRZD3H5SPA4XG2L7DZ6LKEZAVCNFSM6AAAAABQIKVT76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJRGEZDEMBSGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Have not forgotten about this, but it may be a bit before I can circle back to this. Just updating I have not forgotten. |
|
No worries, thanks for the update!
Jeff
…On Tue, Nov 12, 2024 at 5:59 PM Matt Hartley ***@***.***> wrote:
Have not forgotten about this, but it may be a bit before I can circle
back to this. Just updating I have not forgotten.
—
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEGDBZOU374ZLKS4RRXZKL2AKW6VAVCNFSM6AAAAABQIKVT76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZSGE3DOMJWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My WiFi controller is dead. I am fairly confident that this is so:
jeffs@frmwrk16:~/nbmdt$ ip --stats link show dev wlp1s0 3: wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000 link/ether fc:b0:de:18:10:61 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped missed mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 0 0 0 0 0 0 jeffs@frmwrk16:~/nbmdt$Framework customer suggested I run the WiFi diagnostic tool to see what happens. Why not? Nothing else I've tried has fixed or even identified the problem. So I ran it.
Integrated Wi-Fi Diagnostic Script
jeffs@frmwrk16:~/nbmdt$ bash Wifi-Diagnostic.sh
Integrated Wi-Fi Diagnostic Script
Starting Wi-Fi Diagnostics...
Performing ping test to 8.8.8.8...
ping: connect: Network is unreachable
No network detected. Exiting.
rfkill Status:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Final Recommendations
rfkill status explanation:
jeffs@frmwrk16:~/nbmdt$
The text was updated successfully, but these errors were encountered: