[SOLVED]Lenovo T60 internet issue

Kernels & Hardware, configuring network, installing services

[SOLVED]Lenovo T60 internet issue

Postby ticojohn » 2020-03-02 14:18

Installed Debian 10 on the Lenovo T60 using the firmware netinst for i386. During install chose WIFI as the preferred internet connection. After installation was complete there were issues with getting a connection. I had to change the NetworkManager.conf from manage=false to manage=true. That confuses me a bit as on all my other installations I never had to change that parameter. Also, if the ethernet cable is connected the laptop can not connect to the internet via ethernet and the WIFI will disconnect every five seconds and then reconnect.

The WIFI seems to work fine, as long as the ethernet is not connected, and the owner of the computer does not plan to use the ethernet connection, but I am concerned that there is something not configured properly. If somebody has some suggestions I would appreciate the help. Please let me know what further information is needed. Thank you.
Last edited by ticojohn on 2020-03-03 11:51, edited 1 time in total.
I'm not irrational, I'm just quantum probabilistic.
User avatar
ticojohn
 
Posts: 841
Joined: 2009-08-29 18:10
Location: Costa Rica

Re: Lenovo T60 internet issue

Postby Hallvor » 2020-03-02 14:58

Anything in the logs?
Lenovo ThinkPad T440S, Intel Core i7-4600U CPU @ 2.10GHz, 8 GB RAM, 256 GB SSD, Debian Buster (KDE)
Lenovo ThinkPad X240, Intel Core i5-4300U CPU @ 2.90GHz, 8 GB RAM, 120 GB SSD, Debian Buster (KDE)
User avatar
Hallvor
 
Posts: 1061
Joined: 2009-04-16 18:35
Location: Norway

Re: Lenovo T60 internet issue

Postby ticojohn » 2020-03-02 19:05

Hallvor wrote:Anything in the logs?

Good question. The only error I see in journalctl related to NetworkManager that might be of interest is the it failed to initialize SAP driver. I have no idea what that is. However I did notice something different in /etc/network/if-up,d . There is a fil. e, avahi-autoipd, that does not exist in any other of my installations. That is all I see with the ethernet disconnected. I then plugged in the ethernet cable and there are some interesting entries in journalctl. Not sure how much you want to see, but I am posting everything from the time the ethernet was plugged in. Not sure why it is tryin to connect as ipv6 as I have only ipv4. And by the way, getting stuff from laptop to my computer isa pain. LOL

