Tag Info

New answers tagged

0

I managed to solve the problem by following these instructions on installing the free firmware manually: It now works and I am happy! :)


0

Have you tried adding the mesh interface to the br-lan bridge of OpenWRT? I can't give you an command for the CLI, but if I checkbox the mesh interface in the web gui to be part of the lan bridge, it works.


1

you're probably running some tool (e.g., network-manager) which wants to take ownership of your network interfaces and changes the settings. You essentially have two options: Uninstall that tool Configure that tool so it doesn't fiddle with your wireless settings. If it is indeed network-manager, and you want to use that for your wireless settings, then ...


0

After messing around for hours I managed to cook something decent up using zenity and some sudoers changes. I'll give a step by step how I did it all, in case someone else is caught in the ugly situation of being on a linux distro that only has obsolete wireless networking software (like wireless-tools) without any easy way to get a known GUI like wicd... ...


1

A quick search on packages.debian.org revealed the missing htc_7010.fw file in firmware-atheros package. There's some chance this firmware is free. IIRC some years ago the developers working on ath5k/ath9k drivers were able to reverse-engineer the proprietary firmware blob and forced Atheros to change their policy. Consult attached ...


0

Did it by using opposite idea - routed all except "direct" user to vpn instead instead of routing direct user to wlan interface. Because vpn network ips are static for f in /proc/sys/net/ipv4/conf/*/rp_filter; do echo 0 > $f; done echo 1 > /proc/sys/net/ipv4/route/flush iptables -t mangle -A OUTPUT -m owner ! --uid-owner direct2net -j MARK --set-mark ...


0

I had the same issue with a much more recent Fedora version (F20), and gnome-keyring version was not the culprit. Here is how I solved it : Right click on nm-applet. Click on "edit connections". Select the connection you're having issues with, then "edit". Go to the "Wi-Fi Security" tab and enter the wifi password. Save and exit.


0

You may have some stale files in /run/network that need to be deleted. This happens if you manually manipulate network interfaces so that they are not in the state that netctl expects. Alternatively, if your arch is more recent, this is all handled by systemd, so you may need to run systemctl stop netctl@XXX.service where XXX is your netctl profile name.


0

There is an easier way. If you can have the internet access via an ethernet cable you can just install the b43 firmware sudo apt-get install firmware-b43-installer and then load up the b43 module via sudo modprobe b43 Now you should have wireless working


0

It turns out I had failed to enable PCIE bus support for brcmfmac when compiling the Linux kernel. To do so, run make menuconfig and navigate: Device drivers - Network device support - Wireless LAN - PCIE bus interface support for FullMAC driver and enable PCIE bus support.


2

DISCLAIMER: I don't know how dependent this answer is on specific hardware. airmon-ng will enable a monitor interface without disrupting your wifi connection. Install aircrack-ng then run something like (I'm assuming wlan0 here): sudo airmon-ng start wlan0 Which will typically create a mon0 interface to the same physical card. You can also try to do it ...


2

Easiest way is to just reboot. The type of configuration change you've made does not persist across reboots.


0

I have manged to add the wireless network by using nmcli. I think it's something related to nmtui command. I found the help from here


0

From lsusb output, 148f:7601, it should be a MT7601U chip not MT7610U. Please node, Mediatek official site seem swap the link between them, but I'm not very sure about this. I believe some guys have made good progress on MT7601U, refer to https://github.com/kuba-moo/mt7601u You can see, that driver are committed to 4.2 kernel. I have a MT7610U usb ...


0

Is your networkmanager.conf correct? Thats the first thing that came to my mind... /etc/NetworkManager/NetworkManager.conf [ifupdown] managed=true


-2

This works perfectly for me YouTube: Connect USB Wireless Adapter to Kali Linux in Virtualbox


0

Are you opposed to swapping out the wifi cards? I have spent whole days trying to install broadcom drivers, but only succeeded once. If I understood at the time that I could spend like $15 and save myself many hours of frustration, I would have. I have had good luck with the atheros 9k-series, they've always worked out-of-the-box. If you decide to take ...


2

First, you can double-check your /etc/network/interfaces file against mine: auto lo iface lo inet loopback auto wlan2 iface wlan2 inet dhcp wpa-ssid <my essid> wpa-psk <my passphrase> auto eth0 iface eth0 inet static address <my static ip> network <my local network> netmask <my ...


0

it looks like disabled may not be universally supported. it's listed in the link below, but not in freeBSD's wpa_supplicant.conf(5). however.. there's a couple possible issues with your config: your catch-all is priority=-10, but not having a priority will default to priority=0. since 0 > -10, your first "bad" network will try to connect first. if ...


0

there's a large number of posts about the Broadcom BCM43142 having issues in kali, although i did dig up this bit: add all Kali repositories to /etc/apt/sources.list: deb http://http.kali.org/ /kali main contrib non-free deb http://http.kali.org/ /wheezy main contrib non-free deb http://http.kali.org/kali kali-dev main contrib non-free deb ...


0

Searching for "ERROR @wl_cfg80211_get_tx_power : error (-1)" gave me a whole ream of the same question, but it does seem to have a common thread... Kernel version 3.16-3.19 + Broadcom drivers: (sorry for the links, but its hard to follow the thought-thread without them) https://bugs.mageia.org/show_bug.cgi?id=15893 leads to ...


0

your Kali Linux system is running as a virtual machine not a physical machine and you have attached wifi hardware on host machine not to geust machine . so , you will not be able to direct access of wifi in guest machine. solution : connect to wifi on host system and then you have to create bridged or Nat to guest system to connect internet. i hope ...


3

towards the first item (quickly & easily): from the router, you should be able to use netstat -natp to show you a list of all active tcp connections. from your pc, try using nmap -v -sn 192.168.1.0/24 (substitute with your local net) to run a basic ping scan your local net. this should show you everyone connected (even via wifi). towards the second ...



Top 50 recent answers are included