Broken my VPN and Tor (and my connection)
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Here's what happened: I was trying to setup KVM. So I made manual changes regarding my network interfaces.
Somehow, KVM worked.
I don't remember why, but I had to restart my machine.
I then noticed that my bridge was finally up. I also noticed a much slower reboot because of some network configuration message.
But then, I couldn't launch bitmask anymore, even through the terminal.
Actually, my whole connection was down.
So I commented out the changes I've made regarding network interfaces, and made a reboot.
Now, my connection is up, but still no bitmask, even after closing the other instances with htop.
So I decided to try Tor, since I've never really used it. It doesn't work either.
Could not connect to Tor control port.
Beside trying to reinstall both, I have no idea what happened.
Help please !
https://trac.torproject.org/projects/tor/ticket/11776
I think I restarted my machine because Bitmask started, but wasn't able to get a connection.
added to the above, it really seems to be a network issue.
EDIT:
Nevermind, I found a way: instead of leaving the interface modifications commented, I competely erased them to get back to the original file.
For some reason, the inetstat file reverted back to its original state without my intervention. After a reboot, all went well.
I still need to figure out that KVM thing. I'll try without a bridge first.
Anyway, this is SOLVED.
Looks like I really have broken something.
My wifi green light is off, no matter if the ardware switch is on or off. and the FN key+F5 does work, but has no effect on hardware wifi.
I tried
rmmod -f ath9k
sudo rfkill unblock all
sudo modprobe ath9k
and since it gave me a FATAL: something like "no athk9 found"
sudo modprobe ath9k nohwcrypt
which gave me
modprobe: ERROR: could not insert 'ath9k': Invalid argument
And I can't do rfkill list all anymore (maybe because it's not listed there anymore).
From what I understand, I erased the ath9k driver, unblocked everything and then tried to reinstall it in the kernel. This is where it failed.
Bottom line: still no wifi.
Some additional data:
modinfo ath9k
filename: /lib/modules/3.13.0-66-generic/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko
license: Dual BSD/GPL
description: Support for Atheros 802.11n wireless LAN cards.
author: Atheros Communications
srcversion: E7A57F092F500DEC330BD56
alias: platform:qca955x_wmac
alias: platform:ar934x_wmac
alias: platform:ar933x_wmac
alias: platform:ath9k
alias: pci:v0000168Cd00000036sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000036sv0000185Fsd00003027bc*sc*i*
alias: pci:v0000168Cd00000036sv00001B9Asd00002810bc*sc*i*
alias: pci:v0000168Cd00000036sv0000144Fsd00007202bc*sc*i*
alias: pci:v0000168Cd00000036sv00001A3Bsd00002130bc*sc*i*
alias: pci:v0000168Cd00000036sv000011ADsd00000612bc*sc*i*
alias: pci:v0000168Cd00000036sv000011ADsd00000652bc*sc*i*
alias: pci:v0000168Cd00000036sv000011ADsd00000642bc*sc*i*
alias: pci:v0000168Cd00000036sv0000168Csd0000302Cbc*sc*i*
alias: pci:v0000168Cd00000036sv0000168Csd00003027bc*sc*i*
alias: pci:v0000168Cd00000036sv0000144Dsd0000411Ebc*sc*i*
alias: pci:v0000168Cd00000036sv0000144Dsd0000411Dbc*sc*i*
alias: pci:v0000168Cd00000036sv0000144Dsd0000411Cbc*sc*i*
alias: pci:v0000168Cd00000036sv0000144Dsd0000411Bbc*sc*i*
alias: pci:v0000168Cd00000036sv0000144Dsd0000411Abc*sc*i*
alias: pci:v0000168Cd00000036sv00001028sd0000020Ebc*sc*i*
alias: pci:v0000168Cd00000036sv0000103Csd0000217Fbc*sc*i*
alias: pci:v0000168Cd00000036sv0000103Csd000018E3bc*sc*i*
alias: pci:v0000168Cd00000036sv000017AAsd00003026bc*sc*i*
alias: pci:v0000168Cd00000036sv00001A3Bsd0000213Abc*sc*i*
alias: pci:v0000168Cd00000036sv000011ADsd00000662bc*sc*i*
alias: pci:v0000168Cd00000036sv000011ADsd00000672bc*sc*i*
alias: pci:v0000168Cd00000036sv000011ADsd00000622bc*sc*i*
alias: pci:v0000168Cd00000036sv0000185Fsd00003028bc*sc*i*
alias: pci:v0000168Cd00000036sv0000105Bsd0000E069bc*sc*i*
alias: pci:v0000168Cd00000036sv0000168Csd0000302Bbc*sc*i*
alias: pci:v0000168Cd00000036sv0000168Csd00003026bc*sc*i*
alias: pci:v0000168Cd00000036sv0000168Csd00003025bc*sc*i*
alias: pci:v0000168Cd00000036sv00001B9Asd00002812bc*sc*i*
alias: pci:v0000168Cd00000036sv00001B9Asd00002811bc*sc*i*
alias: pci:v0000168Cd00000036sv000011ADsd00006671bc*sc*i*
alias: pci:v0000168Cd00000036sv000011ADsd00000632bc*sc*i*
alias: pci:v0000168Cd00000036sv0000185Fsd0000A119bc*sc*i*
alias: pci:v0000168Cd00000036sv0000105Bsd0000E068bc*sc*i*
alias: pci:v0000168Cd00000036sv00001A3Bsd00002176bc*sc*i*
alias: pci:v0000168Cd00000036sv0000168Csd00003028bc*sc*i*
alias: pci:v0000168Cd00000037sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000034sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000034sv000010CFsd00001783bc*sc*i*
alias: pci:v0000168Cd00000034sv000014CDsd00000064bc*sc*i*
alias: pci:v0000168Cd00000034sv000014CDsd00000063bc*sc*i*
alias: pci:v0000168Cd00000034sv0000103Csd00001864bc*sc*i*
alias: pci:v0000168Cd00000034sv000011ADsd00006641bc*sc*i*
alias: pci:v0000168Cd00000034sv000011ADsd00006631bc*sc*i*
alias: pci:v0000168Cd00000034sv00001043sd0000850Ebc*sc*i*
alias: pci:v0000168Cd00000034sv00001A3Bsd00002110bc*sc*i*
alias: pci:v0000168Cd00000034sv00001969sd00000091bc*sc*i*
alias: pci:v0000168Cd00000034sv000017AAsd00003214bc*sc*i*
alias: pci:v0000168Cd00000034sv0000168Csd00003117bc*sc*i*
alias: pci:v0000168Cd00000034sv000011ADsd00006661bc*sc*i*
alias: pci:v0000168Cd00000034sv00001A3Bsd00002116bc*sc*i*
alias: pci:v0000168Cd00000033sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000032sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000032sv00001043sd0000850Dbc*sc*i*
alias: pci:v0000168Cd00000032sv00001B9Asd00001C01bc*sc*i*
alias: pci:v0000168Cd00000032sv00001B9Asd00001C00bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00001F95bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00001195bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00001F86bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00001186bc*sc*i*
alias: pci:v0000168Cd00000032sv00001B9Asd00002001bc*sc*i*
alias: pci:v0000168Cd00000032sv00001B9Asd00002000bc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Fsd00007197bc*sc*i*
alias: pci:v0000168Cd00000032sv0000105Bsd0000E04Fbc*sc*i*
alias: pci:v0000168Cd00000032sv0000105Bsd0000E04Ebc*sc*i*
alias: pci:v0000168Cd00000032sv000011ADsd00006628bc*sc*i*
alias: pci:v0000168Cd00000032sv000011ADsd00006627bc*sc*i*
alias: pci:v0000168Cd00000032sv00001C56sd00004001bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00002100bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00002C97bc*sc*i*
alias: pci:v0000168Cd00000032sv000017AAsd00003219bc*sc*i*
alias: pci:v0000168Cd00000032sv000017AAsd00003218bc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Dsd0000C708bc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Dsd0000C680bc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Dsd0000C706bc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Dsd0000410Fbc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Dsd0000410Ebc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Dsd0000410Dbc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Dsd00004106bc*sc*i*
alias: pci:v0000168Cd00000032sv0000144Dsd00004105bc*sc*i*
alias: pci:v0000168Cd00000032sv0000185Fsd00003027bc*sc*i*
alias: pci:v0000168Cd00000032sv0000185Fsd00003119bc*sc*i*
alias: pci:v0000168Cd00000032sv0000168Csd00003122bc*sc*i*
alias: pci:v0000168Cd00000032sv0000168Csd00003119bc*sc*i*
alias: pci:v0000168Cd00000032sv0000105Bsd0000E075bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00002152bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd0000126Abc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00002126bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00001237bc*sc*i*
alias: pci:v0000168Cd00000032sv00001A3Bsd00002086bc*sc*i*
alias: pci:v0000168Cd00000030sv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Esv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Dsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Csv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Bsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Bsv00001A3Bsd00002C37bc*sc*i*
alias: pci:v0000168Cd0000002Asv000010CFsd00001536bc*sc*i*
alias: pci:v0000168Cd0000002Asv000010CFsd0000147Dbc*sc*i*
alias: pci:v0000168Cd0000002Asv000010CFsd0000147Cbc*sc*i*
alias: pci:v0000168Cd0000002Asv0000185Fsd0000309Dbc*sc*i*
alias: pci:v0000168Cd0000002Asv00001A32sd00000306bc*sc*i*
alias: pci:v0000168Cd0000002Asv000011ADsd00006642bc*sc*i*
alias: pci:v0000168Cd0000002Asv000011ADsd00006632bc*sc*i*
alias: pci:v0000168Cd0000002Asv0000105Bsd0000E01Fbc*sc*i*
alias: pci:v0000168Cd0000002Asv00001A3Bsd00001C71bc*sc*i*
alias: pci:v0000168Cd0000002Asv*sd*bc*sc*i*
alias: pci:v0000168Cd00000029sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000027sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000024sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000023sv*sd*bc*sc*i*
depends: ath9k_hw,mac80211,ath9k_common,cfg80211,ath
intree: Y
vermagic: 3.13.0-66-generic SMP mod_unload modversions
signer: Magrathea: Glacier signing key
sig_key: E9:1B:80:33:F2:93:82:1D:33:54:C8:C8:36:2B:2B:70:EA:87:B1:8F
sig_hashalgo: sha512
parm: debug:Debugging mask (uint)
parm: nohwcrypt:Disable hardware encryption (int)
parm: blink:Enable LED blink on activity (int)
parm: btcoex_enable:Enable wifi-BT coexistence (int)
parm: bt_ant_diversity:Enable WLAN/BT RX antenna diversity (int)
parm: ps_enable:Enable WLAN PowerSave (int)
and
lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Help much welcomed !
Tehnoetic time.
Aw man... Are you sure it's a hardware issue??
It worked fine until now. There was a bad contact with the switch button pnce (for a short while), but since I can't access it...
Since I just removed that thing from the kernel witout being able to put it back, is there zero chances for the hardware wifi to work again with a kernel replacement/upgrade?
Did you check the hardware switch (if any)? Some weeks ago, I thought my Wifi adapter had died. However it turned out I must have simply pressed the hardware switch by mistake (an Fn+F[:digit:] combination). Finding out that mistake was not that easy: the actual Fn+F[:digit:] combination is not the one indicated on the keyboard. I had to press the key next to the one indicated on the keyboard (bad mapping at the kernel-level I guess).
You mean software switch? Either way, I checked them both, and I tried every FN key combination, but no luck yet.
The ath9k module couldn't be found because you, just like I and almost
everyone else once did, had the assumption that the ‘rmmod’ command is a
safe way to unload modules inserted with the ‘modprobe’ command.
The thing is: The ‘--remove’ option of the ‘modprobe’ command resolves
module dependencies, just like a package manager. On the other hand, the
‘rmmod’ command simply removes the module, no matter if there are
dependent ones loaded.
Besides, I'm not sure, but perhaps the main reason for the ‘modprobe’
command to not be working when trying to reload the ath9k module is
because ‘rmmod’ seems to also remove the module from the "list of
loadable modules", but then again, I'm not sure as I can't find
references to back this statement up.
We could perhaps try inserting the module again by doing:
sudo insmod "/lib/modules/$(uname
--kernel-release)/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko"
And here my memory fails at me again...
After using ‘insmod’, load the module with ‘modprobe’, and after that,
it's recommended that you restart the system (I'm not the master of
module loading, but I think this is needed).
I tried it with the output of uname --kernel-release, and it seemed to go well.
After that, I tried sudo modprobe ath9k,
followed by a reboot.
Still not working though.
Just in case, I tried sudo modprobe ath9k nohwcrypt,
but It tells me that ath9k is an invalid argument.
Same thing with simply sudo modprobe ath9k.
So this is probably because the kernel is back in (I suppose the next step is to check the list of loadable modules).
So I could try to remove it again (this time with modprobe --remove), and sudo modprobe ath9k nohwcrypt.
EDIT:
modprobe --list doesn't work for now,
so I tried lsmod, which lists
ath9k_common (used by "0"), ath9k_hw (used by 1 ath9k_common)
and ath (which is used by the previous both).
modinfo ath9k seems identical to the previous report.
Also, in /etc/modules (modules to load at boot time), only lp and rtc are listed.
I manually put ath9K in etc/modules, but at boot I got ath9k: invalid for parameter 'nohwcrypt'.
Is it related to the fact that my drive is fully encrypted?
I have yet to try to remove ath9K again as mentioned above (with the nohwcrypt option) and put it back.
This might work.
EDIT_2:
I tried
sudo modprobe --remove ath9k
sudo rfkill unblock all
sudo modprobe ath9k nohwcrypt
but the last command (either with or without nohwcrypt) gives me
modprobe: ERROR: could not insert 'ath9k': Invalid argument
lsmod gives me the same output.
I should probably try to understand it more.
But one thing is for sure: no ath9k is listed.
Ok, I noticed something : after a reboot, the ath9k isn't listed on lsmod anymore.
Yet when I input the line you suggested ADFENO, it's back there (tough it's used by "0".
For example, the boot log tells me that ath9k doesn't recognize nohwcrypt as a parameter or something (that after trying sudo modprobe ath9k nohwcrypt).
dmesg /grep ath9k gives the output I get on startup (invalid parameter 'nohwcrypt').
I'll erase it and try all over again.
EDIT:
either with modprobe --remove or rmmod -f, I still get the same output :
ath9k: invalid for parameter nohwcrypt
Btw, I also noticed that the line you (ADFENO) suggested also puts back ath9k in lsmod listing.
Right now, 0: py0 Wireless lan is soft blocked: no
hard blocked : yes.
That and the dmesg out put still ther no matter what I do.
Still digging around the web, but still open to suggestions (Thanks for the previous ones to all).
http://www.emmolution.org/?p=253
This got me hardware blocked : no. Though the file I modified doesn't have the same name, but the option was already there (without =1).
Seems like I disabled hardware encryption. But still no signal.
Right now my situation is similar to this one : http://ubuntuforums.org/showthread.php?t=1728235
Nothing blocked in rfkill, recognized in iwconfig (but not in ifconfig) and lspci, and in lsmod I get an ath9k used by 0.
Feels like I'm getting closer to the goal, but I should study the lines I put in my command line interface more seriously.
Btw, dmesg /grep ath9k doesn't give any output anymore.
I just did some research on how to pass parameters for the modules, and
it seems that, according to ‘modinfo --parameters "ath9k"’, the
parameter ‘nohwcrypt’ MUST HAVE an integer value, and if we're talking
about something that is like a checkbox or a switch that has two modes,
that is, off and on, then we're probably talking about 0 and 1,
respectively.
So to say "I don't want hardware encryption", we must use:
sudo modprobe "ath9k" "nohwcrypt=1"
To tell you the truth, I don't know why they just forgot to document
"how far" goes their integer for the ‘nohwcrypt’ module parameter. That
said, it could be anything from infinite negative integers to infinite
positive integers, I just made a guess based on how most programs deal
with zeros and ones.
Yes, plus I wonder why it worked fine until now, and when I disable wireless encryption (didn't know it had a dedicated one), less problems are dsplayed, but still no connection.
I tried it, it got me the ath9k listed back in lsmod, but it's still hard blocked (when I play with hardware ad software switch, I can unblock it, even though the antenna icon and the connection are still off).
I tried an update through ethernet, no success.
I'm kinda stuck now. I even tried to download network-manager, but it's broken for some reason.
Unless you have ideas, I'm thinking of reinstalling my system, and see how it goes.
That hardware block is a mystery.
I still wonder if libreboot isn't involved :
On most systems, the /boot partition has to be left unencrypted while the others are encrypted. This is so that GRUB, and therefore the kernel, can be loaded and executed since the firmware can't open a LUKS volume. Not so with libreboot! Since GRUB is already included directly as a payload, even /boot can be encrypted. This protects /boot from tampering by someone with physical access to the system.
Logically, no, since when I turn the laptop on, I unencrypt everything. Unless I'm wrong, I can exclude that possibility.
If a re-install doesn't work, would it mean that my hardware wifi is dead (either the switch or the card) ?
With my limited knowledge, I suppose so. Then I'd go with an external card.
Any last minute input more than welcomed, I'll have to delay that reinstall for a day at least anyway.
If you boot off a live Trisquel media, does the wifi work?
Oh, true, thanks.
I just tried, and "enable wifi" was greyed out.
So in Network, I see that "airplane mode" is on.
I try disabling it and enablinthis and wireless on or off with the mouse pointer, and
at some point one combination gave me the wifi networks displayed!
But then I tried FN+F5, and it does enable airplane mode (which seems to be software block).
The hardware switch seemed to have no effect.
Yet now I can't get connected anymore.
I can toggle airplane mode on and off with the mouse, but not off with the FN key combo.
Much worse, I have no way to toggle "wireless" on anymore, no matter the combination of hardware and software switch.
But there was some life signs for a while, so that's encouraging!
Maybe I missed it, but I think that at no point the green wifi antenna icon lit up. But maybe the light died.
And even after rebooting, I still can't switch wireless on anymore, no matter what I do.
Also, if I disable airplane mode and get out of network settings and back in, that airplane mode is on.
EDIT:
rfkill still says that my wlan is hardblocked.
I tried to play with the hardware switch randomly.
More often than not, it's hardblock.
Sometimes, it's not anymore but when I check again, it's actually still hardblocked.
So even without getting very far in into the details, I'm pretty sure the driver is back there, encryption is off, software block is disabled, but hardware is not (the switch doesn't work, and as mentioned, months before I've had a small problem related to that.
So, provided I'm right, one possible thing I can try is to bypass the hardware switch. Or buy an external card.
Well, at least I learned something.
Something new happened:
I managed to turn the green wifi light on by bypassing hardware switch in software:
http://madwifi-project.org/wiki/UserDocs/MiniPCI
actually, it only made my wlan hardblocked to yes in rfkill.
But I need to put the antenna on with sudo ifconfig wlan0 up
at each boot. I'm sure there's a solution to this, but the problem remains:
the antenna is up,
the encryption is down,
but no actuall wifi connection yet.
Maybe all I need is to put the proper data as a network interface (up until now, wifi worked even if the only network interface I had is lo loopback).
What do you think?
EDIT:
After playing with the hardware switch to make sure it was disabled, it actually blocked the signal.
But I can't unblock it anymore.
What is left is putting tape on the right pin, like here:
https://richarddouglasdenton.wordpress.com/2011/05/11/how-to-bypass-a-laptop-wireless-switch/
http://www.allthingstechie.net/2014/10/bypass-laptop-wireless-hardware-radio.html
which will allow me to turn the antenna back on.
But I'll still have no signal there.
GOOD NEWS EVERYONE!
I'm nearly done with this:
I managed to keep the hardware block (rfkill) off, even though if it fails again, I'll resort to taping the proper pin on my wifi card.
So for now, it works.
I tried rebooting again with a Trisquel liveCD, and the wifi is recognized. I tried a connection, and it worked.
But, on my personal install, I have to put the antenna on with sudo ifconfig wlan0 up, and I have no connection.
My last task is filling those gaps.
I'll check the network interface on the liveCD and compare it to mine.
Again, any help welcomed, and thanks for your previous interventions people!
EDIT:
My netinstall is a bit different:
in etc/network/interfaces, I had to add an eth0 interface for my cable connection to be recognized, and it doesn't work if unplugged and plugged again until the next reboot.
The liveCD has none of that, so the truth must be elsewhere.
in etc/modprobe.d/ I have in the net install an additional file (something like wifi-exception or something) with options ath9k nohwcrypt inside (to which I had to add =0). It's not there in the LiveCD.
Where's the magic happening? I mean where should I look to put the connection on automatically, and maybe to put that encryption back on?
It seems the network stuff is dealt with in network-manager in the liveCD.
But it doesn't explain why I could connect in wifi before since I have no sort of network-manager I'm aware of.
I'm trying some manual configuration, but no success yet.
I've put in
allow-hotplug wlan0
iface wlan0 inet dhcp
wireless-essid myNetworkName
wireless-key myKey
sudo iwlist scan finds networks.
My wifi is supposedly on. It shows up everywhere (ifconfig etc),
but in iwconfig, essid is found, but Access Point says non-associated.
Well at least my wifi antenna icon is automatically on now.
But still no connection. Yet.
I have wifi now.
Thankfully, I didn't reinstall a thing.
I just modified the content of the interfaces file according to what the text install asks for (wpa-psk).
and something about avahi-daemon, which I told not to start at boot anymore (wlan0 avahi appeared on ifconfig).
Now,
The problem is that the nohwcrypt option has to be on 1, and I can't find info on it.
(there are suggestions about compiling the driver and doing that modprobe thing once again, which I might try).
Also, now when I plug an external hard drive, or when I launch bitmask, I'm prompted for my pass phrase. Never happend before this incident. No big deal, but I want to know how this happened.
That's actually a good question: what the hell happened ??
1) Initially, I modified the interfaces file according to the KVM tutorial, which f***ed my connection up.
2) So I removed and put back the ath9K driver,
3) and for some reason I was forced to modify the nohwcrypt option.
4) And I had to bypass my hardware wifi switch which is f***ing unreliable.
5) Never had to put my wifi info in the interfaces file beyond the initial install, I had now to put it there. Why?
6) I had wlan0 avahi interface, which I needed to put down for the wifi to work.
The other problem is, I don't know
If I forgot something, it's somewhere up there, but I think I got the essentials.
If someone has answers to this, I'm interested.
(I love the WTF downvote, but anyway, that's not why I'm posting) I didn't try it since I've chosen a paid solution, but if someone still has an issue with Bitmask like that, try erasing your config files, it might make it work (or not, but still worth a try, since a reinstall keeps your .config folder).
- Vous devez vous identifier ou créer un compte pour écrire des commentaires