Code: Select all
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.1957] device (ens2): carrier: link connected
Mar 02 13:26:24 debian kernel: e1000e: ens2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Mar 02 13:26:24 debian kernel: IPv6: ADDRCONF(NETDEV_CHANGE): ens2: link becomes ready
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.2017] device (ens2): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.2050] policy: auto-activating connection 'Wired connection 1' (ec6d8c47-1b2a-3e79-99e0-823c09435595)
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.2069] device (ens2): Activation: starting connection 'Wired connection 1' (ec6d8c47-1b2a-3e79-99e0-823c09435595)
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.2076] device (ens2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.2093] device (ens2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.2123] device (ens2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.2134] dhcp4 (ens2): activation: beginning transaction (timeout in 45 seconds)
Mar 02 13:26:24 debian NetworkManager[459]: <info>  [1583177184.2184] dhcp4 (ens2): dhclient started with pid 1076
Mar 02 13:26:24 debian avahi-daemon[454]: Joining mDNS multicast group on interface ens2.IPv6 with address fe80::194d:7b31:96cd:65fc.
Mar 02 13:26:24 debian avahi-daemon[454]: New relevant interface ens2.IPv6 for mDNS.
Mar 02 13:26:24 debian avahi-daemon[454]: Registering new address record for fe80::194d:7b31:96cd:65fc on ens2.*.
Mar 02 13:26:24 debian dhclient[1076]: DHCPDISCOVER on ens2 to 255.255.255.255 port 67 interval 8
Mar 02 13:26:32 debian dhclient[1076]: DHCPDISCOVER on ens2 to 255.255.255.255 port 67 interval 14
Mar 02 13:26:32 debian dhclient[1076]: DHCPOFFER of 10.222.184.206 from 10.222.184.1
Mar 02 13:26:32 debian dhclient[1076]: DHCPREQUEST for 10.222.184.206 on ens2 to 255.255.255.255 port 67
Mar 02 13:26:32 debian dhclient[1076]: DHCPACK of 10.222.184.206 from 10.222.184.1
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1439] dhcp4 (ens2):   address 10.222.184.206
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1440] dhcp4 (ens2):   plen 21 (255.255.248.0)
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1441] dhcp4 (ens2):   gateway 10.222.184.1
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1441] dhcp4 (ens2):   lease time 3600
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1442] dhcp4 (ens2):   hostname 'debian'
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1442] dhcp4 (ens2):   nameserver '200.91.75.5'
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1442] dhcp4 (ens2):   nameserver '200.91.75.6'
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1443] dhcp4 (ens2):   domain name 'minervanetworks.com'
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1443] dhcp4 (ens2): state changed unknown -> bound
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1465] device (ens2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 02 13:26:32 debian avahi-daemon[454]: Joining mDNS multicast group on interface ens2.IPv4 with address 10.222.184.206.
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1480] device (ens2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 02 13:26:32 debian avahi-daemon[454]: New relevant interface ens2.IPv4 for mDNS.
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1520] device (ens2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 02 13:26:32 debian avahi-daemon[454]: Registering new address record for 10.222.184.206 on ens2.IPv4.
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1565] policy: set 'Wired connection 1' (ens2) as default for IPv4 routing and DNS
Mar 02 13:26:32 debian NetworkManager[459]: <info>  [1583177192.1617] device (ens2): Activation: successful, device activated.
Mar 02 13:26:32 debian dbus-daemon[456]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=459 comm="/usr/sbin/NetworkManager --no-daemon ")
Mar 02 13:26:32 debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 02 13:26:32 debian dhclient[1076]: bound to 10.222.184.206 -- renewal in 1452 seconds.
Mar 02 13:26:32 debian dbus-daemon[456]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 02 13:26:32 debian systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 02 13:26:32 debian nm-dispatcher[1086]: req:1 'up' [ens2]: new request (1 scripts)
Mar 02 13:26:32 debian nm-dispatcher[1086]: req:1 'up' [ens2]: start running ordered scripts...
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7550] device (wls3): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7587] audit: op="device-disconnect" interface="wls3" ifindex=3 pid=904 uid=1000 result="success"
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7588] device (wls3): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
Mar 02 13:26:52 debian avahi-daemon[454]: Withdrawing address record for fe80::219:d2ff:fe45:d9e on wls3.
Mar 02 13:26:52 debian avahi-daemon[454]: Leaving mDNS multicast group on interface wls3.IPv6 with address fe80::219:d2ff:fe45:d9e.
Mar 02 13:26:52 debian avahi-daemon[454]: Interface wls3.IPv6 no longer relevant for mDNS.
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7938] dhcp4 (wls3): canceled DHCP transaction, DHCP client pid 589
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7939] dhcp4 (wls3): state changed bound -> done
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7968] dhcp6 (wls3): canceled DHCP transaction
Mar 02 13:26:52 debian avahi-daemon[454]: Withdrawing address record for 192.168.100.10 on wls3.
Mar 02 13:26:52 debian avahi-daemon[454]: Leaving mDNS multicast group on interface wls3.IPv4 with address 192.168.100.10.
Mar 02 13:26:52 debian avahi-daemon[454]: Interface wls3.IPv4 no longer relevant for mDNS.
Mar 02 13:26:52 debian kernel: wls3: deauthenticating from 84:a9:c4:1e:4c:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 02 13:26:52 debian wpa_supplicant[458]: wls3: CTRL-EVENT-DISCONNECTED bssid=84:a9:c4:1e:4c:c8 reason=3 locally_generated=1
Mar 02 13:26:52 debian wpa_supplicant[458]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/1
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.8419] device (wls3): set-hw-addr: set MAC address to CA:78:89:F2:77:64 (scanning)
Mar 02 13:26:52 debian kernel: IPv6: ADDRCONF(NETDEV_UP): wls3: link is not ready
Mar 02 13:26:52 debian nm-dispatcher[1086]: req:2 'down' [wls3]: new request (1 scripts)
Mar 02 13:26:52 debian NetworkManager[459]: <warn>  [1583177212.9480] sup-iface[0x11c0c88,wls3]: connection disconnected (reason -3)
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.9481] device (wls3): supplicant interface state: completed -> disconnected
Mar 02 13:26:52 debian wpa_supplicant[458]: wls3: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 02 13:27:00 debian nm-dispatcher[1086]: req:2 'down' [wls3]: start running ordered scripts...
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7145] device (ens2): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7165] manager: NetworkManager state is now DISCONNECTING
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7218] device (ens2): disconnecting for new activation request.
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7221] audit: op="connection-activate" uuid="ec6d8c47-1b2a-3e79-99e0-823c09435595" name="Wired connection 1" pid=904 uid=1000 result="success"
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7222] device (ens2): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Mar 02 13:27:03 debian avahi-daemon[454]: Withdrawing address record for fe80::194d:7b31:96cd:65fc on ens2.
Mar 02 13:27:03 debian avahi-daemon[454]: Leaving mDNS multicast group on interface ens2.IPv6 with address fe80::194d:7b31:96cd:65fc.
Mar 02 13:27:03 debian avahi-daemon[454]: Interface ens2.IPv6 no longer relevant for mDNS.
Mar 02 13:27:03 debian nm-dispatcher[1086]: req:3 'connectivity-change': new request (1 scripts)
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7565] dhcp4 (ens2): canceled DHCP transaction, DHCP client pid 1076
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7566] dhcp4 (ens2): state changed bound -> done
Mar 02 13:27:03 debian avahi-daemon[454]: Withdrawing address record for 10.222.184.206 on ens2.
Mar 02 13:27:03 debian avahi-daemon[454]: Leaving mDNS multicast group on interface ens2.IPv4 with address 10.222.184.206.
Mar 02 13:27:03 debian avahi-daemon[454]: Interface ens2.IPv4 no longer relevant for mDNS.
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7765] manager: NetworkManager state is now DISCONNECTED
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7824] device (ens2): Activation: starting connection 'Wired connection 1' (ec6d8c47-1b2a-3e79-99e0-823c09435595)
Mar 02 13:27:03 debian nm-dispatcher[1086]: req:4 'down' [ens2]: new request (1 scripts)
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7881] device (ens2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7939] manager: NetworkManager state is now CONNECTING
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7957] device (ens2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.7988] device (ens2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8012] dhcp4 (ens2): activation: beginning transaction (timeout in 45 seconds)
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8162] dhcp4 (ens2): dhclient started with pid 1148
Mar 02 13:27:03 debian avahi-daemon[454]: Joining mDNS multicast group on interface ens2.IPv6 with address fe80::194d:7b31:96cd:65fc.
Mar 02 13:27:03 debian avahi-daemon[454]: New relevant interface ens2.IPv6 for mDNS.
Mar 02 13:27:03 debian avahi-daemon[454]: Registering new address record for fe80::194d:7b31:96cd:65fc on ens2.*.
Mar 02 13:27:03 debian dhclient[1148]: DHCPREQUEST for 10.222.184.206 on ens2 to 255.255.255.255 port 67
Mar 02 13:27:03 debian dhclient[1148]: DHCPACK of 10.222.184.206 from 10.222.184.1
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8942] dhcp4 (ens2):   address 10.222.184.206
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8943] dhcp4 (ens2):   plen 21 (255.255.248.0)
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8943] dhcp4 (ens2):   gateway 10.222.184.1
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8944] dhcp4 (ens2):   lease time 10800
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8944] dhcp4 (ens2):   hostname 'debian'
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8945] dhcp4 (ens2):   nameserver '200.91.75.5'
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8945] dhcp4 (ens2):   nameserver '200.91.75.6'
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8945] dhcp4 (ens2):   domain name 'minervanetworks.com'
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.8946] dhcp4 (ens2): state changed unknown -> bound
Mar 02 13:27:03 debian avahi-daemon[454]: Joining mDNS multicast group on interface ens2.IPv4 with address 10.222.184.206.
Mar 02 13:27:03 debian avahi-daemon[454]: New relevant interface ens2.IPv4 for mDNS.
Mar 02 13:27:03 debian avahi-daemon[454]: Registering new address record for 10.222.184.206 on ens2.IPv4.
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.9028] device (ens2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.9087] device (ens2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.9117] device (ens2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.9157] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 02 13:27:03 debian dhclient[1148]: bound to 10.222.184.206 -- renewal in 5190 seconds.
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.9258] manager: NetworkManager state is now CONNECTED_SITE
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.9282] policy: set 'Wired connection 1' (ens2) as default for IPv4 routing and DNS
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.9342] device (ens2): Activation: successful, device activated.
Mar 02 13:27:03 debian NetworkManager[459]: <info>  [1583177223.9387] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 02 13:27:03 debian nm-dispatcher[1086]: req:5 'up' [ens2]: new request (1 scripts)
Mar 02 13:27:03 debian nm-dispatcher[1086]: req:6 'connectivity-change': new request (1 scripts)
Mar 02 13:27:14 debian nm-dispatcher[1086]: req:3 'connectivity-change': start running ordered scripts...
Mar 02 13:27:14 debian nm-dispatcher[1086]: req:4 'down' [ens2]: start running ordered scripts...
Mar 02 13:27:28 debian dbus-daemon[809]: [session uid=1000 pid=809] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.44' (uid=1000 pid=1183 comm="/usr/bin/gnome-terminal ")
Mar 02 13:27:28 debian systemd[785]: Starting GNOME Terminal Server...
Mar 02 13:27:28 debian dbus-daemon[809]: [session uid=1000 pid=809] Successfully activated service 'org.gnome.Terminal'
Mar 02 13:27:28 debian systemd[785]: Started GNOME Terminal Server.
Mar 02 13:27:28 debian nm-dispatcher[1086]: req:5 'up' [ens2]: start running ordered scripts...
Mar 02 13:27:40 debian su[1221]: (to root) mike on pts/0
Mar 02 13:27:40 debian su[1221]: pam_unix(su:session): session opened for user root by (uid=1000)
Mar 02 13:27:56 debian nm-dispatcher[1086]: req:6 'connectivity-change': start running ordered scripts...
Mar 02 13:28:06 debian systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Mar 02 13:30:01 debian CRON[1254]: pam_unix(cron:session): session opened for user root by (uid=0)
Mar 02 13:30:01 debian CRON[1255]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Mar 02 13:30:01 debian CRON[1254]: pam_unix(cron:session): session closed for user root
Mar 02 13:32:36 debian NetworkManager[459]: <info>  [1583177556.9994] device (wls3): set-hw-addr: set MAC address to 9A:8E:DC:24:19:2A (scanning)
Mar 02 13:32:37 debian kernel: IPv6: ADDRCONF(NETDEV_UP): wls3: link is not ready
Mar 02 13:32:37 debian NetworkManager[459]: <info>  [1583177557.0912] device (wls3): supplicant interface state: disconnected -> disabled
Mar 02 13:32:37 debian NetworkManager[459]: <info>  [1583177557.1191] device (wls3): supplicant interface state: disabled -> disconnected
Mar 02 13:33:21 debian systemd[1]: Started Run anacron jobs.
Mar 02 13:33:21 debian anacron[1259]: Anacron 2.3 started on 2020-03-02
Mar 02 13:33:21 debian anacron[1259]: Normal exit (0 jobs run)
Mar 02 13:33:21 debian systemd[1]: anacron.service: Succeeded.
Mar 02 13:33:51 debian kernel: usb 5-2: new high-speed USB device number 4 using ehci-pci
Mar 02 13:33:51 debian kernel: usb 5-2: New USB device found, idVendor=0951, idProduct=1665, bcdDevice= 2.00
Mar 02 13:33:51 debian kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 02 13:33:51 debian kernel: usb 5-2: Product: DataTraveler 2.0
Mar 02 13:33:51 debian kernel: usb 5-2: Manufacturer: Kingston
Mar 02 13:33:51 debian kernel: usb 5-2: SerialNumber: 001A4D5D52A81FB139587AA3
Mar 02 13:33:51 debian kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Mar 02 13:33:51 debian kernel: scsi host6: usb-storage 5-2:1.0
Mar 02 13:33:51 debian kernel: usbcore: registered new interface driver usb-storage
Mar 02 13:33:51 debian kernel: usbcore: registered new interface driver uas
Mar 02 13:33:52 debian kernel: scsi 6:0:0:0: Direct-Access     Kingston DataTraveler 2.0 0000 PQ: 0 ANSI: 4
Mar 02 13:33:52 debian kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
Mar 02 13:33:52 debian kernel: sd 6:0:0:0: [sdb] 30535744 512-byte logical blocks: (15.6 GB/14.6 GiB)
Mar 02 13:33:52 debian kernel: sd 6:0:0:0: [sdb] Write Protect is off
Mar 02 13:33:52 debian kernel: sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
Mar 02 13:33:52 debian kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Mar 02 13:33:52 debian kernel:  sdb: sdb1
Mar 02 13:33:52 debian kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
I'm not irrational, I'm just quantum probabilistic.
User avatar
ticojohn
 
