Results 1 to 5 of 5

Thread: We need to talk about the wireless troubleshooting script

  1. #1
    currentshaft is offline Oops! My Coffee Cup is empty.
    Join Date
    May 2024
    Beans
    Hidden!

    We need to talk about the wireless troubleshooting script

    i
    Last edited by currentshaft; 4 Weeks Ago at 02:02 AM.

  2. #2
    Join Date
    May 2014
    Location
    /home
    Beans
    11,162
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: We need to talk about the wireless troubleshooting script

    I guess I can get rid of that info. This is because of changes in netplan and Ubuntu 24.04, once tested I can push my changes. When I use the script normally, I see permissions errors for netplan results in the script and I wonder if some people are running as root
    Last edited by jeremy31; August 26th, 2024 at 05:03 PM.

  3. #3
    currentshaft is offline Oops! My Coffee Cup is empty.
    Join Date
    May 2024
    Beans
    Hidden!

    Re: We need to talk about the wireless troubleshooting script

    .
    Last edited by currentshaft; 4 Weeks Ago at 03:52 PM.

  4. #4
    Join Date
    May 2014
    Location
    /home
    Beans
    11,162
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: We need to talk about the wireless troubleshooting script

    If you are running 24.04, try it now
    Code:
    wget -N -t 5 -T 10 https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info && \
    chmod +x wireless-info
    sudo ./wireless-info
    Then look at the results

    The script wasn't meant for users to run with sudo as sudo is in the script itself only when needed. When run normally the script asks for the password but it isn't used for the netplan parts

  5. #5
    currentshaft is offline Oops! My Coffee Cup is empty.
    Join Date
    May 2024
    Beans
    Hidden!

    Re: We need to talk about the wireless troubleshooting script

    I ran the script: it provided no output and then asked for my sudo password without an explanation. I Control-C'd a few of those prompts and it still produced a result. We should indicate why a password is being requested.

    I'm not sure exactly how the SSID names and especially a list of all nearby networks helps troubleshooting, but if possible we should redact them: they are a big privacy risk.

    The rest looks clean. Thanks for working on this.
    Last edited by Irihapeti; 4 Weeks Ago at 01:48 PM. Reason: Restored original content

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •