Hi, I used arch based distros before, and i know that arch packages about wifi doesn’t support WEP networks. Btw, is there any way to connect to a WEP wifi? I have a old ass tp link router so it won’t let me to setup again for switching to wpa or something like that, pls help me!
Seems like this was asked before both in reddit and here. Do a bit of searxing.
4 Likes
Hi there, welcome to the forum.
Please follow the topic template and post your garuda-inxi.
Thank you. 
3 Likes
hi,
did you try to disable in the webbrowser only https? like this error message what i got.
You’ve enabled HTTPS-Only Mode for enhanced security, …
did your tp link router has an ip where you can get access to it? or a tp-login page?
you can also try to create a new networj=k with the settings?
In my opinion you have to switch to iwd with networkmanager instead of wpa_supplicant
See e.g. (see the Edit at the end):
Or use iwd directly:
5 Likes
I tried the steps, but now no wifi networks shows up, i hope you could help me, can you say the exacts steps i need to do to connect to a wfi WEP network?
Thank you
It would be very helpful if you would post your garuda-inxi. This would give us an overview of your system - for example desktop environment, wifi hardware/wifi drivers and which network manager is in use.
2 Likes
sure, here is it.
System:
Kernel: 6.13.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=fd8e5572-ca27-4ac1-a0b8-7c7162cc7106 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: ERR-101 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: H110-D3A v: N/A serial: N/A
Mobo: Gigabyte model: H110-D3A-CF serial: N/A
uuid: 03d502e0-045e-0581-8606-7b0700080009 UEFI: American Megatrends v: F25
date: 04/11/2018
CPU:
Info: model: Intel Core i3-6300 socket: U3E1 bits: 64 type: MT MCP
arch: Skylake-S gen: core 6 level: v3 note: check built: 2015
process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3
microcode: 0xF0
Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 800 min/max: 800/3800 base/boost: 3800/8300 scaling:
driver: intel_pstate governor: powersave volts: 1.2 V ext-clock: 100 MHz
cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 30399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel HD Graphics 530 vendor: Gigabyte driver: i915 v: kernel
arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: DP-1
empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:1912 class-ID: 0300
Display: unspecified server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :1 screens: 1
Screen-1: 0 s-res: 1280x720 s-dpi: 96 s-size: 339x191mm (13.35x7.52")
s-diag: 389mm (15.32")
Monitor-1: DP-1 model: AOC 718Swag-1 serial: <filter> built: 2008 res:
mode: 1280x720 hz: 75 scale: 100% (1) dpi: 87 gamma: 1.2
size: 372x210mm (14.65x8.27") diag: 427mm (16.8") ratio: 16:9 modes:
max: 1280x720 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 530 (SKL GT2)
device-ID: 8086:1912 memory: 3.73 GiB unified: yes
API: Vulkan v: 1.4.304 layers: 8 device: 0 type: integrated-gpu name: Intel
HD Graphics 530 (SKL GT2) driver: N/A device-ID: 8086:1912
surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 19.1.7 256
bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
chip-ID: 8086:a170 class-ID: 0403
API: ALSA v: k6.13.5-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.7 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp1s0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter
vendor: AzureWave driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 04:00.0 chip-ID: 168c:0032 class-ID: 0280
IF: wlp4s0 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8.2:6
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
Local Storage: total: 521.66 GiB used: 63.29 GiB (12.1%)
ID-1: /dev/sda maj-min: 8:0 model: SSD 240GB size: 223.57 GiB block-size:
physical: 512 B logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: 7A0 temp: 30 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 23d 20h cycles: 680
read: 100.6 MiB written: 60.5 MiB
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST320LT012-1DG14C
family: Laptop HDD size: 298.09 GiB block-size: physical: 4096 B
logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s lanes: 1 mode: 2.0
sata: 3.0 speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0001SDM1 temp: 38 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 2y 57d 21h cycles: 12630
read: 55.53 TiB written: 22.4 TiB Old-Age: g-sense error rate: 2091
Pre-Fail: reallocated sector: 100 threshold: 36
attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
Partition:
ID-1: / raw-size: 110.99 GiB size: 110.99 GiB (100.00%)
used: 9.37 GiB (8.4%) fs: btrfs block-size: 4096 B dev: /dev/sda4
maj-min: 8:4
ID-2: /boot/efi raw-size: 600 MiB size: 598.8 MiB (99.80%)
used: 19 MiB (3.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 110.99 GiB size: 110.99 GiB (100.00%)
used: 9.37 GiB (8.4%) fs: btrfs block-size: 4096 B dev: /dev/sda4
maj-min: 8:4
ID-4: /var/log raw-size: 110.99 GiB size: 110.99 GiB (100.00%)
used: 9.37 GiB (8.4%) fs: btrfs block-size: 4096 B dev: /dev/sda4
maj-min: 8:4
ID-5: /var/tmp raw-size: 110.99 GiB size: 110.99 GiB (100.00%)
used: 9.37 GiB (8.4%) fs: btrfs block-size: 4096 B dev: /dev/sda4
maj-min: 8:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.64 GiB used: 311.6 MiB (4.0%)
priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
max-streams: 4 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 8 GiB available: 7.64 GiB used: 4.77 GiB (62.5%) igpu: 64 MiB
Processes: 250 Power: uptime: 18m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3.04 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1725 libs: 523 tools: octopi,paru Compilers:
clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi (sudo) default: Bash v: 5.2.37
running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date: 2025-04-18
Last full system update: 2025-04-18
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units:
all I want is connect to my wifi WEP network.
Something in the instructions didn’t work probably.
AFAIK wpa_supplicant doesn’t support anymore WEP, that’s why we need iwd
#install iwd,
sudo pacman -S iwd --needed
#stop the NetworkManager.service
sudo systemctl stop NetworkManager
#stop/disable the wpa_supplicant.service.
sudo systemctl disable --now wpa_supplicant.service
#mask the wpa_supplicant.service.
sudo systemctl mask wpa_supplicant
#create the Network Manager backend configuration file
echo -e "[device]\nwifi.backend=iwd" | sudo tee /etc/NetworkManager/conf.d/wifi_backend.conf
#reload and apply any changes to systemd services
sudo systemctl daemon-reload
#restart the NetworkManager.service.
sudo systemctl start NetworkManager
Of course you’ll have to use tethering with your mobile phone.
Then, with networkmanager everthing should work as normal.
If not, you could try the manual connection.
2 Likes
No offense intended, but this is a waste everyone’s time.
Please search the following phrase with a mainstream search engine:
"Is wep encryption secure? "
The response from the most prevalent search engine is pretty unambiguous. First response from Google:
A WEP-protected network can be cracked in under a minute, especially if the network sees a lot of traffic. Threat actors are then able to intercept a large number of data packets. WEP has been demonstrated to be extremely insecure and should not be used to protect Wi-Fi networks.
WEP encryption has been obsolete for ages. Even if money is extremely tight, I’m sure you can find used hardware with a secure mode of encryption very cheaply or even for free. Most people upgrade there hardware fairly regularly and older but secure models of router’s and low cost wifi can likely be found for next to nothing, (or for free at an electronics recycling depot) .
Sorry to be so blunt, but trying to force a WEP connection to work properly is a waste of effort, it’s simply too outdated to provide any level of security.
5 Likes
Btw: You did not perform a system update after the installation:
Open a terminal and please perform a garuda-update.
And please make a backup of this external HDD:
Either the USB cable is bad, or the controller of the external enclosure is defective or the hard disk is slowly dying - in this case you should replace the drive with a new one.