Tag: RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1

Why are my packets going out the wrong interface according to the linux routing table?

Post author By How To
Post date March 13, 2021
No Comments on Why are my packets going out the wrong interface according to the linux routing table?

I have an Ubuntu Bionic machine with a wifi link; and I have set up a wireguard tunnel on it: # ifconfig lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 5502 bytes 545376 (545.3 KB) RX errors 0 dropped 0 overruns 0 […]

Tags 30 hops max, 60 byte packets 1 10.0.0.1 (10.0.0.1) 68.393 ms 74.587 ms 74.328 ms^C But if use traceroute 8.8.8.8 -i wlan0 to force traceroute to use, as the routing table above should enforce, BROADCAST, but now I have reversed that to allow the peer to forward through this host. However, I have an Ubuntu Bionic machine with a wifi link; and I have set up a wireguard tunnel on it: # ifconfig lo: flags=73<UP, it always hangs. Traceroute shows that it's trying to route packets through the tunnel (the peer is currently configured to drop them): trac, it seems like my packets still want to route through the tunnel for some reason. Here's my routing table: # route -n Kernel IP routing tabl, LOOPBACK, MULTICAST> mtu 1500 inet 192.168.1.218 netmask 255.255.0.0 broadcast 192.168.255.255 ether dc:85:de:f3:3f:65 txqueuelen 1, NOARP> mtu 1420 inet 10.0.0.3 netmask 255.255.0.0 destination 10.0.0.3 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00, POINTOPOINT, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, then it works. What could be going on? Doesn't the routing table say that packets targeting 8.8.8.8 have to go out wlan0 to 192.168.1.1 for

User Help

Using Alfa AWUS036NH on a Raspberry pi 4 running kali linux

Post author By How To
Post date March 3, 2021
No Comments on Using Alfa AWUS036NH on a Raspberry pi 4 running kali linux

I’m having an issue with my raspberry detecting the Alfa antenna I got. I’m trying to configure and get up running the Alfa AWUS036NH on my Kali linux system (Image here. Kali Linux RaspberryPi 2 (v1.2), 3, 4 and 400 (64-Bit)), which is installed on the Raspberry pi 4 model B. When plugging the Alfa […]

Tags 3, 4 and 400 (64-Bit)), and that it should be detected without further action. Though it looks like it is not on my system, because the antenna is not detected by the system in any way. (I did not install any driver). I have also connected the raspberry to my loca, BROADCAST, I'm having an issue with my raspberry detecting the Alfa antenna I got. I'm trying to configure and get up running the Alfa AWUS036NH on my, LOOPBACK, MULTICAST> mtu 1500 ether dc:a6:32:a6:7a:34 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0, MULTICAST> mtu 1500 inet 192.168.1.31 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::a700:d248:d3cb:5d46 prefi, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, so I do have an internet connection via the pi's internal network card. I'm running kali on a headless pi over ssh. The alfa antenna was con, the Alfa signal LED lights up and stays lit. So I am assuming the system is powered up correctly. I have read that the antenna is supported, which is installed on the Raspberry pi 4 model B. When plugging the Alfa USB cable in the booted pi (I tried all the USB 2 and USB 3 ports)

User Help

Using Alfa AWUS036NH on a Raspberry pi 4 running kali linux

Post author By How To
Post date February 28, 2021
No Comments on Using Alfa AWUS036NH on a Raspberry pi 4 running kali linux

Tags 3, 4 and 400 (64-Bit)), and that it should be detected without further action. Though it looks like it is not on my system, because the antenna is not detected by the system in any way. (I did not install any driver). I have also connected the raspberry to my loca, BROADCAST, I'm having an issue with my raspberry detecting the Alfa antenna I got. I'm trying to configure and get up running the Alfa AWUS036NH on my, LOOPBACK, MULTICAST> mtu 1500 ether dc:a6:32:a6:7a:34 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0, MULTICAST> mtu 1500 inet 192.168.1.31 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::a700:d248:d3cb:5d46 prefi, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, so I do have an internet connection via the pi's internal network card. I'm running kali on a headless pi over ssh. The alfa antenna was con, the Alfa signal LED lights up and stays lit. So I am assuming the system is powered up correctly. I have read that the antenna is supported, which is installed on the Raspberry pi 4 model B. When plugging the Alfa USB cable in the booted pi (I tried all the USB 2 and USB 3 ports)

User Help

Using Alfa AWUS036NH on a Raspberry pi 4 running kali linux

Post author By How To
Post date February 27, 2021
No Comments on Using Alfa AWUS036NH on a Raspberry pi 4 running kali linux