Posts: 841
Joined: 2009-08-29 18:10
Location: Costa Rica

Re: Lenovo T60 internet issue

Postby ticojohn » 2020-03-02 20:03

After looking at the description for avahi-autoipd I am really wondering why that is installed on the T60. I have Buster installed on two drives on my desktop and on my Intel NUC. The desktop does not have WIFI but the NUC does. None of the installs have that file in /etc/network/if-up.d . I am wondering if that is what is causing the problem. Anybody have thoughts on this? I don't want to get carried away but am tempted to rename the file and see what happens. If I do rename it will it just come back on reboot or update?
I'm not irrational, I'm just quantum probabilistic.
User avatar
ticojohn
 
Posts: 841
Joined: 2009-08-29 18:10
Location: Costa Rica

Re: Lenovo T60 internet issue

Postby ticojohn » 2020-03-02 20:53

The more I read about avahi-autoipd the I wonder why it is installed on the T60. But just removing it me not be easy as I don't know how it gets started (is it just called by the avahi daemon?). Some of what I have read would indicate that it can cause problems with dhcp. It seems that is is intended for local ad-hoc networks.
I'm not irrational, I'm just quantum probabilistic.
User avatar
ticojohn
 
Posts: 841
Joined: 2009-08-29 18:10
Location: Costa Rica

