so it seems that without any config, the traffic passes from wlan1 to wlan0’s network flawlessly; but traffic from wlan0 network stops at the Android device, even with iptables -P FORWARD ACCEPT, so I’m clueless on what to do next

how could I set up NAT like this ? thanks

ip r

default via 192.168.15.1 dev enp3s0 proto dhcp src 192.168.15.32 metric 100
192.168.15.0/24 dev enp3s0 proto kernel scope link src 192.168.15.32 metric 100
192.168.38.0/24 via 192.168.15.21 dev enp3s0    

tyvm

Another section of the log when this happened:

Aug 15 18:00:48 arch kwin_wayland[3328]: This plugin does not support raise()
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_VALUE in glTexStorage2D(width, height or depth < 1)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glBindFramebuffer(non-gen name)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)

autistic fixation with IPV6

tyvm

seems to be working, even with some 404s returned

/var/lib/pacman/sync/multilib.db.part 100%[===================================================================================================================>] 137.53K --.-KB/s in 0.007s

2024-08-14 11:06:10 (19.4 MB/s) - ‘/var/lib/pacman/sync/multilib.db.part’ saved [140827/140827]

–2024-08-14 11:06:10-- https://mirror.osbeck.com/archlinux/multilib/os/x86_64/multilib.db.sig Loaded CA certificate ‘/etc/ssl/certs/ca-certificates.crt’ Resolving mirror.osbeck.com (mirror.osbeck.com)… 2606:4700:20::6819:5e05, 2606:4700:20::ac43:6136, 2606:4700:20::6819:5f05 Connecting to mirror.osbeck.com (mirror.osbeck.com)|2606:4700:20::6819:5e05|:443… connected. HTTP request sent, awaiting response… 404 not found 2024-08-14 11:06:10 ERROR 404: not found.

That’d be over 1TB with zram on