Tags 3, 4 and 400 (64-Bit)), and I can't seem to find a reasonable solution. Edit 1: after installing Kali 2021 on a notebook and doing the same procedure, and that it should be detected without further action. Though it looks like it is not on my system, because the antenna is not detected by the system in any way. (I did not install any driver). I have also connected the raspberry to my loca, BROADCAST, I'm having an issue with my raspberry detecting the Alfa antenna I got. I'm trying to configure and get up running the Alfa AWUS036NH on my, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub kali@kali:~$ sudo airmon-ng [sudo] password for kali: PHY Inter, LOOPBACK, MULTICAST> mtu 1500 ether dc:a6:32:a6:7a:34 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0, MULTICAST> mtu 1500 inet 192.168.1.31 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::a700:d248:d3cb:5d46 prefi, network interface not detected., no usb signal, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, so I do have an internet connection via the pi's internal network card. I'm running kali on a headless pi over ssh. The alfa antenna was con, the Alfa signal LED lights up and stays lit. So I am assuming the system is powered up correctly. I have read that the antenna is supported, the result is the same. Alfa light on, which is installed on the Raspberry pi 4 model B. When plugging the Alfa USB cable in the booted pi (I tried all the USB 2 and USB 3 ports)

Linux Mastering Development

Connection problems after Docker install

Post author By Linux Questions
Post date February 25, 2021
No Comments on Connection problems after Docker install

I have installed Docker normally and everything worked fine but after a reboot, I lost my network (PCIe Wireless Adapter, Wired Connection, and even USB Tethering). I found a lot of similar content, but none works for me. I even removed Docker completely but still with the problem. I don’t know now if Docker was […]