Re: Lenovo T60 internet issue

Postby sunrat » 2020-03-02 22:09

You can disable avahi-daemon:
Code: Select all
systemctl stop avahi-daemon.service
systemctl disable avahi-daemon.service
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 3074
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Lenovo T60 internet issue

Postby ticojohn » 2020-03-02 22:53

sunrat wrote:You can disable avahi-daemon:
Code: Select all
systemctl stop avahi-daemon.service
systemctl disable avahi-daemon.service

Thanks. I just found something strange. With the ethernet selected I looked at resolv.conf it has something really weird. It is not getting the local nameserver 196.168.100.1
Code: Select all
# Generated by NetworkManager
search minervanetworks.com
nameserver 200.91.75.5
nameserver 200.91.75.5


I will disable avahi and see what happens
I'm not irrational, I'm just quantum probabilistic.
User avatar
ticojohn
 
Posts: 841
Joined: 2009-08-29 18:10
Location: Costa Rica

Re: Lenovo T60 internet issue

Postby sunrat » 2020-03-03 01:33

ticojohn wrote:Thanks. I just found something strange. With the ethernet selected I looked at resolv.conf it has something really weird. It is not getting the local nameserver 196.168.100.1
Code: Select all
# Generated by NetworkManager
search minervanetworks.com
nameserver 200.91.75.5
nameserver 200.91.75.5

