Hello again Readers, One fact I omitted from the details below which seems significant: when the Telstra modem was rebooted, another computer that connects to it by wireless, a Macbook Air, connected without incident and worked as normal. This led me to think the modem was in order and made me reluctant to reset it in any way.
ben -- [email protected] On Tue, Feb 16, 2021, at 6:39 PM, Ben Nisenbaum via luv-main wrote: > Hello Readers, > > The power went off and so the router, a Telstra Smart Modem, went down. > I closed off the computer which was on a UPS so it avoided a crash. On > the return of power some minutes later, when I rebooted the compuer, > the wifi wouldn't connect to the modem. This was the case for two > computers with the same os and the same wireless dongle. > > The computers are running Debian bullseye and were up to date. > The wireless dongle is TP-Link TL-WN821N v5/v6 [RTL8192EU]. > > These are the things I tried to get it going but failed: > > - Rebooted the NBN device, the modem and the computer, several times. > The computer booted last each time. > - rmmod && modprobe the driver 8192eu. > - Recompiled the driver from source code which I had downloaded just a > few days before, and modprobed it. > - Redid the whole configuration by hand running: > # wpa_passphrase TelstraModem password > > /etc/wpa_supplicant/wpa_supplicant.conf > # wpa_supplicant -B -c /etc/wpa_supplicant/wpa_supplicant.conf -i > wifiname > # dhclient wifiname > > These commands worked when I originally set up the wifi months ago. > Later I put the details into /etc/network/interfaces and wifi started > automatically without any problems. Today I commented out the > interfaces file to redo the configuration manually and found the the > wifi broke down at the command: > # dhclient wifiname > It just hung there without getting an IP address. > > I haven't found anything more online to try. > > After reconnecting a computer to the router by ethernet I was able to > get back online. I opened the Telstra router in my firefox browser and > could see the different devices it was connected to. I could not see > any way of making it forget any devices. I thought perhaps it needed to > do that so that it could accept a new signal from the dongle. There was > a "system reset" tag under the "Management" page, but I was loath to > try that not knowing what would be reset and what state it would get me > into. There is also a "reset" hole on the physical router itself which > resets it to factory reset, but I was unsure about using that too not > knowing whether that would kill my connection altogether. And I don't > know if it would resolve my issue. > > Here is the log of failure > > [root@owl ~]# journalctl _SYSTEMD_UNIT=networking.service > -- Journal begins at Wed 2021-02-10 22:42:15 AEDT, ends at Tue > 2021-02-16 18:32:36 AEDT. -- > Feb 11 21:49:10 owl ifdown[8796]: ifdown: waiting for lock on > /run/network/ifstate.wlxd4519c547 > -- Boot 60a530f933d34011ad378c6f347fe6e1 -- > Feb 12 23:24:22 owl ifdown[5919]: ifdown: waiting for lock on > /run/network/ifstate.wlxd4519c547 > -- Boot 49e73170cc1b41a0bd746030f0049eba -- > Feb 13 22:44:38 owl ifdown[13352]: ifdown: waiting for lock on > /run/network/ifstate.wlxd4519c547 > -- Boot bd2375d5169f4f88aabdcf2c8d869b24 -- > Feb 14 22:24:16 owl ifdown[18676]: ifdown: waiting for lock on > /run/network/ifstate.wlxd4519c547 > -- Boot 88237d37e1904015b665aaac5e26f417 -- > Feb 15 22:50:55 owl ifdown[12141]: ifdown: waiting for lock on > /run/network/ifstate.wlxd4519c547 > -- Boot c2e5e72ae20a480a89dcd24ee563c32f -- > Feb 16 11:18:08 owl ifdown[763]: ifdown: waiting for lock on > /run/network/ifstate.wlxd4519c547 > -- Boot fbd608f05ac54d1faa42e3fd05d0b0d3 -- > Feb 16 12:12:31 owl dhclient[861]: Killed old client process > Feb 16 12:12:31 owl ifdown[861]: Killed old client process > Feb 16 12:12:32 owl dhclient[861]: Internet Systems Consortium DHCP > Client 4.4.1 > Feb 16 12:12:32 owl ifdown[861]: Internet Systems Consortium DHCP > Client 4.4.1 > Feb 16 12:12:32 owl ifdown[861]: Copyright 2004-2018 Internet Systems > Consortium. > Feb 16 12:12:32 owl ifdown[861]: All rights reserved. > Feb 16 12:12:32 owl ifdown[861]: For info, please visit > https://www.isc.org/software/dhcp/ > Feb 16 12:12:32 owl dhclient[861]: Copyright 2004-2018 Internet Systems > Consortium. > Feb 16 12:12:32 owl dhclient[861]: All rights reserved. > Feb 16 12:12:32 owl dhclient[861]: For info, please visit > https://www.isc.org/software/dhcp/ > Feb 16 12:12:32 owl dhclient[861]: > Feb 16 12:12:33 owl dhclient[861]: Listening on > LPF/wlxd4519c547/d0:37:45:19:c5:47 > Feb 16 12:12:33 owl ifdown[861]: Listening on > LPF/wlxd4519c547/d0:37:45:19:c5:47 > Feb 16 12:12:33 owl ifdown[861]: Sending on > LPF/wlxd4519c547/d0:37:45:19:c5:47 > Feb 16 12:12:33 owl ifdown[861]: Sending on Socket/fallback > Feb 16 12:12:33 owl dhclient[861]: Sending on > LPF/wlxd4519c547/d0:37:45:19:c5:47 > Feb 16 12:12:33 owl dhclient[861]: Sending on Socket/fallback > Feb 16 12:12:33 owl dhclient[861]: DHCPRELEASE of 192.168.0.15 on > wlxd4519c547 to 192.168.0.1 port 67 > Feb 16 12:12:33 owl ifdown[861]: DHCPRELEASE of 192.168.0.15 on > wlxd4519c547 to 192.168.0.1 port 67 > Feb 16 12:12:33 owl ifdown[861]: send_packet: Network is unreachable > Feb 16 12:12:33 owl ifdown[861]: send_packet: please consult README > file regarding broadcast address. > Feb 16 12:12:33 owl ifdown[861]: dhclient.c:2879: Failed to send 300 > byte long packet over fallback interface. > Feb 16 12:12:33 owl dhclient[861]: send_packet: Network is unreachable > Feb 16 12:12:33 owl dhclient[861]: send_packet: please consult README > file regarding broadcast address. > Feb 16 12:12:33 owl dhclient[861]: dhclient.c:2879: Failed to send 300 > byte long packet over fallback interface. > [root@owl ~]# > > > I would be very grateful for some suggestions or information on this issue. > > Thanks > > ben > > > > > > > > > > -- > > [email protected] > _______________________________________________ > luv-main mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ luv-main mailing list -- [email protected] To unsubscribe send an email to [email protected]
