After running said command, the terminal outputs this:kedaha wrote:OK, as root run this:Code: Select all
# dhclient
Code: Select all
RTNETLINK answers: File exists
After running said command, the terminal outputs this:kedaha wrote:OK, as root run this:Code: Select all
# dhclient
Code: Select all
RTNETLINK answers: File exists
Code: Select all
iwlist scan
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
The output readskedaha wrote:How about:Code: Select all
iwlist scan
Code: Select all
bash: iwlist: command not found
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
I get the same error when typing iwconfig, and I've installed connman but can't seem to access it from the terminal.kedaha wrote:Assuming you've already read wiki.debian.org/WiFi/HowToUse#Command_Line
No, you're right and I apologise, instead of reading and trying to take things in I'm just taking what I'm being told and trying to do it in hopes of an easy fix and that's stupid and unfair of me. For now I'll stick to the Wiki and read through it in regards to any problems I have. Thank you for whatever help you did give me, and the same goes to everyone else who gave me advice and helped me out. I appreciate it more than I may make it seem. I'm going to just use the Wiki for advice from now on.Lysander wrote:OP, you are not learning anything. You are now only looking for quick fixes. It's the equivalent of moving to another country and repeating stock phrases to the locals rather than learning the language from base. In addition to that, the gfx card-related 'fix' that you found after reading one of the links I posted was very easy to find.
You're turning into a help vampire. Get off the forums, read the Debian Wiki [or alternately, leave the house]. I'm out.
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.
No.Mephistopheles wrote:I think the reason it classes it as an Ethernet connection is because I'm connected to the wifi booster via an ethernet cable, but the connection is still wireless.
AdrianTM wrote:There's no hacker in my grandma...
The output of "ip a" is as follows:dilberts_left_nut wrote:No.Mephistopheles wrote:I think the reason it classes it as an Ethernet connection is because I'm connected to the wifi booster via an ethernet cable, but the connection is still wireless.
It is ethernet.
Post output of 'ip a'
Code: Select all
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 40:8d:5c:e1:fe:77 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.193/24 brd 192.168.1.255 scope global dynamic enp3s0
valid_lft 85281sec preferred_lft 85281sec
inet6 fe80::428d:5cff:fee1:fe77/64 scope link
valid_lft forever preferred_lft forever