That does look weird. Minerva Networks appears to be a pay tv provider from San Jose, California, whereas the IP resolves to an address in San José, Costa Rica (ICE.GO.CR). Maybe your ISP?
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 3074
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Lenovo T60 internet issue

Postby ticojohn » 2020-03-03 01:43

That does look weird. Minerva Networks appears to be a pay tv provider from San Jose, California, whereas the IP resolves to an address in San José, Costa Rica (ICE.GO.CR). Maybe your ISP?


If it as my ISP why wouldn't it do the same on my other computers? And it only happens when I connect the ethernet cable. Doesn't happen with the WIFI connection. I think it has to be somewhere in the software.
I'm not irrational, I'm just quantum probabilistic.
User avatar
ticojohn
 
Posts: 841
Joined: 2009-08-29 18:10
Location: Costa Rica

Re: Lenovo T60 internet issue

Postby Hallvor » 2020-03-03 08:12

Code: Select all
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7587] audit: op="device-disconnect" interface="wls3" ifindex=3 pid=904 uid=1000 result="success"
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7588] device (wls3): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
Mar 02 13:26:52 debian avahi-daemon[454]: Withdrawing address record for fe80::219:d2ff:fe45:d9e on wls3.
Mar 02 13:26:52 debian avahi-daemon[454]: Leaving mDNS multicast group on interface wls3.IPv6 with address fe80::219:d2ff:fe45:d9e.
Mar 02 13:26:52 debian avahi-daemon[454]: Interface wls3.IPv6 no longer relevant for mDNS.
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7938] dhcp4 (wls3): canceled DHCP transaction, DHCP client pid 589
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7939] dhcp4 (wls3): state changed bound -> done
Mar 02 13:26:52 debian NetworkManager[459]: <info>  [1583177212.7968] dhcp6 (wls3): canceled DHCP transaction
Mar 02 13:26:52 debian avahi-daemon[454]: Withdrawing address record for 192.168.100.10 on wls3.
Mar 02 13:26:52 debian avahi-daemon[454]: Leaving mDNS multicast group on interface wls3.IPv4 with address 192.168.100.10.
Mar 02 13:26:52 debian avahi-daemon[454]: Interface wls3.IPv4 no longer relevant for mDNS.
Mar 02 13:26:52 debian kernel: wls3: deauthenticating from 84:a9:c4:1e:4c:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 02 13:26:52 debian wpa_supplicant[458]: wls3: CTRL-EVENT-DISCONNECTED bssid=84:a9:c4:1e:4c:c8 reason=3 locally_generated=1


