Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 43

Thread: Broadcom wireless initially worked, now balky

  1. #21
    Join Date
    Jan 2020
    Beans
    48

    Re: Broadcom wireless initially worked, now balky

    Quote Originally Posted by chili555 View Post
    Everything looks perfect until:Let's try to see where it fails.Please run and post the result of:
    Code:
    ping -c3 192.168.0.1
    ping -c3 8.8.8.8
    ping4 -c3 www.google.com
    I hope we see a clue in there!

    dave@ThinkPad-X131e:~$ ping -c3 192.168.0.1
    PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

    --- 192.168.0.1 ping statistics ---
    3 packets transmitted, 0 received, 100% packet loss, time 2033ms

    dave@ThinkPad-X131e:~$ ping -c3 8.8.8.8
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    From 192.168.0.31 icmp_seq=1 Destination Host Unreachable
    From 192.168.0.31 icmp_seq=2 Destination Host Unreachable
    From 192.168.0.31 icmp_seq=3 Destination Host Unreachable

    --- 8.8.8.8 ping statistics ---
    3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2051ms
    pipe 3
    dave@ThinkPad-X131e:~$ ping4 -c3 www.google.com
    ping4: www.google.com: Temporary failure in name resolution

  2. #22
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,022
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: Broadcom wireless initially worked, now balky

    Quote Originally Posted by davepool View Post
    dave@ThinkPad-X131e:~$ ping -c3 192.168.0.1
    PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

    --- 192.168.0.1 ping statistics ---
    3 packets transmitted, 0 received, 100% packet loss, time 2033ms

    dave@ThinkPad-X131e:~$ ping -c3 8.8.8.8
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    From 192.168.0.31 icmp_seq=1 Destination Host Unreachable
    From 192.168.0.31 icmp_seq=2 Destination Host Unreachable
    From 192.168.0.31 icmp_seq=3 Destination Host Unreachable

    --- 8.8.8.8 ping statistics ---
    3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2051ms
    pipe 3
    dave@ThinkPad-X131e:~$ ping4 -c3 www.google.com
    ping4: www.google.com: Temporary failure in name resolution
    If you can't even ping the gateway (router) at 192.168.0.1, that suggests that you aren't actually connected. What does this report?
    Code:
    iwconfig
    ip addr show wlp2s0b1
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  3. #23
    Join Date
    Jan 2020
    Beans
    48

    Re: Broadcom wireless initially worked, now balky

    Quote Originally Posted by chili555 View Post
    If you can't even ping the gateway (router) at 192.168.0.1, that suggests that you aren't actually connected. What does this report?
    Code:
    iwconfig
    ip addr show wlp2s0b1
    And yet, every time I start up or re-start, the pop-up notification and then the icon in the tray all report that I'm connected. In fact, right now it shows active when I hover the cursor over it and then opening Connection information it's got all the info, including 65 Mb/s as the speed.

    dave@ThinkPad-X131e:~$ iwconfig
    enp3s0 no wireless extensions.

    wlp2s0b1 IEEE 802.11 ESSID:"NETGEAR55"
    Mode:Managed Frequency:2.412 GHz Access Point: 14:59:C0:84:E3:B3
    Bit Rate=65 Mb/s Tx-Power=19 dBm
    Retry short limit:7 RTS thrff Fragment thrff
    Power Managementff
    Link Quality=70/70 Signal level=-34 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:197 Invalid misc:9 Missed beacon:0

    lo no wireless extensions.
    dave@ThinkPad-X131e:~$ ip addr show wlp2s0b1
    3: wlp2s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 2c:d0:5a:01:5d:aa brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.31/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0b1
    valid_lft 86231sec preferred_lft 86231sec
    inet6 fe80::6129:96a1:f772:1674/64 scope link noprefixroute
    valid_lft forever preferred_lft forever

  4. #24
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,022
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: Broadcom wireless initially worked, now balky

    [ 76.529526] [UFW BLOCK] IN=wlp2s0b1 OUT= MAC=2c:d0:5a:01:5d:aa:c8:1f:66:0c:0d:e5:08:00 SRC=192.168.0.19 DST=192.168.0.31 LEN=44 TOS=0x00 PREC=0x00 TTL=128 ID=5575 PROTO=UDP SPT=50135 DPT=8612 LEN=24
    I notice a lot of messages in the log having to do with blocking by your firewall. Please try:
    Code:
    sudo ufw disable
    ping -c3 192.168.0.1
    sudo ufw enable
    Any change/improvement/miracles?

    Tx excessive retries:197
    Studying...
    Last edited by chili555; 3 Weeks Ago at 02:01 AM.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  5. #25
    Join Date
    Jan 2020
    Beans
    48

    Re: Broadcom wireless initially worked, now balky

    Quote Originally Posted by chili555 View Post
    I notice a lot of messages in the log having to do with blocking by your firewall. Please try:
    Code:
    sudo ufw disable
    ping -c3 192.168.0.1
    sudo ufw enable
    Any change/improvement/miracles?

    Studying...

    dave@ThinkPad-X131e:~$ sudo ufw disable
    [sudo] password for dave:
    Firewall stopped and disabled on system startup
    dave@ThinkPad-X131e:~$ ping -c3 192.168.0.1
    PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

    --- 192.168.0.1 ping statistics ---
    3 packets transmitted, 0 received, 100% packet loss, time 2055ms

    dave@ThinkPad-X131e:~$ sudo ufw enable
    Firewall is active and enabled on system startup

  6. #26
    Join Date
    Jan 2020
    Beans
    48

    Re: Broadcom wireless initially worked, now balky

    Separate thought: I'm reading that as many millions of laptops as there are around the world with Broadcom cards, some of them (not sure if it's specific models or just random production errors) are just beasts. The web is full of "as soon as I got rid of the Broadcom card it came with...." messages. Hard to miss 'em. I'm also seeing that an Intel card for this specific ThinkPad can be bought for $20 (and a buddy has told me he replaced a card once with a rather "generic" card that he got for $10...but I think he was lucky that it was compatible because I'm also told that some manufacturers have a very tight "whitelist" of wireless cards).

    All to say that I'm already prepared to find this is the only way out.

  7. #27
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,022
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: Broadcom wireless initially worked, now balky

    Quote Originally Posted by davepool View Post
    Separate thought: I'm reading that as many millions of laptops as there are around the world with Broadcom cards, some of them (not sure if it's specific models or just random production errors) are just beasts. The web is full of "as soon as I got rid of the Broadcom card it came with...." messages. Hard to miss 'em. I'm also seeing that an Intel card for this specific ThinkPad can be bought for $20 (and a buddy has told me he replaced a card once with a rather "generic" card that he got for $10...but I think he was lucky that it was compatible because I'm also told that some manufacturers have a very tight "whitelist" of wireless cards).

    All to say that I'm already prepared to find this is the only way out.
    I am not at all convinced that the wireless card itself is the fault here. You have the curious circumstance of appearing, by all accounts, to be connected and yet you cannot ping any site including the gateway (router) that you are apparently connected to.

    Will you please click the Network Manager icon and turn on Airplane Mode so as to disable, temporarily, the wireless. Then connect the ethernet and try again:
    Code:
    ping -c3 192.168.0.1
    ping -c3 8.8.8.8
    ping4 -c3 www.google.com
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  8. #28
    Join Date
    Jan 2020
    Beans
    48

    Re: Broadcom wireless initially worked, now balky

    Quote Originally Posted by chili555 View Post
    I am not at all convinced that the wireless card itself is the fault here. You have the curious circumstance of appearing, by all accounts, to be connected and yet you cannot ping any site including the gateway (router) that you are apparently connected to.

    Will you please click the Network Manager icon and turn on Airplane Mode so as to disable, temporarily, the wireless. Then connect the ethernet and try again:
    Code:
    ping -c3 192.168.0.1
    ping -c3 8.8.8.8
    ping4 -c3 www.google.com
    For whatever reason, the ethernet connection keeps cycling from Connecting 1000 Mb/s to Disconnected. When I try to use the terminal with Airplane Mode engaged, I get what you see in the first lines below. When I turned Airplane Mode off (which I know is not what you asked...but I wanted to get you *something* in the way of results), everything after those first two lines is what came back:

    dave@ThinkPad-X131e:~$ ping -c3 192.168.0.1
    ping: connect: Network is unreachable


    dave@ThinkPad-X131e:~$ ping -c3 192.168.0.1
    PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=680 ms
    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=5.94 ms

    --- 192.168.0.1 ping statistics ---
    3 packets transmitted, 2 received, 33.3333% packet loss, time 2028ms
    rtt min/avg/max/mdev = 5.944/343.212/680.480/337.268 ms
    dave@ThinkPad-X131e:~$ ping -c3 8.8.8.8
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=120 ms
    64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=65.8 ms
    64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=35.9 ms

    --- 8.8.8.8 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 35.900/74.029/120.423/34.997 ms
    dave@ThinkPad-X131e:~$ ping4 -c3 www.google.com
    PING www.google.com (172.217.11.164) 56(84) bytes of data.
    64 bytes from lax28s15-in-f4.1e100.net (172.217.11.164): icmp_seq=3 ttl=56 time=162 ms

    --- www.google.com ping statistics ---
    3 packets transmitted, 1 received, 66.6667% packet loss, time 2016ms
    rtt min/avg/max/mdev = 161.959/161.959/161.959/0.000 ms

  9. #29
    Join Date
    Jan 2020
    Beans
    48

    Re: Broadcom wireless initially worked, now balky

    Quote Originally Posted by chili555 View Post
    I am not at all convinced that the wireless card itself is the fault here. You have the curious circumstance of appearing, by all accounts, to be connected and yet you cannot ping any site including the gateway (router) that you are apparently connected to.

    Will you please click the Network Manager icon and turn on Airplane Mode so as to disable, temporarily, the wireless. Then connect the ethernet and try again:
    Code:
    ping -c3 192.168.0.1
    ping -c3 8.8.8.8
    ping4 -c3 www.google.com
    Wait! Success! I got the ethernet to work. So, with the wifi off because it was in Airplane Mode, here are the results from the same commands:

    dave@ThinkPad-X131e:~$ ping -c3 192.168.0.1
    PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.58 ms
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.18 ms
    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.18 ms

    --- 192.168.0.1 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2004ms
    rtt min/avg/max/mdev = 1.176/1.646/2.583/0.662 ms
    dave@ThinkPad-X131e:~$ ping -c3 8.8.8.8
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=31.9 ms
    64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=28.6 ms
    64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=28.8 ms

    --- 8.8.8.8 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 28.597/29.750/31.894/1.517 ms
    dave@ThinkPad-X131e:~$ ping4 -c3 www.google.com
    PING www.google.com (172.217.14.100) 56(84) bytes of data.
    64 bytes from lax31s01-in-f4.1e100.net (172.217.14.100): icmp_seq=1 ttl=56 time=27.9 ms
    64 bytes from lax31s01-in-f4.1e100.net (172.217.14.100): icmp_seq=2 ttl=56 time=30.1 ms
    64 bytes from lax31s01-in-f4.1e100.net (172.217.14.100): icmp_seq=3 ttl=56 time=28.7 ms

    --- www.google.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2004ms
    rtt min/avg/max/mdev = 27.934/28.923/30.132/0.910 ms

  10. #30
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,022
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: Broadcom wireless initially worked, now balky

    For whatever reason, the ethernet connection keeps cycling from Connecting 1000 Mb/s to Disconnected.
    3 packets transmitted, 2 received, 33.3333% packet loss, time 2028ms
    3 packets transmitted, 1 received, 66.6667% packet loss, time 2016ms
    Wait! Success! I got the ethernet to work.
    Isn't it at all suspicious that, at times, BOTH the wireless AND the ethernet are, as you say, balky?? Are any other devices connected to the same network "balky" at tiimes? Could this be an issue at the router?

    The fact that the ethernet correctly pings the router and www.google.com seems to rule out any DNS configuration issue in your Ubuntu computer.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

Page 3 of 5 FirstFirst 12345 LastLast

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
  •