Tags and even USB Tethering). I found a lot of similar content, because as I said, but it seems a big coincidence. Also, but none works for me. I even removed Docker completely but still with the problem. I don't know now if Docker was the problem, I don't have problems. Even on an older Kernel version, I have "No Wi-Fi Adapter Found". ifconfig: lo: flags=73<UP, I have installed Docker normally and everything worked fine but after a reboot, I lost my network (PCIe Wireless Adapter, I tried to set bip on /etc/docker/daemon.json: { "bip": "172.31.0.1/16" } Doesn't work as well. I tried to boot into the older Kernel wh, it was working fine before the reboot. I also tried: sudo rfkill list sudo rfkill unblock all Can someone help me, it works. Before removed Docker, LOOPBACK, Ltd. physical id: 0 bus info: pci@0000:06:00.0 version: 00 width: 64 bits clock: 33MHz capabilities, Ltd. physical id: 0 bus info: pci@0000:07:00.0 version: 15 width: 64 bits clock: 33MHz capabilities, on Live USB, please? System info: OS Name: Ubuntu 20.04.1 LTS Kernel: 5.8.0-44-generic (on 5.8.0-43-generic it works) OS Type: 64-bit GNOME Version:, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, then lost internet connection on reboot! [Ubuntu 16.04.2 LTS], Wired Connection

Mastering Development System & Network

OpenVPN server assigns same IP address (10.8.0.6) to all connected clients

Post author By Server Questions
Post date February 24, 2021
No Comments on OpenVPN server assigns same IP address (10.8.0.6) to all connected clients

I followed How To Set Up and Configure an OpenVPN Server on Ubuntu 20.04 to setup OpenVPN server. I noticed, when any clients connects to OpenVPN Server, each of them is getting same IP address: 10.8.0.6. In /etc/openvpn/server/server.conf, I have these settings so that it can assigns IP addresses in 10.8.0.X. # Configure server mode […]

Tags # the rest will be made available to clients. # Each client will be able to reach the server # on 10.8.0.1. Comment this line out if you are, BROADCAST, each of them is getting same IP address: 10.8.0.6. In /etc/openvpn/server/server.conf, I followed How To Set Up and Configure an OpenVPN Server on Ubuntu 20.04 to setup OpenVPN server. I noticed, I have these settings so that it can assigns IP addresses in 10.8.0.X. # Configure server mode and supply a VPN subnet # for OpenVPN to draw, LOOPBACK, MULTICAST> mtu 1500 inet 10.8.0.6 netmask 255.255.255.255 destination 10.8.0.5 inet6 fe80::2fa0:961f:7ba8:c04c prefixlen, MULTICAST> mtu 1500 inet 192.168.11.23 netmask 255.255.255.0 broadcast 192.168.11.255 inet6 240b:11:8a62:bc10:f64d:30ff:fe, NOARP, POINTOPOINT, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, when any clients connects to OpenVPN Server

Mastering Development System & Network

OpenVPN server assigns same IP address (10.8.0.6) to all connected clients

Post author By Server Questions
Post date February 24, 2021
No Comments on OpenVPN server assigns same IP address (10.8.0.6) to all connected clients

Tags # the rest will be made available to clients. # Each client will be able to reach the server # on 10.8.0.1. Comment this line out if you are, BROADCAST, each of them is getting same IP address: 10.8.0.6. In /etc/openvpn/server/server.conf, I followed How To Set Up and Configure an OpenVPN Server on Ubuntu 20.04 to setup OpenVPN server. I noticed, I have these settings so that it can assigns IP addresses in 10.8.0.X. # Configure server mode and supply a VPN subnet # for OpenVPN to draw, LOOPBACK, MULTICAST> mtu 1500 inet 10.8.0.6 netmask 255.255.255.255 destination 10.8.0.5 inet6 fe80::2fa0:961f:7ba8:c04c prefixlen, MULTICAST> mtu 1500 inet 192.168.11.23 netmask 255.255.255.0 broadcast 192.168.11.255 inet6 240b:11:8a62:bc10:f64d:30ff:fe, NOARP, POINTOPOINT, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, when any clients connects to OpenVPN Server

Mastering Development System & Network

OpenVPN server assigns same IP address (10.8.0.6) to all connected clients

Post author By Server Questions
Post date February 24, 2021
No Comments on OpenVPN server assigns same IP address (10.8.0.6) to all connected clients

Tags # the rest will be made available to clients. # Each client will be able to reach the server # on 10.8.0.1. Comment this line out if you are, BROADCAST, each of them is getting same IP address: 10.8.0.6. In /etc/openvpn/server/server.conf, I followed How To Set Up and Configure an OpenVPN Server on Ubuntu 20.04 to setup OpenVPN server. I noticed, I have these settings so that it can assigns IP addresses in 10.8.0.X. # Configure server mode and supply a VPN subnet # for OpenVPN to draw, LOOPBACK, MULTICAST> mtu 1500 inet 10.8.0.6 netmask 255.255.255.255 destination 10.8.0.5 inet6 fe80::2fa0:961f:7ba8:c04c prefixlen, MULTICAST> mtu 1500 inet 192.168.11.23 netmask 255.255.255.0 broadcast 192.168.11.255 inet6 240b:11:8a62:bc10:f64d:30ff:fe, NOARP, POINTOPOINT, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, when any clients connects to OpenVPN Server

Linux Mastering Development

“Cable unplugged”, network issues on Linux Mint dual boot

Post author By Linux Questions
Post date February 21, 2021
No Comments on “Cable unplugged”, network issues on Linux Mint dual boot

I have recently bought a new router (D-Link EXO DIR-878 AC1900) and I am now experiencing weird network issues on my dual boot machine (Win 10 / Mint 20). On Windows and all other connected devices everything works just fine without any issues, but when booting Linux I usually cannot connect to internet at all. […]

Tags 00100101" "0x1043" "0x87c5" Feb 21 12:30:25 computer-name alsactl[843]: Hardware is initialized using a generic method Feb 21 12:30:25 comput, 00100700" "0x1da2" "0xaaf0" Feb 21 12:30:25 computer-name alsactl[843]: Hardware is initialized using a generic method Feb 21 12:30:25 comput, 00aa0100, 104387c5, and also upgrading it to the latest firmware And nothing of that works. There is one thing that does work, BROADCAST, but they will never show any light whatsoever after the computer boots into "cable unplugged". I tried checking the router logs but it did n, but when booting Linux I usually cannot connect to internet at all. It just says "cable unplugged", even though the Ethernet cable is plugged in (and works on Windows). Some things that I have tried to no avail: Disconnecting and reconnect, here is a partial dump from the syslog along with output from "ifconfig" and "ip a" after booting into "cable unplugged": SYSLOG ====== Feb, however: Rebooting the computer. Weirdly enough, I have recently bought a new router (D-Link EXO DIR-878 AC1900) and I am now experiencing weird network issues on my dual boot machine (Win 1, in maybe 1 of 5-10 boots I can connect to internet and everything works perfectly with no issues at all. But when it shows "cable unplugged", LOOPBACK, LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 3c:7c:3f:f0:05:a4 brd ff:ff:ff:ff:ff:ff inet 192.168.0.192/24, LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 12, MULTICAST, MULTICAST> mtu 1500 ether 3c:7c:3f:f0:05:a4 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0, MULTICAST> mtu 1500 inet 192.168.0.192 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::65f2:62cd:c3a2:39a prefi, plugin=systemd-resolved Feb 21 12:30:26 computer-name NetworkManager[764]: [1613907026.0149] manager[0x559f18803030]: rfkill: Wi-Fi h, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, up, UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 3c:7c:3f:f0:05:a4 brd ff:ff:ff:ff:ff:ff And here is output from "ifc

Mastering Development System & Network

How to access subnet from Open VPN server (Ubuntu), VPN client RouterOS?

Post author By Server Questions
Post date January 29, 2021
No Comments on How to access subnet from Open VPN server (Ubuntu), VPN client RouterOS?

Here’s the setup: [OpenVPN server] — WAN — [RouterOS client] — [Local subnet client] 10.5.0.0 10.5.0.14 10.10.10.2 $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 123.45.128.1 0.0.0.0 UG 0 0 0 eth0 10.5.0.0 10.5.0.2 255.255.255.0 UG 0 0 0 tun0 10.5.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 […]

Tags 0% packet loss ❔ How can I make route from [OpenVPN server] to [Local subnet]? e.g. ping 10.10.10.2, BROADCAST, Here's the setup: [OpenVPN server] --- WAN --- [RouterOS client] --- [Local subnet client] 10.5.0.0 10.5.0.14, LOOPBACK, MULTICAST> mtu 1500 inet 10.5.0.1 netmask 255.255.255.255 destination 10.5.0.2 inet6 fe80::8d8b:2759:671:2327 prefixlen 6, MULTICAST> mtu 1500 inet 123.45.67.89 netmask 255.255.240.0 broadcast 123.45.123.255 inet6 fe80::b47f:49ff:fe42:8567 pref, NOARP, POINTOPOINT, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1