This can't be good.

Is this related?

https://bugs.launchpad.net/ubuntu/+sour ... ug/1586528
Lenovo ThinkPad T440S, Intel Core i7-4600U CPU @ 2.10GHz, 8 GB RAM, 256 GB SSD, Debian Buster (KDE)
Lenovo ThinkPad X240, Intel Core i5-4300U CPU @ 2.90GHz, 8 GB RAM, 120 GB SSD, Debian Buster (KDE)
User avatar
Hallvor
 
Posts: 1061
Joined: 2009-04-16 18:35
Location: Norway

Re: Lenovo T60 internet issue

Postby ticojohn » 2020-03-03 11:51

I am so DUMB ALL OVER. @sunrat was right in the ballpark. My modem/router is a fiber optic box giving me internet, tv, and telephone service. It has 4 router ports. Ports one(1) and two(2) are for internet, three(3) and four(4) are for IPTV. Without thinking about it I was plugging the laptop's ethernet cable in to port three(3). DUMB. Never thought about it until after sunrat's comment, and a good nights sleep.
@sunrat ..... That does look weird. Minerva Networks appears to be a pay tv provider from San Jose, California, whereas the IP resolves to an address in San José, Costa Rica (ICE.GO.CR). Maybe your ISP?

Checked it out this morning by plugging in to port two(2). Everything works fine. Thanks to all for the responses. You all put me on track to solving this issue.
I'm not irrational, I'm just quantum probabilistic.
User avatar
ticojohn
 
Posts: 841
Joined: 2009-08-29 18:10
Location: Costa Rica

Re: [SOLVED]Lenovo T60 internet issue

Postby sunrat » 2020-03-03 12:03

Haha, I love it when I find out I've been dumb, always learn something. I made a big booboo this week and deleted my backup email profile, only to find out later I had actually changed it to be the active one and lost about 18 months of emails locally. They're still on their servers though if I really need to find them.
I now have a restored profile where I thought it was supposed to be originally, and a fresh backup on another drive. Still need to schedule a regular rsync backup of that. I should read my profile message more often. :mrgreen:
Great that you got it sorted @ticojohn! 8)
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 3074
Joined: 2006-08-29 09:12
Location: Melbourne, Australia


Return to System configuration

Who is online

Users browsing this forum: No registered users and 1 guest

fashionable