Well after some research, I learned that since Bullseye, Debian does not use older device names such as eth0, so I found mine with ip addr My computer's Ethernet port in the Asus 701 is listed as enp3s0 But it somehow got disabled, even though I used it for the installation of Debian. So I was able to enable it with nmclient enp3s0 But for some reason, I still cannot access the TP-link router. As mentioned, there is supposed to be a key on the device for network access, because it is putting out an SSID, but I should be able to log into it and use admin:admin to make it a bridge with my home router. I've reset it numerous times too. The net-tools seems to be what gave me more utilities in this project. I'm wondering if openwrt will work on this, but I don't have the model needed to get the correct firmware. Anyway, just thought I'd mention this here, especially about the change in device names. Glenn ----- Original Message ----- From: D.J.J. Ring, Jr. To: K0LNY Cc: [email protected] ; Jérémy Prego Sent: Friday, July 7, 2023 6:46 PM Subject: Re: ifconfig
As root user: Try "ipconfig -a" Or "/sbin config eth0* Rgds, David On Fri, Jul 7, 2023, 18:43 K0LNY <[email protected]> wrote: Yeah, after I did the question to the list, my web search revealed the same thing, so after installing that, it works. But I am still having trouble finding the wired TP-Link device plugged into the computer. I find all devices on the home router, that my Debian device is connected to wirelessly, but I can't seem to find the TP-link. It is plugged into the Debian machine via Ethernet. I've tried the 192.168.1.1 and 192.168.0.1. But all the tools don't show the device on the Ethernet port of this computer. Glenn Thanks. ----- Original Message ----- From: "Jérémy Prego" <[email protected]> To: <[email protected]> Sent: Friday, July 7, 2023 5:15 PM Subject: Re: ifconfig > hello, > > apt install net-tools > > Jerem > Le 07/07/2023 à 23:53, K0LNY a écrit : >> Anyone know why the ifconfig command does not work on my Debian 32 bit on >> my Asus? >> I've tried it as root and not as root, it just says >> command not found. >> Thanks. >
