I have connected two machines via Ethernet cable, 192.168.1.2(master) & 192.168.1.3(slave). I can ssh both and even ping command also works fine. Trouble is while running Hadoop & Nutch I have to ssh to the other machine, comes a part where ssh asks for password like this:
root@192.168.1.2 password: root@192.168.1.3 password
Wonder whose password should I be giving? master's? or slave's? or should it be:
master's passwd: slave passwd?.
I've purchased an Edimax AC600 Dual-Band Wi-Fi USB Adapter for my Ubuntu 18.04 PC. It did not work out of the box, and I saw advice out on the Internet on how to obtain the driver source code and install it, but I learned that a driver for this adapter is also available in Ubuntu through rtl8812au-dkms package. I installed the package by running
apt install rtl8812au-dkms
The adapter started working after installing the driver, but I cannot see any 5GHz WiFi networks on the PC. My laptop and phone can connect to my 5GHz network just fine, so the problem must be with the PC. If you had experience using this adapter, please let me know how did you make it see the 5GHz networks.
UPD1:
Upon heynnema's request I listed the avaliable frequencies and saw some 5GHz frequencies there:
dmytro@dkpc1:~$ iwlist wlx74da38eea053 freq
wlx74da38eea053 21 channels in total; available frequencies :
... [removed] ...
Channel 36 : 5.18 GHz
Channel 40 : 5.2 GHz
Channel 44 : 5.22 GHz
Channel 48 : 5.24 GHz
Channel 52 : 5.26 GHz
Channel 56 : 5.28 GHz
Channel 60 : 5.3 GHz
Channel 64 : 5.32 GHz
Current Frequency:2.427 GHz (Channel 4)
After this I inspected my router settings and found out that channel selection for 5GHz WiFi was set to automatic, and the channel 169 was selected. I changed it manually to channel 64. After this I was able to see the network from my PC and connect to it. Thanks!
I am having problems configuring the uncomplicated firewall (ufw) to allow outgoing multicast traffic. I am blocking all in and outgoing connections as the default policy. I have supplemented with the rules listed below. Yet, I get these error messages repeated twice after every time I boot the system:
Errors (repeated twice on boot-up):
[UFW BLOCK] IN= OUT=eth0 SRC=192.168.0.2 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
[UFW BLOCK] IN= OUT=eth0 SRC=fe80:0000:0000:0000:f66d:feee:feee:feee DST=ff02:0000:0000:0000:0000:0000:0000:0002 LEN=56 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0
[UFW BLOCK] IN= OUT=eth0 SRC=fe80:0000:0000:0000:f66d:04ff:feee:df54 DST=ff02:0000:0000:0000:0000:0000:0000:0016 LEN=96 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=ICMPv6 TYPE=143 CODE=0
Main rules:
ufw allow out proto udp to 224.0.0.0/3
ufw allow out proto udp to ff00::/8
ufw allow in proto udp to 224.0.0.0/3
ufw allow in proto udp to ff00::/8
in
/etc/ufw/user.rules:
-A ufw-before-input -p igmp -d 224.0.0.0/3 -j ACCEPT
-A ufw-before-output -p igmp -d 224.0.0.0/3 -j ACCEPT
and in
/etc/ufw/user6.rules:
-A ufw6-before-input -p icmpv6 -d ff00::/8 -j ACCEPT
-A ufw6-before-output -p icmpv6 -d ff00::/8 -j ACCEPT
Fresh install of Kubuntu 19.10 on a new Lenovo P53.
At first the Wifi network works, and I'm able to connect to my home Wifi using the usual password.
The driver manager recommends to install backport-iwlwifi-dkms, which I do, but now the passwords are rejected. I also tried my phone hotspot (that has a rather simple password) and it is rejected too. I can connect to the phone hotspot if I reconfigure it to be password-less.
Password can be displayed and is OK, I even copy/pasted it.
The log of a connection sequence from /var/log/syslog (it seems it tried first to connect using a stored password which is very likely the right one too):
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9624] device (wlp82s0): Activation: starting connection 'HomeNetwork' (9ca67590-8a02-495c-a7cb-da56076aad08)
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9627] audit: op="connection-activate" uuid="9ca67590-8a02-495c-a7cb-da56076aad08" name="HomeNetwork" pid=1633 uid=1000 result="success"
Jan 17 21:45:41 P53 kernel: [ 2997.428660] wlp82s0: authenticate with 14:0c:76:bc:ab:68
Jan 17 21:45:41 P53 wpa_supplicant[1122]: wlp82s0: SME: Trying to authenticate with 14:0c:76:bc:ab:68 (SSID='HomeNetwork' freq=5260 MHz)
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9630] device (wlp82s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9643] manager: NetworkManager state is now CONNECTING
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9656] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9664] device (wlp82s0): Activation: (wifi) access point 'HomeNetwork' has security, but secrets are required.
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9665] device (wlp82s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9684] device (wlp82s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9687] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] device (wlp82s0): Activation: (wifi) connection 'HomeNetwork' has security, and secrets exist. No new secrets needed.
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] Config: added 'ssid' value 'HomeNetwork'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] Config: added 'scan_ssid' value '1'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9689] Config: added 'psk' value '<hidden>'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9793] device (wlp82s0): supplicant interface state: inactive -> authenticating
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9793] device (p2p-dev-wlp82s0): supplicant management interface state: inactive -> authenticating
Jan 17 21:45:41 P53 kernel: [ 2997.433797] wlp82s0: send auth to 14:0c:76:bc:ab:68 (try 1/3)
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: Trying to associate with 14:0c:76:bc:ab:68 (SSID='HomeNetwork' freq=5260 MHz)
Jan 17 21:45:42 P53 NetworkManager[1121]: <info> [1579293942.0044] device (wlp82s0): supplicant interface state: authenticating -> associating
Jan 17 21:45:42 P53 NetworkManager[1121]: <info> [1579293942.0044] device (p2p-dev-wlp82s0): supplicant management interface state: authenticating -> associating
Jan 17 21:45:42 P53 kernel: [ 2997.458775] wlp82s0: authenticated
Jan 17 21:45:42 P53 kernel: [ 2997.461167] wlp82s0: associate with 14:0c:76:bc:ab:68 (try 1/3)
Jan 17 21:45:42 P53 kernel: [ 2997.463098] wlp82s0: RX AssocResp from 14:0c:76:bc:ab:68 (capab=0x111 status=0 aid=4)
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: Associated with 14:0c:76:bc:ab:68
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 17 21:45:42 P53 kernel: [ 2997.468796] wlp82s0: associated
Jan 17 21:45:42 P53 NetworkManager[1121]: <info> [1579293942.0195] device (wlp82s0): supplicant interface state: associating -> 4-way handshake
Jan 17 21:45:42 P53 NetworkManager[1121]: <info> [1579293942.0195] device (p2p-dev-wlp82s0): supplicant management interface state: associating -> 4-way handshake
Jan 17 21:45:42 P53 kernel: [ 2997.523928] wlp82s0: Limiting TX power to 17 (20 - 3) dBm as advertised by 14:0c:76:bc:ab:68
Jan 17 21:45:42 P53 kernel: [ 2998.015706] iwlwifi 0000:52:00.0: Unhandled alg: 0x707
Jan 17 21:45:43 P53 kernel: [ 2998.480972] wlp82s0: deauthenticating from 14:0c:76:bc:ab:68 by local choice (Reason: 1=UNSPECIFIED)
Jan 17 21:45:43 P53 wpa_supplicant[1122]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=14:0c:76:bc:ab:68)
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-DISCONNECTED bssid=14:0c:76:bc:ab:68 reason=1 locally_generated=1
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=1 duration=10 reason=WRONG_KEY
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=2 duration=20 reason=CONN_FAILED
Jan 17 21:45:43 P53 wpa_supplicant[1122]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3
Jan 17 21:45:43 P53 NetworkManager[1121]: <warn> [1579293943.0361] sup-iface[0x55e11c9c6be0,wlp82s0]: connection disconnected (reason -1)
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.0412] device (wlp82s0): supplicant interface state: 4-way handshake -> disconnected
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.0420] device (wlp82s0): Activation: (wifi) disconnected during association, asking for new key
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.0420] device (wlp82s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.0424] device (p2p-dev-wlp82s0): supplicant management interface state: 4-way handshake -> disconnected
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.1413] device (wlp82s0): supplicant interface state: disconnected -> inactive
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.1413] device (p2p-dev-wlp82s0): supplicant management interface state: disconnected -> inactive
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0258] device (wlp82s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0262] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] device (wlp82s0): Activation: (wifi) connection 'HomeNetwork' has security, and secrets exist. No new secrets needed.
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] Config: added 'ssid' value 'HomeNetwork'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] Config: added 'scan_ssid' value '1'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0266] Config: added 'psk' value '<hidden>'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0372] device (wlp82s0): supplicant interface state: inactive -> scanning
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0372] device (p2p-dev-wlp82s0): supplicant management interface state: inactive -> scanning
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: SME: Trying to authenticate with 14:0c:76:55:47:d1 (SSID='HomeNetwork' freq=2447 MHz)
Jan 17 21:45:55 P53 kernel: [ 3010.490277] wlp82s0: authenticate with 14:0c:76:55:47:d1
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0417] device (wlp82s0): supplicant interface state: scanning -> authenticating
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0417] device (p2p-dev-wlp82s0): supplicant management interface state: scanning -> authenticating
Jan 17 21:45:55 P53 kernel: [ 3010.496321] wlp82s0: send auth to 14:0c:76:55:47:d1 (try 1/3)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: Trying to associate with 14:0c:76:55:47:d1 (SSID='HomeNetwork' freq=2447 MHz)
Jan 17 21:45:55 P53 kernel: [ 3010.520689] wlp82s0: authenticated
Jan 17 21:45:55 P53 kernel: [ 3010.521092] wlp82s0: associate with 14:0c:76:55:47:d1 (try 1/3)
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0662] device (wlp82s0): supplicant interface state: authenticating -> associating
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0662] device (p2p-dev-wlp82s0): supplicant management interface state: authenticating -> associating
Jan 17 21:45:55 P53 kernel: [ 3010.525437] wlp82s0: RX AssocResp from 14:0c:76:55:47:d1 (capab=0x411 status=0 aid=3)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: Associated with 14:0c:76:55:47:d1
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 17 21:45:55 P53 kernel: [ 3010.531546] wlp82s0: associated
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0822] device (wlp82s0): supplicant interface state: associating -> 4-way handshake
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0822] device (p2p-dev-wlp82s0): supplicant management interface state: associating -> 4-way handshake
Jan 17 21:45:55 P53 wpa_supplicant[1122]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=14:0c:76:55:47:d1)
Jan 17 21:45:55 P53 kernel: [ 3010.543158] wlp82s0: deauthenticating from 14:0c:76:55:47:d1 by local choice (Reason: 1=UNSPECIFIED)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-DISCONNECTED bssid=14:0c:76:55:47:d1 reason=1 locally_generated=1
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=1 duration=10 reason=WRONG_KEY
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=2 duration=20 reason=CONN_FAILED
Jan 17 21:45:55 P53 wpa_supplicant[1122]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3
Jan 17 21:45:55 P53 NetworkManager[1121]: <warn> [1579293955.1000] sup-iface[0x55e11c9c6be0,wlp82s0]: connection disconnected (reason -1)
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.1051] device (wlp82s0): supplicant interface state: 4-way handshake -> disconnected
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.1056] device (wlp82s0): Activation: (wifi) disconnected during association, asking for new key
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.1057] device (wlp82s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.1060] device (p2p-dev-wlp82s0): supplicant management interface state: 4-way handshake -> disconnected
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.2052] device (wlp82s0): supplicant interface state: disconnected -> inactive
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.2052] device (p2p-dev-wlp82s0): supplicant management interface state: disconnected -> inactive
Jan 17 21:45:57 P53 NetworkManager[1121]: <warn> [1579293957.0813] device (wlp82s0): no secrets: User canceled the secrets request.
Jan 17 21:45:57 P53 NetworkManager[1121]: <info> [1579293957.0814] device (wlp82s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Jan 17 21:45:57 P53 NetworkManager[1121]: <info> [1579293957.0817] manager: NetworkManager state is now DISCONNECTED
Jan 17 21:45:57 P53 NetworkManager[1121]: <warn> [1579293957.0824] device (wlp82s0): Activation: failed for connection 'HomeNetwork'
Jan 17 21:45:57 P53 NetworkManager[1121]: <info> [1579293957.0826] device (wlp82s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
The part of lshw that seems relevant:
*-pci:3
description: PCI bridge
product: Cannon Lake PCH PCI Express Root Port #6
vendor: Intel Corporation
physical id: 1c.5
bus info: pci@0000:00:1c.5
version: f0
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:125 memory:ce200000-ce2fffff
*-network
description: Ethernet interface
product: Intel Corporation
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:52:00.0
logical name: wlp82s0
version: 1a
serial: 94:e6:f7:f4:70:cc
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical
configuration: broadcast=yes driver=iwlwifi driverversion=5.3.0-26-generic firmware=48.4fa0041f.0 latency=0 link=no multicast=yes
resources: irq:17 memory:ce200000-ce203fff
Any ideas?
Otherwise how do I reinstall the previous one?
$$>dkms status
backport-iwlwifi, 7906, 5.3.0-26-generic, x86_64: installed
nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
nvidia, 435.21, 5.3.0-26-generic, x86_64: installed
I have downloaded proxychains and configured it to run with tor. I want a chain of 3 or more proxies. 3 will be enough.
The problem is finding proxies that are up and running i just keep getting messages saying denied/timeout could i have a copy of someones proxychains.conf file that is up and working with alive proxies or give me a copy of proxies in the right arrangement i.e
socks4/5
https etc ip port
SOCKS5 1.81.97.243 6673
SOCKS5 1.81.148.187 6673
SOCKS5 1.81.127.201 6673
SOCKS5 1.61.149.199 6673
SOCKS5 95.78.55.48 1080
SOCKS4 178.54.32.58 50610
SOCKS5 178.150.156.219 13579
SOCKS5 95.78.18.183 1080
SOCKS4 93.85.4.0 52342
SOCKS5 5.167.238.35 1080
SOCKS5 95.78.48.149 1080
For the past two days, my data usage has increased even though I did nothing more than normal data surfing. I installed nethogs and found this application (/usr/bin/freshclam) drinking my data ridiculously. Can anyone help me with this? What is this and how can I completely remove it?
One more thing I wonder If any application can upload my documents data to its server without my permission (it would be a nightmare).
I have Ubuntu18 LTS running on an old iMac.
I have the wifi hardware disabled and my router doesn't have a portal.
For some reason hotspot login keeps opening and closing and my network icon changes to a ? and back again.
What is this?
And how can I remove/disable the hotspot login program?
My notebook has the infamous Intel AC 7260 adapter and after a few days the adapter just stopped working e.g. (The adapter can see the ap but can not connect when it connects it is connected for short time and than disconnects also it can't connect after disconnects), maybe it is because I ran apt-get update but I'm not sure.
I can't connect to ap
I checked the version of the driver
ls /lib/firmware/iwlwifi-7260*
and it returned
/lib/firmware/iwlwifi-7260-7.ucode
/lib/firmware/iwlwifi-7260-8.ucode
/lib/firmware/iwlwifi-7260-9.ucode
so I'm not sure which version of the driver the OS is using. Is it 7,8 or 9? I checked the Intel site and there is a version 9 for my kernel. I'm not sure if I should delete all 3 and get a new driver from Intel
Recently, I bought a Logitech M570 Wireless Trackball Mouse. While I am very happy with it overall, one issue is nagging me. Every so often, the mouse will experience a input lag, so movement is jumpy instead of smooth. This can be very annoying when I need to perform precise movements.
After doing some Google searching, I have found two possible causes of my problem.
After a look on Wikipedia, I verified the receiver uses the 2.4 GHz frequency band. However, the spec seems to suggest it jumps between frequencies in its band like Bluetooth, which makes it hard to verify whether this is the cause of my problem.
After a look at the frequencies used by nearby WiFi networks, I have found that two are in the 2.4 GHz range as well. Below is the output of sudo iwlist wlan0 scan | grep Frequency | sort | uniq -c | sort -n.
1 Frequency:2.437 GHz (Channel 6)
3 Frequency:2.412 GHz (Channel 1)
I am by no means an expert in wireless networking, but this does seem to help verify my theory that the receiver is in fact experiencing interference because it is jumping to these frequencies.
I can also verify that my USB WiFi adapter is adjacent to my receiver's USB port, which could be causing some problems as well. The WiFi adapter only supports the 2.4 GHz band, sadly, so preventing interference that way would be problematic, since I would be limited to jumping USB ports. Below is the output of iwlist wlan0 channel.
wlan0 14 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Channel 12 : 2.467 GHz
Channel 13 : 2.472 GHz
Channel 14 : 2.484 GHz
Current Frequency:2.412 GHz (Channel 1)
So, my question is, is it possible to change the frequency band of my receiver? If so, how? If anybody can come up with a better solution, please feel free to provide that as an answer as well.
I'm trying to forward incoming multicast traffic to my LAN.
This is the packet I can see coming into the WAN interface.
192.168.60.5.50258 > 234.5.6.7.8910: UDP, length 1000
Wan - eth0.2
Lan - br-lan / eth0.1
I've been trying a few different iptable entries but no success. Is there something different with it being a multicast packet?
Very new to Ubuntu, Linux, and command line. I installed Ubuntu 18.04 virtual box 6.0 and Kali Linux 19.04. I am trying to install the alfa awus036ach to look at my home network with Kali as a virtual machine. lsusb shows that the alfa is connected. I tried:
https://tacticalware.com/install-alfa-awus036ach-drivers-on-ubuntu-18-04/
Here I had issues coping files to the correct folder. Did not work for me
Also tried:
https://github.com/aircrack-ng/rtl8812au
Unsuccessfully.
I pretty sure am making errors and are unable/unfamiliar enough with Linux and command line to see my mistakes
Any and all help will be greatly appreciated. Also if it is not too much the why.
I'm running 16.04 LTS for my Unifi controller and have always used UFW.
I've always had UFW enabled and it's always worked. Lately, it seems that some rules don't even work anymore - can't even delete some while UFW is running, says that the rule cannot be found but run the same command while UFW is off and it accepts the command.
Everything other than the rules I've added are stock from Ubuntu's repo.
ufw --version
ufw 0.35
Copyright 2008-2015 Canonical Ltd.
lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
On starting the Virtual Machine through Bridged Adapter network settings, it shows error message:
Failed to open a session for the virtual machine <....>
Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (you might need to modprobe vboxnetflt to make it accessible) (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Please install the virtualbox-dkms package and execute 'modprobe vboxdrv' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND).
The output of command sudo modprobe vboxdrv is nothing, the terminal just goes to next line.
Please suggest
Same problem with Realtek Device b822 as discussed in rtl8723ae unstable on Ubuntu 14.04 and New install - no network devices available - Realtek Device b822. Tried installing rtl8822be with and without dkms. None of them works. Here are the details: https://paste.ubuntu.com/p/XkJjD6YmHZ/.
Sometimes, it says "No Wi-Fi Adapter Found". Sometimes, it is "No visible networks".
Updates
I did this:
wget https://github.com/lwfinger/rtlwifi_new/archive/extended.zip
unzip extended.zip
cd rtlwifi_new-extended
make
sudo make install
sudo modprobe rtl8822be
Got stuck in sudo modprobe rtl8822be. It gives me modprobe: ERROR: could not insert 'rtl8822be': Exec format error. Also, this my dmesg | grep rtl8822be output:
[ 20.265500] r8822be: Using firmware rtlwifi/rtl8822befw.bin
[ 39.784639] WARNING: CPU: 0 PID: 1076 at /build/linux-vxxS7y/linux-4.15.0/drivers/staging/rtlwifi/rtl8822be/fw.c:239 rtl8822be_fill_h2c_cmd+0x1ac/0x660 [r8822be]
[ 39.784685] RIP: 0010:rtl8822be_fill_h2c_cmd+0x1ac/0x660 [r8822be]
And, this is my dmesg | grep r8822be output (redoing the whole thing after disconnecting from the internet):
[ 9334.006706] r8822be: halmac_init_hal failed
[ 9334.006865] r8822be: halmac_init_hal failed
[ 9334.007017] r8822be: halmac_init_hal failed
[ 9334.007168] r8822be: halmac_init_hal failed
[ 9334.007319] r8822be: halmac_init_hal failed
[ 9334.007470] r8822be: halmac_init_hal failed
[ 9334.007620] r8822be: halmac_init_hal failed
[ 9334.007771] r8822be: halmac_init_hal failed
[ 9334.007922] r8822be: halmac_init_hal failed
[ 9334.008073] r8822be: halmac_init_hal failed
[ 9340.045331] r8822be: [ERR]Pwr cmd polling timeout!!
[ 9340.045337] r8822be: [ERR]Pwr cmd offset : 5!!
[ 9340.045340] r8822be: [ERR]Pwr cmd value : 0!!
[ 9340.045343] r8822be: [ERR]Pwr cmd msk : 2!!
[ 9340.045346] r8822be: [ERR]Read offset = 5 value = 2!!
[ 9340.045349] r8822be: [Err]pwr sub seq parser fail, status = 0x28!
[ 9340.045352] r8822be: Handle power off cmd error
Any help will be appreciated greatly!
PS: I was using my phone (creating a personal hotspot) to access the internet via bluetooth.
I can rsync to my remote computer, but cannot rsync from my remote computer - it doesn't seem to exchange a file list in that direction, so it tries to transfer all of a huge number of files rather than update just the ones that have changed are that are new.
The setup is a bit complicated. I have a remote computer behind a firewall and need to exchange files with that computer from my home computer. The home computer doesn't have a permanent IP address, so I'm using noip to bounce the reverse ssh to whatever my home computer's current IP address is. The reverse ssh command my remote computer is running is:
autossh -g -R 45678:localhost:22 me@noip.net
On my home computer, I'm running the noip2 program that tells noip.net to bounce port 45678 to my home computer.
On my home computer, I can synchronize my documents folder to my remote computer using:
rsync -navzu --stats -e "ssh -p 45678" --delete /home/me/Documents/ me@localhost:/home/me/Documents
That works fine. Only documents that are new or have been updated are transferred and the remote computer is made up-to-date.
However, when I try to reverse this to update home home computer from the remote computer with the following, it doesn't work:
rsync -navzu --stats -e "ssh -p 45678" --delete me@localhost:/home/me/Documents/ /home/me/Documents
rsync sees none of the files in Documents on my home computer and tries to transfer every file, on a dry run.
Any idea what's wrong here?
I use DLINK DWA-125 on my PC as my network card doesn't support wireless connections and have an issue with my adapter using Ubuntu 15.10. I can see a lot of WiFi spots but the connection quality is 0 for each of those spots, even for my own spot which is 2-3 meters away from my PC (I can connect to it, yet it takes a lot of time and then I get ridiculously low connection speed - average ping on google.com is 2700ms).
I tried to make my notebook function as a WiFi hotspot and then connected to it from my PC to check the connection - it worked, but I could get the connection quality 3/4 and the speed of 2 MB/s only when I put my laptop very close to the adapter.
I've searched through a bunch of topics on different forums but most of them discuss making visibility of the adapter in Ubuntu, so I could get literally nothing out of that.
I use clear Ubuntu 15.10 x86 (installed yesterday) and the driver for the adapter was successfully configured during the install.
driver: r8188eu
$ lsusb
Bus 002 Device 002: ID 2001:330f D-Link Corp.
$ iwconfig
wlx6c198f894581 IEEE 802.11bgn ESSID:"TP-LINK_B17466" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:2.442 GHz Access Point: C0:4A:00:B1:74:66
Bit Rate:150 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=75/100 Signal level=-48 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
lo no wireless extensions.
enp2s0 no wireless extensions.
Running
Linux RedmiBook 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
lspci reports the device
01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
dmesg shows following messages when modprobe ath10_pci
[ 35.405479] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 35.677189] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 11ad:0847
[ 35.677191] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 35.677655] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
[ 35.741238] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=11ad,subsystem-device=0847 from ath10k/QCA6174/hw3.0/board-2.bin
[ 35.741396] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a
[ 35.813765] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[ 35.832637] ath10k_pci 0000:01:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
ko
as a result no wifi no networks visible and no connection possible
P.S. Posted a bug report
I have a 3G stick that I'm connected with to the network. I would like to share this connection with my PlayStation 3. How can I create a virtual router?
I'm investigating a system freeze and I came across the following in /var/log/syslog
Jan 22 08:40:41 hostname wpa_supplicant[907]: message repeated 42 times: [ TDLS: Invalid frame - payloadtype=1 category=241 action=42]
Jan 22 08:40:44 hostname wpa_supplicant[907]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
Jan 22 08:40:46 hostname wpa_supplicant[907]: TDLS: Invalid frame - payloadtype=1 category=241 action=42
Jan 22 08:40:49 hostname wpa_supplicant[907]: message repeated 11 times: [ TDLS: Invalid frame - payloadtype=1 category=241 action=42]
Jan 22 08:40:51 hostname wpa_supplicant[907]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
Jan 22 08:40:53 hostname wpa_supplicant[907]: TDLS: Invalid frame - payloadtype=1 category=241 action=42
Jan 22 08:40:56 hostname wpa_supplicant[907]: message repeated 35 times: [ TDLS: Invalid frame - payloadtype=1 category=241 action=42]
Jan 22 08:40:58 hostname wpa_supplicant[907]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
Jan 22 08:41:01 hostname wpa_supplicant[907]: TDLS: Invalid frame - payloadtype=1 category=241 action=42
Jan 22 08:41:04 hostname wpa_supplicant[907]: message repeated 11 times: [ TDLS: Invalid frame - payloadtype=1 category=241 action=42]
Jan 22 08:41:05 hostname wpa_supplicant[907]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
Jan 22 08:41:08 hostname wpa_supplicant[907]: TDLS: Invalid frame - payloadtype=1 category=241 action=42
Jan 22 08:41:11 hostname wpa_supplicant[907]: message repeated 40 times: [ TDLS: Invalid frame - payloadtype=1 category=241 action=42]
This goes on for hours and hours, pretty much from boot up. I've had a hard time finding anything related to this message. Any help would be appreciated. I should add that the network connection does work and I can communicate to the box via wifi.
Could this be due to improper network configuration? We are on 16.04 and used as an embedded device so configuration of wifi is done through nmcli.
I have Ubuntu server 12.04 installed, so I have no GUI. When I do the command ifconfig, I cannot find my internl ip address. It says inet addr: 127.0.0.1 .
Here is the output of ifconfig -a:
eth0 link encap:Ethernet HWaddr 00:06:4f:4a:66:f0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth1 link encap:Ethernet HWaddr 00:16:ec:05:c8:9c
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr 127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1800 errors:0 dropped:0 overruns:0 frame:0
Tx packets:1800 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:143896 (143.b KB) TX bytes:143896 (143.8 KB)
here are the contents of etc/network/interfaces:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
If someone could edit this for me, the contents of etc/network/interfaces should be on seperate lines.
The output of host askubuntu.com was:
;; connection timed out; no servers could be reached.
I set up owncloud and webmin a few months ago and was using them for a month with no problems. I think the power went off one day 2 months ago and I never turned the server back on until yesterday. I haven't done anything that would have affected the internet setup So i'm not sure why it doesn't work anymore. As far as my network topology goes, I have a pci-e network card for the pc. The ethernet line goes from the network card to a switch, and then to a modem/router from there.