There is an "rst@1" at the bottom of the screen next to the name of the networks that have been owned
Is there any way I can remove this from the screen?
I'm using pwnagotchi version 2.5.6 and waveshare_3 screen
Thank you very much.

Is your feature request related to a problem? Please describe.
Enhancement request. Presently, users have to invert the color presentation by editing view.py, which appears to be overwritten or reverted under certain conditions (including updates)

Describe the solution you'd like
Adding a parameter to the config.toml file might provide a better way to preserve user settings between updates. Perhaps adding something like ui.display.invertcolors would be a good way to address the issue.

Describe the bug
Installed latest 2.4.8 image on Raspberry Pi 3B+, 4B, and 400, all get their IP address through DHCP on the Ethernet port, but for some odd reason, the default route doesn't get set on a 3B+, but it does get set on a 4B and 400

To Reproduce
Steps to reproduce the behavior:
Install 2.4.8 on a Raspberry Pi 3B+, plug in the Ethernet, do a "netstat -r", mysteriously 3B+ doesn't have default route, but do the exact same thing on a 4B or 400 and it does get set.

Expected behavior
Expect the 3B+ to get the default route

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Pwnagotchi version 2.4.8
• OS version Linux pwnagotchi3b 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
• Type of hardware Raspberry Pi 3B+

Additional context
As a work around, I added "sudo route add default gw xx.xx.xx.xx" to the /usr/bin/pwnagotchi-launcher so that the default route would get set each time a reboot occured (of course I can't easily move this pwnagotchi to a different network now).

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

so when setting the internet sharing for the device I realize it was set for a 10.0.0.x network many users including my self had an issue as we dont have that setup we are on att and thus bound by the 192.168.1.254 gateway that is att

Describe the solution you'd like
A clear and concise description of what you want to happen.

easier more modular powershell script, enter in your gateway and go.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

writing a new script. see below for example. [needs some more work]

Additional context
Add any other context or screenshots about the feature request here.

based on the original script which is made for a 10.0.0.1 network and then my 192.168.1.x for att users

https://raw.githubusercontent.com/evilsocket/pwnagotchi/master/scripts/win_connection_share.ps1

and

https://pastebin.com/edit/zwbFHW3n

then

https://pastebin.com/SL1ynbg3

Describe the bug
Installed 2.2.4 on a Raspberry Pi Zero 2W, saw in the log where it said "restarting wifi.recon" but didn't work

To Reproduce
Steps to reproduce the behavior:

1. just leave it there running
2. ...
3. ...

Expected behavior
The hope is that FixBRCMF would keep it pwnagotchi running without doing a reboot.

Screenshots

Environment (please complete the following information):

• Pwnagotchi version 2.2.4

• OS version

• Type of hardware Raspberry Pi Zero 2 W
  pwnagotchi.log

• Any additional hardware used

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
Problem, having to always get the pwnagotchi to connect to bluetooth tether with my phone to get internet.

Describe the solution you'd like
Having the pwnagotchi connect to wifi networks listed in a config option.

I know you can't have the pwnagotchi deauth if the wifi chip is having to be connected to a network, however, many people, like myself, use an external wifi adapter to deauth, and just turn the pi's wifi chip off. What I'm wanting is to instead of turning the chip off, using it to connect to networks that we list. I know what I'm wanting is possible and can be done individually, but it requires a lot of changes to be done, which is why most people don't do it. Having the ability to just click a button in the config, and type our network and password would be awesome

Additional context
this just an idea, ok if it nots something that you'd want to take on

I need your help updating the languages on the project! If you speak a language that is not English, please help update the languages for Pwnagotchi-Torch.

You can fork my repo edit your language file and then create a PR. I would appreciate your help. I have taken the liberty to update Dutch.

Is it possible to run on pi5?

When updating from 2.5.0 to 2.5.1, RPI will reboot.

Steps to reproduce the behavior:

1. sudo pwnagotchi --check-update
2. wait a few minutes, will reboot
3. update fails

Expected behavior

Environment (please complete the following information):

• Pwnagotchi version 2.5.1
• OS version 64bit
• Type of hardware RPI 4 8gb
• Any additional hardware used External Wifi. Fails with onboard as we..

Not sure if this is an issue with the fork, or lack of knowledge on my part. I have disabled onboard WIFI for my Pi Zero 2 W in config.txt, and added an ALFA AC600 USB WIFI, with drivers successfully installed (https://github.com/aircrack-ng/rtl8812au), and packet injection successfully tested via 'aireplay-ng -9 wlan0'. However, pwnagotchi will not work.

Here is a log:

Sep 10 00:22:44 Loki kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Sep 10 00:22:44 Loki systemd-fsck[151]: e2fsck 1.46.2 (28-Feb-2021)
Sep 10 00:22:44 Loki kernel: [ 0.000000] Linux version 6.1.21-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023
Sep 10 00:22:44 Loki kernel: [ 0.000000] random: crng init done
Sep 10 00:22:44 Loki systemd-fsck[151]: rootfs: clean, 140127/7504960 files, 2393187/30801920 blocks
Sep 10 00:22:44 Loki kernel: [ 0.000000] Machine model: Raspberry Pi Zero 2 W Rev 1.0
Sep 10 00:22:44 Loki kernel: [ 0.000000] efi: UEFI not found.
Sep 10 00:22:44 Loki kernel: [ 0.000000] Reserved memory: created CMA memory pool at 0x000000001ac00000, size 64 MiB
Sep 10 00:22:44 Loki kernel: [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Sep 10 00:22:44 Loki kernel: [ 0.000000] Zone ranges:
Sep 10 00:22:44 Loki systemd[1]: Finished File System Check on Root Device.
Sep 10 00:22:44 Loki kernel: [ 0.000000] DMA [mem 0x0000000000000000-0x000000001effffff]
Sep 10 00:22:44 Loki kernel: [ 0.000000] DMA32 empty
Sep 10 00:22:44 Loki kernel: [ 0.000000] Normal empty
Sep 10 00:22:44 Loki kernel: [ 0.000000] Movable zone start for each node
Sep 10 00:22:44 Loki kernel: [ 0.000000] Early memory node ranges
Sep 10 00:22:44 Loki kernel: [ 0.000000] node 0: [mem 0x0000000000000000-0x000000001effffff]
Sep 10 00:22:44 Loki systemd[1]: Starting Remount Root and Kernel File Systems...
Sep 10 00:22:44 Loki kernel: [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000001effffff]
Sep 10 00:22:44 Loki kernel: [ 0.000000] On node 0, zone DMA: 4096 pages in unavailable ranges
Sep 10 00:22:44 Loki kernel: [ 0.000000] percpu: Embedded 29 pages/cpu s78504 r8192 d32088 u118784
Sep 10 00:22:44 Loki kernel: [ 0.000000] pcpu-alloc: s78504 r8192 d32088 u118784 alloc=294096
Sep 10 00:22:44 Loki kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Sep 10 00:22:44 Loki kernel: [ 0.000000] Detected VIPT I-cache on CPU0
Sep 10 00:22:44 Loki systemd[1]: Finished Remount Root and Kernel File Systems.
Sep 10 00:22:44 Loki kernel: [ 0.000000] CPU features: kernel page table isolation forced ON by KASLR
Sep 10 00:22:44 Loki kernel: [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
Sep 10 00:22:44 Loki kernel: [ 0.000000] CPU features: detected: ARM erratum 843419
Sep 10 00:22:44 Loki kernel: [ 0.000000] CPU features: detected: ARM erratum 845719
Sep 10 00:22:44 Loki kernel: [ 0.000000] alternatives: applying boot alternatives
Sep 10 00:22:44 Loki kernel: [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 124992
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Sep 10 00:22:44 Loki kernel: [ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:05:78:C5 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000 console=tty1 root=PARTUUID=1c27ccc9-02 rootfstype=ext4 fsck.repair=yes rootwait modules-load=dwc2,g_ether
Sep 10 00:22:44 Loki kernel: [ 0.000000] Unknown kernel command line parameters "modules-load=dwc2,g_ether", will be passed to user space.
Sep 10 00:22:44 Loki kernel: [ 0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Sep 10 00:22:44 Loki kernel: [ 0.000000] Memory: 408760K/507904K available (11776K kernel code, 2106K rwdata, 3688K rodata, 4160K init, 1077K bss, 33608K reserved, 65536K cma-reserved)
Sep 10 00:22:44 Loki systemd[1]: Starting Flush Journal to Persistent Storage...
Sep 10 00:22:44 Loki kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Sep 10 00:22:44 Loki kernel: [ 0.000000] ftrace: allocating 39744 entries in 156 pages
Sep 10 00:22:44 Loki kernel: [ 0.000000] ftrace: allocated 156 pages with 4 groups
Sep 10 00:22:44 Loki kernel: [ 0.000000] trace event string verifier disabled
Sep 10 00:22:44 Loki kernel: [ 0.000000] rcu: Preemptible hierarchical RCU implementation.
Sep 10 00:22:44 Loki kernel: [ 0.000000] rcu: RCU event tracing is enabled.
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
Sep 10 00:22:44 Loki kernel: [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
Sep 10 00:22:44 Loki kernel: [ 0.000000] Trampoline variant of Tasks RCU enabled.
Sep 10 00:22:44 Loki kernel: [ 0.000000] Rude variant of Tasks RCU enabled.
Sep 10 00:22:44 Loki kernel: [ 0.000000] Tracing variant of Tasks RCU enabled.
Sep 10 00:22:44 Loki kernel: [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Sep 10 00:22:44 Loki kernel: [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Sep 10 00:22:44 Loki kernel: [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
Sep 10 00:22:44 Loki systemd[1]: Starting Load/Save Random Seed...
Sep 10 00:22:44 Loki kernel: [ 0.000000] Root IRQ handler: bcm2836_arm_irqchip_handle_irq
Sep 10 00:22:44 Loki kernel: [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
Sep 10 00:22:44 Loki kernel: [ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Sep 10 00:22:44 Loki kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Sep 10 00:22:44 Loki kernel: [ 0.000001] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Sep 10 00:22:44 Loki kernel: [ 0.000389] Console: colour dummy device 80x25
Sep 10 00:22:44 Loki systemd[1]: Starting Create System Users...
Sep 10 00:22:44 Loki kernel: [ 0.001412] printk: console [tty1] enabled
Sep 10 00:22:44 Loki kernel: [ 0.001499] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=76800)
Sep 10 00:22:44 Loki systemd[1]: Finished Set the console keyboard layout.
Sep 10 00:22:44 Loki kernel: [ 0.001567] pid_max: default: 32768 minimum: 301
Sep 10 00:22:44 Loki kernel: [ 0.001767] LSM: Security Framework initializing
Sep 10 00:22:44 Loki kernel: [ 0.002046] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.002109] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.004057] cgroup: Disabling memory control group subsystem
Sep 10 00:22:44 Loki kernel: [ 0.007313] cblist_init_generic: Setting adjustable number of callback queues.
Sep 10 00:22:44 Loki systemd[1]: Finished Coldplug All udev Devices.
Sep 10 00:22:44 Loki kernel: [ 0.007363] cblist_init_generic: Setting shift to 2 and lim to 1.
Sep 10 00:22:44 Loki kernel: [ 0.007658] cblist_init_generic: Setting shift to 2 and lim to 1.
Sep 10 00:22:44 Loki kernel: [ 0.008010] cblist_init_generic: Setting shift to 2 and lim to 1.
Sep 10 00:22:44 Loki kernel: [ 0.008684] rcu: Hierarchical SRCU implementation.
Sep 10 00:22:44 Loki kernel: [ 0.008723] rcu: Max phase no-delay instances is 1000.
Sep 10 00:22:44 Loki kernel: [ 0.010529] EFI services will not be available.
Sep 10 00:22:44 Loki kernel: [ 0.011313] smp: Bringing up secondary CPUs ...
Sep 10 00:22:44 Loki kernel: [ 0.013047] Detected VIPT I-cache on CPU1
Sep 10 00:22:44 Loki kernel: [ 0.013234] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
Sep 10 00:22:44 Loki systemd[1]: Starting Helper to synchronize boot up for ifupdown...
Sep 10 00:22:44 Loki kernel: [ 0.015001] Detected VIPT I-cache on CPU2
Sep 10 00:22:44 Loki kernel: [ 0.015146] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
Sep 10 00:22:44 Loki kernel: [ 0.016930] Detected VIPT I-cache on CPU3
Sep 10 00:22:44 Loki kernel: [ 0.017073] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
Sep 10 00:22:44 Loki kernel: [ 0.017305] smp: Brought up 1 node, 4 CPUs
Sep 10 00:22:44 Loki kernel: [ 0.017470] SMP: Total of 4 processors activated.
Sep 10 00:22:44 Loki systemd[1]: Finished Create System Users.
Sep 10 00:22:44 Loki kernel: [ 0.017506] CPU features: detected: 32-bit EL0 Support
Sep 10 00:22:44 Loki kernel: [ 0.017540] CPU features: detected: 32-bit EL1 Support
Sep 10 00:22:44 Loki kernel: [ 0.017577] CPU features: detected: CRC32 instructions
Sep 10 00:22:44 Loki kernel: [ 0.017775] CPU: All CPU(s) started at EL2
Sep 10 00:22:44 Loki kernel: [ 0.017826] alternatives: applying system-wide alternatives
Sep 10 00:22:44 Loki kernel: [ 0.020426] devtmpfs: initialized
Sep 10 00:22:44 Loki systemd[1]: Finished Load/Save Random Seed.
Sep 10 00:22:44 Loki kernel: [ 0.044851] Enabled cp15_barrier support
Sep 10 00:22:44 Loki kernel: [ 0.044939] Enabled setend support
Sep 10 00:22:44 Loki kernel: [ 0.045283] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Sep 10 00:22:44 Loki kernel: [ 0.045360] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in First Boot Complete being skipped.
Sep 10 00:22:44 Loki kernel: [ 0.048881] pinctrl core: initialized pinctrl subsystem
Sep 10 00:22:44 Loki kernel: [ 0.050240] DMI not present or invalid.
Sep 10 00:22:44 Loki kernel: [ 0.051294] NET: Registered PF_NETLINK/PF_ROUTE protocol family
Sep 10 00:22:44 Loki kernel: [ 0.063376] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
Sep 10 00:22:44 Loki kernel: [ 0.063846] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Sep 10 00:22:44 Loki systemd[1]: Starting Create Static Device Nodes in /dev...
Sep 10 00:22:44 Loki kernel: [ 0.065427] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
Sep 10 00:22:44 Loki kernel: [ 0.065627] audit: initializing netlink subsys (disabled)
Sep 10 00:22:44 Loki kernel: [ 0.066094] audit: type=2000 audit(0.064:1): state=initialized audit_enabled=0 res=1
Sep 10 00:22:44 Loki kernel: [ 0.067116] thermal_sys: Registered thermal governor 'step_wise'
Sep 10 00:22:44 Loki kernel: [ 0.067252] cpuidle: using governor menu
Sep 10 00:22:44 Loki kernel: [ 0.067934] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Sep 10 00:22:44 Loki systemd-modules-load[143]: Inserted module 'dwc2'
Sep 10 00:22:44 Loki kernel: [ 0.068258] ASID allocator initialised with 32768 entries
Sep 10 00:22:44 Loki kernel: [ 0.068596] Serial: AMBA PL011 UART driver
Sep 10 00:22:44 Loki kernel: [ 0.081804] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Sep 10 00:22:44 Loki kernel: [ 0.100538] raspberrypi-firmware soc:firmware: Attached to firmware from 2023-03-17T10:53:00, variant start_cd
Sep 10 00:22:44 Loki kernel: [ 0.104558] raspberrypi-firmware soc:firmware: Firmware hash is 82f3750a65fadae9a38077e3c2e217ad158c8d54
Sep 10 00:22:44 Loki systemd[1]: Finished Helper to synchronize boot up for ifupdown.
Sep 10 00:22:44 Loki kernel: [ 0.116732] KASLR enabled
Sep 10 00:22:44 Loki kernel: [ 0.169301] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Sep 10 00:22:44 Loki kernel: [ 0.175814] SCSI subsystem initialized
Sep 10 00:22:44 Loki kernel: [ 0.176224] usbcore: registered new interface driver usbfs
Sep 10 00:22:44 Loki kernel: [ 0.176343] usbcore: registered new interface driver hub
Sep 10 00:22:44 Loki kernel: [ 0.176473] usbcore: registered new device driver usb
Sep 10 00:22:44 Loki kernel: [ 0.177043] usb_phy_generic phy: supply vcc not found, using dummy regulator
Sep 10 00:22:44 Loki kernel: [ 0.177419] usb_phy_generic phy: dummy supplies not allowed for exclusive requests
Sep 10 00:22:44 Loki systemd-modules-load[143]: Inserted module 'g_ether'
Sep 10 00:22:44 Loki kernel: [ 0.178025] pps_core: LinuxPPS API ver. 1 registered
Sep 10 00:22:44 Loki kernel: [ 0.178065] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [email protected]
Sep 10 00:22:44 Loki systemd[1]: Finished Create Static Device Nodes in /dev.
Sep 10 00:22:44 Loki systemd[1]: Finished Load Kernel Modules.
Sep 10 00:22:44 Loki systemd[1]: Reached target Local File Systems (Pre).
Sep 10 00:22:44 Loki systemd[1]: Starting Apply Kernel Variables...
Sep 10 00:22:44 Loki systemd[1]: Starting Rule-based Manager for Device Events and Files...
Sep 10 00:22:44 Loki systemd[1]: Finished Apply Kernel Variables.
Sep 10 00:22:44 Loki systemd[1]: Finished Flush Journal to Persistent Storage.
Sep 10 00:22:44 Loki systemd[1]: Started Rule-based Manager for Device Events and Files.
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Huge Pages File System being skipped.
Sep 10 00:22:44 Loki kernel: [ 0.178136] PTP clock support registered
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
Sep 10 00:22:44 Loki kernel: [ 0.179973] vgaarb: loaded
Sep 10 00:22:44 Loki kernel: [ 0.181097] clocksource: Switched to clocksource arch_sys_counter
Sep 10 00:22:44 Loki kernel: [ 0.182710] VFS: Disk quotas dquot_6.6.0
Sep 10 00:22:44 Loki kernel: [ 0.182857] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Sep 10 00:22:44 Loki kernel: [ 0.183186] FS-Cache: Loaded
Sep 10 00:22:44 Loki kernel: [ 0.183510] CacheFiles: Loaded
Sep 10 00:22:44 Loki kernel: [ 0.200312] NET: Registered PF_INET protocol family
Sep 10 00:22:44 Loki kernel: [ 0.200690] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.202809] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.202888] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.202955] TCP established hash table entries: 4096 (order: 3, 32768 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.203064] TCP bind hash table entries: 4096 (order: 5, 131072 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.203286] TCP: Hash tables configured (established 4096 bind 4096)
Sep 10 00:22:44 Loki kernel: [ 0.203509] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
Sep 10 00:22:44 Loki kernel: [ 0.203583] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
Sep 10 00:22:44 Loki kernel: [ 0.203931] NET: Registered PF_UNIX/PF_LOCAL protocol family
Sep 10 00:22:44 Loki kernel: [ 0.205016] RPC: Registered named UNIX socket transport module.
Sep 10 00:22:44 Loki kernel: [ 0.205104] RPC: Registered udp transport module.
Sep 10 00:22:44 Loki kernel: [ 0.205142] RPC: Registered tcp transport module.
Sep 10 00:22:44 Loki kernel: [ 0.205176] RPC: Registered tcp NFSv4.1 backchannel transport module.
Sep 10 00:22:44 Loki systemd[1]: Found device /dev/disk/by-partuuid/1c27ccc9-01.
Sep 10 00:22:44 Loki kernel: [ 0.205233] PCI: CLS 0 bytes, default 64
Sep 10 00:22:44 Loki kernel: [ 0.207740] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
Sep 10 00:22:44 Loki kernel: [ 0.208193] kvm [1]: IPA Size Limit: 40 bits
Sep 10 00:22:44 Loki kernel: [ 0.210084] kvm [1]: Hyp mode initialized successfully
Sep 10 00:22:44 Loki kernel: [ 1.994355] Initialise system trusted keyrings
Sep 10 00:22:44 Loki systemd[1]: Starting File System Check on /dev/disk/by-partuuid/1c27ccc9-01...
Sep 10 00:22:44 Loki kernel: [ 1.995056] workingset: timestamp_bits=46 max_order=17 bucket_order=0
Sep 10 00:22:44 Loki kernel: [ 2.008519] zbud: loaded
Sep 10 00:22:44 Loki kernel: [ 2.013409] NFS: Registering the id_resolver key type
Sep 10 00:22:44 Loki kernel: [ 2.013509] Key type id_resolver registered
Sep 10 00:22:44 Loki kernel: [ 2.013546] Key type id_legacy registered
Sep 10 00:22:44 Loki kernel: [ 2.013748] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Sep 10 00:22:44 Loki systemd-fsck[216]: fsck.fat 4.2 (2021-01-31)
Sep 10 00:22:44 Loki kernel: [ 2.013797] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
Sep 10 00:22:44 Loki kernel: [ 2.016047] Key type asymmetric registered
Sep 10 00:22:44 Loki kernel: [ 2.016094] Asymmetric key parser 'x509' registered
Sep 10 00:22:44 Loki kernel: [ 2.016242] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
Sep 10 00:22:44 Loki systemd-fsck[216]: /dev/mmcblk0p1: 325 files, 15692/130554 clusters
Sep 10 00:22:44 Loki kernel: [ 2.016713] io scheduler mq-deadline registered
Sep 10 00:22:44 Loki kernel: [ 2.016759] io scheduler kyber registered
Sep 10 00:22:44 Loki kernel: [ 2.025297] bcm2708_fb soc:fb: FB found 1 display(s)
Sep 10 00:22:44 Loki kernel: [ 2.037638] Console: switching to colour frame buffer device 90x30
Sep 10 00:22:44 Loki kernel: [ 2.041290] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 720x480
Sep 10 00:22:44 Loki kernel: [ 2.052422] bcm2835-rng 3f104000.rng: hwrng registered
Sep 10 00:22:44 Loki systemd[1]: Finished File System Check on /dev/disk/by-partuuid/1c27ccc9-01.
Sep 10 00:22:44 Loki kernel: [ 2.054634] vc-mem: phys_addr:0x00000000 mem_base=0x1fa00000 mem_size:0x20000000(512 MiB)
Sep 10 00:22:44 Loki kernel: [ 2.059066] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Sep 10 00:22:44 Loki kernel: [ 2.081245] brd: module loaded
Sep 10 00:22:44 Loki kernel: [ 2.096641] loop: module loaded
Sep 10 00:22:44 Loki kernel: [ 2.098895] Loading iSCSI transport class v2.0-870.
Sep 10 00:22:44 Loki systemd[1]: Mounting /boot...
Sep 10 00:22:44 Loki kernel: [ 2.107630] usbcore: registered new interface driver r8152
Sep 10 00:22:44 Loki kernel: [ 2.108964] usbcore: registered new interface driver lan78xx
Sep 10 00:22:44 Loki kernel: [ 2.110233] usbcore: registered new interface driver smsc95xx
Sep 10 00:22:44 Loki kernel: [ 2.112001] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Sep 10 00:22:44 Loki systemd[1]: Mounted /boot.
Sep 10 00:22:44 Loki kernel: [ 2.113490] dwc_otg: FIQ enabled
Sep 10 00:22:44 Loki kernel: [ 2.113507] dwc_otg: NAK holdoff enabled
Sep 10 00:22:44 Loki kernel: [ 2.113523] dwc_otg: FIQ split-transaction FSM enabled
Sep 10 00:22:44 Loki kernel: [ 2.113549] Module dwc_common_port init
Sep 10 00:22:44 Loki kernel: [ 2.114275] usbcore: registered new interface driver uas
Sep 10 00:22:44 Loki kernel: [ 2.115530] usbcore: registered new interface driver usb-storage
Sep 10 00:22:44 Loki kernel: [ 2.117029] mousedev: PS/2 mouse device common for all mice
Sep 10 00:22:44 Loki systemd[1]: Reached target Local File Systems.
Sep 10 00:22:44 Loki kernel: [ 2.124014] sdhci: Secure Digital Host Controller Interface driver
Sep 10 00:22:44 Loki kernel: [ 2.125202] sdhci: Copyright(c) Pierre Ossman
Sep 10 00:22:44 Loki kernel: [ 2.127031] sdhci-pltfm: SDHCI platform and OF driver helper
Sep 10 00:22:44 Loki kernel: [ 2.130435] ledtrig-cpu: registered to indicate activity on CPUs
Sep 10 00:22:44 Loki systemd[1]: Starting Set console font and keymap...
Sep 10 00:22:44 Loki kernel: [ 2.132026] hid: raw HID events driver (C) Jiri Kosina
Sep 10 00:22:44 Loki kernel: [ 2.133408] usbcore: registered new interface driver usbhid
Sep 10 00:22:44 Loki kernel: [ 2.134505] usbhid: USB HID core driver
Sep 10 00:22:44 Loki kernel: [ 2.135900] bcm2835_vchiq 3f00b840.mailbox: there is not valid maps for state default
Sep 10 00:22:44 Loki kernel: [ 2.145592] NET: Registered PF_PACKET protocol family
Sep 10 00:22:44 Loki kernel: [ 2.146952] Key type dns_resolver registered
Sep 10 00:22:44 Loki systemd[1]: Starting Raise network interfaces...
Sep 10 00:22:44 Loki kernel: [ 2.150285] registered taskstats version 1
Sep 10 00:22:44 Loki kernel: [ 2.151493] Loading compiled-in X.509 certificates
Sep 10 00:22:44 Loki kernel: [ 2.153923] Key type .fscrypt registered
Sep 10 00:22:44 Loki kernel: [ 2.154972] Key type fscrypt-provisioning registered
Sep 10 00:22:44 Loki kernel: [ 2.183507] uart-pl011 3f201000.serial: cts_event_workaround enabled
Sep 10 00:22:44 Loki kernel: [ 2.184795] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 99, base_baud = 0) is a PL011 rev2
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Sep 10 00:22:44 Loki kernel: [ 2.192287] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Sep 10 00:22:44 Loki kernel: [ 2.194180] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Sep 10 00:22:44 Loki kernel: [ 2.198503] sdhost: log_buf @ 000000005f536df2 (c2f65000)
Sep 10 00:22:44 Loki kernel: [ 2.250647] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Sep 10 00:22:44 Loki kernel: [ 2.257046] of_cfs_init
Sep 10 00:22:44 Loki kernel: [ 2.258466] of_cfs_init: OK
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Sep 10 00:22:44 Loki kernel: [ 2.261492] Waiting for root device PARTUUID=1c27ccc9-02...
Sep 10 00:22:44 Loki kernel: [ 2.284272] mmc0: host does not support reading read-only switch, assuming write-enable
Sep 10 00:22:44 Loki kernel: [ 2.290365] mmc0: new high speed SDXC card at address 59b4
Sep 10 00:22:44 Loki kernel: [ 2.293135] mmcblk0: mmc0:59b4 LX128 118 GiB
Sep 10 00:22:44 Loki kernel: [ 2.298981] mmcblk0: p1 p2
Sep 10 00:22:44 Loki kernel: [ 2.300945] mmcblk0: mmc0:59b4 LX128 118 GiB
Sep 10 00:22:44 Loki kernel: [ 2.342094] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
Sep 10 00:22:44 Loki kernel: [ 2.344604] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Sep 10 00:22:44 Loki kernel: [ 2.354899] devtmpfs: mounted
Sep 10 00:22:44 Loki kernel: [ 2.368643] Freeing unused kernel memory: 4160K
Sep 10 00:22:44 Loki kernel: [ 2.370161] Run /sbin/init as init process
Sep 10 00:22:44 Loki systemd[1]: Starting Create Volatile Files and Directories...
Sep 10 00:22:44 Loki kernel: [ 2.371358] with arguments:
Sep 10 00:22:44 Loki kernel: [ 2.371373] /sbin/init
Sep 10 00:22:44 Loki systemd[1]: Finished Set console font and keymap.
Sep 10 00:22:44 Loki kernel: [ 2.371389] with environment:
Sep 10 00:22:44 Loki kernel: [ 2.371403] HOME=/
Sep 10 00:22:44 Loki kernel: [ 2.371419] TERM=linux
Sep 10 00:22:44 Loki systemd[1]: Reached target Hardware activated USB gadget.
Sep 10 00:22:44 Loki kernel: [ 2.371434] modules-load=dwc2,g_ether
Sep 10 00:22:44 Loki kernel: [ 3.280284] NET: Registered PF_INET6 protocol family
Sep 10 00:22:44 Loki kernel: [ 3.284265] Segment Routing with IPv6
Sep 10 00:22:44 Loki kernel: [ 3.285641] In-situ OAM (IOAM) with IPv6
Sep 10 00:22:44 Loki systemd-udevd[176]: Using default interface naming scheme 'v247'.
Sep 10 00:22:44 Loki mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1"
Sep 10 00:22:44 Loki mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Sep 10 00:22:44 Loki mtp-probe: bus: 1, device: 3 was not an MTP device
Sep 10 00:22:44 Loki mtp-probe: bus: 1, device: 4 was not an MTP device
Sep 10 00:22:44 Loki systemd[1]: Finished Raise network interfaces.
Sep 10 00:22:44 Loki systemd[1]: Finished Create Volatile Files and Directories.
Sep 10 00:22:44 Loki systemd[1]: Found device /sys/subsystem/net/devices/usb0.
Sep 10 00:22:44 Loki systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Sep 10 00:22:44 Loki kernel: [ 4.852472] fuse: init (API version 7.37)
Sep 10 00:22:44 Loki kernel: [ 5.535110] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.
Sep 10 00:22:44 Loki kernel: [ 5.602771] dwc2 3f980000.usb: supply vusb_d not found, using dummy regulator
Sep 10 00:22:44 Loki kernel: [ 5.604533] dwc2 3f980000.usb: supply vusb_a not found, using dummy regulator
Sep 10 00:22:44 Loki kernel: [ 5.821384] dwc2 3f980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM
Sep 10 00:22:44 Loki kernel: [ 5.821920] dwc2 3f980000.usb: DWC OTG Controller
Sep 10 00:22:44 Loki systemd[1]: Started ifup for usb0.
Sep 10 00:22:44 Loki kernel: [ 5.824445] dwc2 3f980000.usb: new USB bus registered, assigned bus number 1
Sep 10 00:22:44 Loki systemd[1]: Reached target Network.
Sep 10 00:22:44 Loki kernel: [ 5.824534] dwc2 3f980000.usb: irq 51, io mem 0x3f980000
Sep 10 00:22:44 Loki kernel: [ 5.827865] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
Sep 10 00:22:44 Loki kernel: [ 5.830468] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 10 00:22:44 Loki kernel: [ 5.831794] usb usb1: Product: DWC OTG Controller
Sep 10 00:22:44 Loki kernel: [ 5.833289] usb usb1: Manufacturer: Linux 6.1.21-v8+ dwc2_hsotg
Sep 10 00:22:44 Loki kernel: [ 5.834606] usb usb1: SerialNumber: 3f980000.usb
Sep 10 00:22:44 Loki systemd[1]: Reached target Network is Online.
Sep 10 00:22:44 Loki kernel: [ 5.837241] hub 1-0:1.0: USB hub found
Sep 10 00:22:44 Loki mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Sep 10 00:22:44 Loki kernel: [ 5.838704] hub 1-0:1.0: 1 port detected
Sep 10 00:22:44 Loki kernel: [ 5.916201] using random self ethernet address
Sep 10 00:22:44 Loki kernel: [ 5.917638] using random host ethernet address
Sep 10 00:22:44 Loki kernel: [ 5.920053] usb0: HOST MAC 7a:b6:0b:7b:cb:b3
Sep 10 00:22:44 Loki kernel: [ 5.921337] usb0: MAC 2e:62:f3:5a:5b:5d
Sep 10 00:22:44 Loki mtp-probe: bus: 1, device: 4 was not an MTP device
Sep 10 00:22:44 Loki kernel: [ 5.922750] using random self ethernet address
Sep 10 00:22:44 Loki kernel: [ 5.923916] using random host ethernet address
Sep 10 00:22:44 Loki kernel: [ 5.925138] g_ether gadget.0: Ethernet Gadget, version: Memorial Day 2008
Sep 10 00:22:44 Loki kernel: [ 5.926228] g_ether gadget.0: g_ether ready
Sep 10 00:22:44 Loki kernel: [ 5.927282] dwc2 3f980000.usb: bound driver g_ether
Sep 10 00:22:44 Loki kernel: [ 6.141154] usb 1-1: new high-speed USB device number 2 using dwc2
Sep 10 00:22:44 Loki systemd[1]: Starting Network Time Synchronization...
Sep 10 00:22:44 Loki kernel: [ 6.356425] usb 1-1: New USB device found, idVendor=2109, idProduct=2812, bcdDevice= b.e0
Sep 10 00:22:44 Loki kernel: [ 6.356476] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 10 00:22:44 Loki kernel: [ 6.356501] usb 1-1: Product: USB2.0 Hub
Sep 10 00:22:44 Loki kernel: [ 6.356676] usb 1-1: Manufacturer: VIA Labs, Inc.
Sep 10 00:22:44 Loki kernel: [ 6.358928] hub 1-1:1.0: USB hub found
Sep 10 00:22:44 Loki systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Sep 10 00:22:44 Loki kernel: [ 6.359385] hub 1-1:1.0: 4 ports detected
Sep 10 00:22:44 Loki kernel: [ 6.669195] usb 1-1.1: new high-speed USB device number 3 using dwc2
Sep 10 00:22:44 Loki systemd[1]: Finished Update UTMP about System Boot/Shutdown.
Sep 10 00:22:44 Loki kernel: [ 6.783244] usb 1-1.1: New USB device found, idVendor=0bda, idProduct=0811, bcdDevice= 2.00
Sep 10 00:22:44 Loki kernel: [ 6.783297] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 10 00:22:44 Loki kernel: [ 6.783321] usb 1-1.1: Product: 802.11ac WLAN Adapter
Sep 10 00:22:44 Loki kernel: [ 6.783343] usb 1-1.1: Manufacturer: Realtek
Sep 10 00:22:44 Loki kernel: [ 6.783364] usb 1-1.1: SerialNumber: 00e04c000001
Sep 10 00:22:44 Loki sh[356]: usb0=usb0
Sep 10 00:22:44 Loki kernel: [ 6.953223] usb 1-1.3: new high-speed USB device number 4 using dwc2
Sep 10 00:22:44 Loki systemd[1]: Found device RTL8153 Gigabit Ethernet Adapter.
Sep 10 00:22:44 Loki kernel: [ 7.067754] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
Sep 10 00:22:44 Loki kernel: [ 7.067810] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Sep 10 00:22:44 Loki kernel: [ 7.067836] usb 1-1.3: Product: USB 10/100/1000 LAN
Sep 10 00:22:44 Loki kernel: [ 7.067857] usb 1-1.3: Manufacturer: Realtek
Sep 10 00:22:44 Loki kernel: [ 7.067878] usb 1-1.3: SerialNumber: 000001000000
Sep 10 00:22:44 Loki systemd[1]: Started ifup for eth0.
Sep 10 00:22:44 Loki kernel: [ 7.197263] usb 1-1.3: reset high-speed USB device number 4 using dwc2
Sep 10 00:22:44 Loki dhclient[370]: Internet Systems Consortium DHCP Client 4.4.1
Sep 10 00:22:44 Loki kernel: [ 7.239678] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
Sep 10 00:22:44 Loki kernel: [ 7.243388] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Sep 10 00:22:44 Loki kernel: [ 7.243446] [vc_sm_connected_init]: start
Sep 10 00:22:44 Loki kernel: [ 7.249225] vc_sm_cma_vchi_init: failed to open VCHI service (-1)
Sep 10 00:22:44 Loki kernel: [ 7.249264] [vc_sm_connected_init]: failed to initialize shared memory service
Sep 10 00:22:44 Loki kernel: [ 7.277938] mc: Linux media interface: v0.10
Sep 10 00:22:44 Loki kernel: [ 7.376625] r8152 1-1.3:1.0: load rtl8153a-3 v2 02/07/20 successfully
Sep 10 00:22:44 Loki sh[370]: Internet Systems Consortium DHCP Client 4.4.1
Sep 10 00:22:44 Loki kernel: [ 7.411887] r8152 1-1.3:1.0 eth0: v1.12.13
Sep 10 00:22:44 Loki kernel: [ 7.472556] videodev: Linux video capture interface: v2.00
Sep 10 00:22:44 Loki kernel: [ 7.485375] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Sep 10 00:22:44 Loki kernel: [ 7.563189] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Sep 10 00:22:44 Loki kernel: [ 7.588732] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Sep 10 00:22:44 Loki sh[370]: Copyright 2004-2018 Internet Systems Consortium.
Sep 10 00:22:44 Loki kernel: [ 7.603071] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
Sep 10 00:22:44 Loki sh[370]: All rights reserved.
Sep 10 00:22:44 Loki kernel: [ 7.623849] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
Sep 10 00:22:44 Loki kernel: [ 7.628557] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
Sep 10 00:22:44 Loki kernel: [ 7.632026] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
Sep 10 00:22:44 Loki kernel: [ 7.642212] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
Sep 10 00:22:44 Loki kernel: [ 7.661548] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
Sep 10 00:22:44 Loki sh[370]: For info, please visit https://www.isc.org/software/dhcp/
Sep 10 00:22:44 Loki kernel: [ 7.661806] : Unregister from media controller
Sep 10 00:22:44 Loki kernel: [ 7.661834] (efault): Unregistering node (null)[0] device node /dev/video0
Sep 10 00:22:44 Loki kernel: [ 7.661874] (efault): Unregistering node (null)[0] device node /dev/video0
Sep 10 00:22:44 Loki kernel: [ 7.661896] (efault): Unregistering node (null)[0] device node /dev/video0
Sep 10 00:22:44 Loki dhclient[370]: Copyright 2004-2018 Internet Systems Consortium.
Sep 10 00:22:44 Loki kernel: [ 7.661916] (efault): Unregistering node (null)[0] device node /dev/video0
Sep 10 00:22:44 Loki kernel: [ 8.749899] rtc-ds1307: probe of 1-0068 failed with error -121
Sep 10 00:22:44 Loki kernel: [ 8.906309] usbcore: registered new interface driver cdc_ether
Sep 10 00:22:44 Loki dhclient[370]: All rights reserved.
Sep 10 00:22:44 Loki kernel: [ 8.911768] usbcore: registered new interface driver r8153_ecm
Sep 10 00:22:44 Loki kernel: [ 9.159572] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Sep 10 00:22:44 Loki kernel: [ 9.212932] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Sep 10 00:22:44 Loki kernel: [ 9.224476] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
Sep 10 00:22:44 Loki dhclient[370]: For info, please visit https://www.isc.org/software/dhcp/
Sep 10 00:22:44 Loki kernel: [ 9.800468] 88XXau: loading out-of-tree module taints kernel.
Sep 10 00:22:44 Loki kernel: [ 10.148562] usb 1-1.1: 88XXau 00:c0:ca:b1:6e:a9 hw_info[107]
Sep 10 00:22:44 Loki kernel: [ 10.172834] usbcore: registered new interface driver rtl88XXau
Sep 10 00:22:44 Loki kernel: [ 10.579345] uart-pl011 3f201000.serial: no DMA platform data
Sep 10 00:22:44 Loki dhclient[370]:
Sep 10 00:22:44 Loki systemd[1]: Started Network Time Synchronization.
Sep 10 00:22:44 Loki systemd[1]: Reached target System Initialization.
Sep 10 00:22:44 Loki systemd[1]: Started Daily Cleanup of Temporary Directories.
Sep 10 00:22:44 Loki systemd[1]: Reached target System Time Set.
Sep 10 00:22:44 Loki systemd[1]: Reached target System Time Synchronized.
Sep 10 00:22:44 Loki systemd[1]: Started Daily apt download activities.
Sep 10 00:22:44 Loki systemd[1]: Started Daily apt upgrade and clean activities.
Sep 10 00:22:44 Loki systemd[1]: Started Periodic ext4 Online Metadata Check for All Filesystems.
Sep 10 00:22:44 Loki systemd[1]: Started Daily exim4-base housekeeping.
Sep 10 00:22:44 Loki systemd[1]: Started Discard unused blocks once a week.
Sep 10 00:22:44 Loki systemd[1]: Started Daily rotation of log files.
Sep 10 00:22:44 Loki systemd[1]: Started Daily man-db regeneration.
Sep 10 00:22:44 Loki systemd[1]: Reached target Timers.
Sep 10 00:22:44 Loki systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Sep 10 00:22:44 Loki systemd[1]: Listening on D-Bus System Message Bus Socket.
Sep 10 00:22:44 Loki systemd[1]: Reached target Sockets.
Sep 10 00:22:44 Loki systemd[1]: Reached target Basic System.
Sep 10 00:22:44 Loki dhclient[370]: Listening on LPF/eth0/00:e0:8f:00:4a:aa
Sep 10 00:22:44 Loki sh[370]: Listening on LPF/eth0/00:e0:8f:00:4a:aa
Sep 10 00:22:44 Loki sh[370]: Sending on LPF/eth0/00:e0:8f:00:4a:aa
Sep 10 00:22:44 Loki sh[370]: Sending on Socket/fallback
Sep 10 00:22:44 Loki sh[370]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Sep 10 00:22:44 Loki dhclient[370]: Sending on LPF/eth0/00:e0:8f:00:4a:aa
Sep 10 00:22:44 Loki dhclient[370]: Sending on Socket/fallback
Sep 10 00:22:44 Loki dhclient[370]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Sep 10 00:22:44 Loki systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Sep 10 00:22:44 Loki systemd[1]: Started bettercap api.rest service..
Sep 10 00:22:44 Loki systemd[1]: Started Regular background program processing daemon.
Sep 10 00:22:44 Loki systemd[1]: Started D-Bus System Message Bus.
Sep 10 00:22:44 Loki cron[381]: (CRON) INFO (pidfile fd = 3)
Sep 10 00:22:44 Loki systemd[1]: Starting dphys-swapfile - set up, mount/unmount, and delete a swap file...
Sep 10 00:22:44 Loki cron[381]: (CRON) INFO (Running @reboot jobs)
Sep 10 00:22:44 Loki avahi-daemon[379]: Found user 'avahi' (UID 108) and group 'avahi' (GID 113).
Sep 10 00:22:44 Loki avahi-daemon[379]: Successfully dropped root privileges.
Sep 10 00:22:44 Loki avahi-daemon[379]: avahi-daemon 0.8 starting up.
Sep 10 00:22:44 Loki systemd[1]: Starting Remove Stale Online ext4 Metadata Check Snapshots...
Sep 10 00:22:44 Loki systemd[1]: Starting LSB: exim Mail Transport Agent...
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped.
Sep 10 00:22:44 Loki systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Sep 10 00:22:44 Loki systemd[1]: Starting Authorization Manager...
Sep 10 00:22:44 Loki systemd[1]: Started pwngrid peer service..
Sep 10 00:22:44 Loki systemd[1]: Started pwnagotchi Deep Reinforcement Learning instrumenting bettercap for WiFI pwning..
Sep 10 00:22:44 Loki systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)...
Sep 10 00:22:44 Loki systemd[1]: Starting /etc/rc.local Compatibility...
Sep 10 00:22:44 Loki systemd[1]: Starting LSB: rng-tools (Debian variant)...
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.
Sep 10 00:22:44 Loki systemd[1]: Starting System Logging Service...
Sep 10 00:22:44 Loki mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1"
Sep 10 00:22:44 Loki mtp-probe: bus: 1, device: 3 was not an MTP device
Sep 10 00:22:44 Loki systemd[1]: Starting OpenBSD Secure Shell server...
Sep 10 00:22:44 Loki systemd[1]: Condition check resulted in Turn on SSH if /boot/ssh is present being skipped.
Sep 10 00:22:44 Loki systemd-udevd[180]: Using default interface naming scheme 'v247'.
Sep 10 00:22:44 Loki avahi-daemon[379]: Successfully called chroot().
Sep 10 00:22:44 Loki avahi-daemon[379]: Successfully dropped remaining capabilities.
Sep 10 00:22:44 Loki avahi-daemon[379]: No service file found in /etc/avahi/services.
Sep 10 00:22:44 Loki avahi-daemon[379]: Joining mDNS multicast group on interface usb0.IPv4 with address 10.0.0.2.
Sep 10 00:22:44 Loki avahi-daemon[379]: New relevant interface usb0.IPv4 for mDNS.
Sep 10 00:22:44 Loki avahi-daemon[379]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Sep 10 00:22:44 Loki avahi-daemon[379]: New relevant interface lo.IPv6 for mDNS.
Sep 10 00:22:44 Loki avahi-daemon[379]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Sep 10 00:22:44 Loki avahi-daemon[379]: New relevant interface lo.IPv4 for mDNS.
Sep 10 00:22:44 Loki avahi-daemon[379]: Network interface enumeration completed.
Sep 10 00:22:44 Loki avahi-daemon[379]: Registering new address record for 10.0.0.2 on usb0.IPv4.
Sep 10 00:22:44 Loki avahi-daemon[379]: Registering new address record for ::1 on lo..
Sep 10 00:22:44 Loki avahi-daemon[379]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 10 00:22:44 Loki rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2102.0]
Sep 10 00:22:44 Loki rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="422" x-info="https://www.rsyslog.com"] start
Sep 10 00:22:44 Loki dphys-swapfile[386]: want /var/swap=1024MByte, checking existing: keeping it
Sep 10 00:22:44 Loki systemd[1]: Starting User Login Management...
Sep 10 00:22:44 Loki systemd[1]: Starting Permit User Sessions...
Sep 10 00:22:44 Loki systemd[1]: Started System Logging Service.
Sep 10 00:22:44 Loki systemd[1]: Started /etc/rc.local Compatibility.
Sep 10 00:22:44 Loki kernel: [ 11.216955] Adding 1048572k swap on /var/swap. Priority:-2 extents:10 across:4562944k SSFS
Sep 10 00:22:44 Loki kernel: [ 11.238455] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 10 00:22:44 Loki kernel: [ 11.239802] r8152 1-1.3:1.0 eth0: carrier on
Sep 10 00:22:44 Loki systemd[1]: Finished Permit User Sessions.
Sep 10 00:22:44 Loki systemd[1]: Finished dphys-swapfile - set up, mount/unmount, and delete a swap file.
Sep 10 00:22:44 Loki raspi-config[414]: Checking if shift key is held down: No. Switching to ondemand scaling governor.
Sep 10 00:22:44 Loki systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
Sep 10 00:22:44 Loki systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Sep 10 00:22:44 Loki systemd[1]: Started Getty on tty1.
Sep 10 00:22:44 Loki systemd[1]: Reached target Login Prompts.
Sep 10 00:22:44 Loki systemd[1]: Starting Load/Save RF Kill Switch Status...
Sep 10 00:22:44 Loki systemd[1]: Found device Realtek 8812AU/8821AU 802.11ac WLAN Adapter [USB Wireless Dual-Band Adapter 2.4/5Ghz].
Sep 10 00:22:44 Loki systemd[1]: Started ifup for wlan0.
Sep 10 00:22:44 Loki systemd[1]: Started Authorization Manager.
Sep 10 00:22:44 Loki polkitd[407]: started daemon version 0.105 using authority implementation local' version 0.105'
Sep 10 00:22:44 Loki sh[507]: ifup: missing required variable: address
Sep 10 00:22:44 Loki sh[507]: ifup: missing required configuration variables for interface wlan0/inet
Sep 10 00:22:44 Loki sh[507]: ifup: failed to bring up wlan0
Sep 10 00:22:44 Loki avahi-daemon[379]: Server startup complete. Host name is Loki.local. Local service cookie is 4251817222.
Sep 10 00:22:44 Loki rngd[525]: rngd 2.2 starting up...
Sep 10 00:22:44 Loki rngd[525]: entropy feed to the kernel ready
Sep 10 00:22:45 Loki systemd[1]: Starting Modem Manager...
Sep 10 00:22:45 Loki systemd[1]: Started Load/Save RF Kill Switch Status.
Sep 10 00:22:45 Loki systemd[1]: Started LSB: rng-tools (Debian variant).
Sep 10 00:22:45 Loki systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Sep 10 00:22:45 Loki systemd[1]: [email protected]: Failed with result 'exit-code'.
Sep 10 00:22:45 Loki systemd[1]: Started User Login Management.
Sep 10 00:22:45 Loki systemd[1]: Started OpenBSD Secure Shell server.
Sep 10 00:22:45 Loki ModemManager[543]: ModemManager (version 1.14.12) starting in system bus...
Sep 10 00:22:45 Loki avahi-daemon[379]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::2e0:8fff:fe00:4aaa.
Sep 10 00:22:45 Loki avahi-daemon[379]: New relevant interface eth0.IPv6 for mDNS.
Sep 10 00:22:45 Loki avahi-daemon[379]: Registering new address record for fe80::2e0:8fff:fe00:4aaa on eth0.*.
Sep 10 00:22:45 Loki dhclient[370]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Sep 10 00:22:45 Loki sh[370]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Sep 10 00:22:45 Loki dhclient[370]: DHCPOFFER of 192.168.137.109 from 192.168.137.1
Sep 10 00:22:45 Loki sh[370]: DHCPOFFER of 192.168.137.109 from 192.168.137.1
Sep 10 00:22:45 Loki sh[370]: DHCPREQUEST for 192.168.137.109 on eth0 to 255.255.255.255 port 67
Sep 10 00:22:45 Loki dhclient[370]: DHCPREQUEST for 192.168.137.109 on eth0 to 255.255.255.255 port 67
Sep 10 00:22:45 Loki dhclient[370]: DHCPACK of 192.168.137.109 from 192.168.137.1
Sep 10 00:22:45 Loki sh[370]: DHCPACK of 192.168.137.109 from 192.168.137.1
Sep 10 00:22:45 Loki avahi-daemon[379]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.137.109.
Sep 10 00:22:45 Loki avahi-daemon[379]: New relevant interface eth0.IPv4 for mDNS.
Sep 10 00:22:45 Loki avahi-daemon[379]: Registering new address record for 192.168.137.109 on eth0.IPv4.
Sep 10 00:22:59 Loki systemd-timesyncd[324]: Initial synchronization to time server 5.161.186.39:123 (0.debian.pool.ntp.org).
Sep 10 00:23:00 Loki avahi-daemon[379]: Got SIGHUP, reloading.
Sep 10 00:23:00 Loki systemd[1]: Started Modem Manager.
Sep 10 00:23:00 Loki avahi-daemon[379]: No service file found in /etc/avahi/services.
Sep 10 00:23:00 Loki dhclient[370]: bound to 192.168.137.109 -- renewal in 230526 seconds.
Sep 10 00:23:00 Loki sh[370]: bound to 192.168.137.109 -- renewal in 230526 seconds.
Sep 10 00:23:00 Loki sh[828]: eth0=eth0
Sep 10 00:23:01 Loki systemd[1]: pwngrid-peer.service: Main process exited, code=exited, status=1/FAILURE
Sep 10 00:23:01 Loki systemd[1]: pwngrid-peer.service: Failed with result 'exit-code'.
Sep 10 00:23:01 Loki systemd[1]: e2scrub_reap.service: Succeeded.
Sep 10 00:23:01 Loki systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
Sep 10 00:23:01 Loki rfkill: unblock set for all
Sep 10 00:23:02 Loki exim4[405]: Starting MTA: exim4.
Sep 10 00:23:02 Loki systemd[1]: Started LSB: exim Mail Transport Agent.
Sep 10 00:23:02 Loki systemd[1]: Reached target Multi-User System.
Sep 10 00:23:02 Loki systemd[1]: Starting Update UTMP about System Runlevel Changes...
Sep 10 00:23:02 Loki systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Sep 10 00:23:02 Loki systemd[1]: Finished Update UTMP about System Runlevel Changes.
Sep 10 00:23:02 Loki kernel: [ 15.645993] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep 10 00:23:02 Loki bettercap-launcher[861]: Found 3 processes that could cause trouble.
Sep 10 00:23:02 Loki bettercap-launcher[861]: Kill them using 'airmon-ng check kill' before putting
Sep 10 00:23:02 Loki bettercap-launcher[861]: the card in monitor mode, they will interfere by changing channels
Sep 10 00:23:02 Loki bettercap-launcher[861]: and sometimes putting the interface back in managed mode
Sep 10 00:23:02 Loki bettercap-launcher[907]: PID Name
Sep 10 00:23:02 Loki bettercap-launcher[907]: 370 dhclient
Sep 10 00:23:02 Loki bettercap-launcher[907]: 379 avahi-daemon
Sep 10 00:23:02 Loki bettercap-launcher[907]: 391 avahi-daemon
Sep 10 00:23:02 Loki bettercap-launcher[861]: PHY#011Interface#011Driver#011#011Chipset
Sep 10 00:23:02 Loki ModemManager[543]: [base-manager] couldn't check support for device '/sys/devices/platform/soc/3f980000.usb': not supported by any plugin
Sep 10 00:23:02 Loki ModemManager[543]: [base-manager] couldn't check support for device '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1': not supported by any plugin
Sep 10 00:23:02 Loki ModemManager[543]: [base-manager] couldn't check support for device '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3': not supported by any plugin
Sep 10 00:23:02 Loki bettercap-launcher[861]: phy0#011wlan0#011#01188XXau#011#011Realtek Semiconductor Corp. Realtek 8812AU/8821AU 802.11ac WLAN Adapter [USB Wireless Dual-Band Adapter 2.4/5Ghz]
Sep 10 00:23:02 Loki bettercap-launcher[861]: #11#011(monitor mode enabled)
Sep 10 00:23:03 Loki systemd[1]: systemd-rfkill.service: Succeeded.
Sep 10 00:23:03 Loki kernel: [ 17.214279] Bluetooth: Core ver 2.22
Sep 10 00:23:03 Loki kernel: [ 17.214422] NET: Registered PF_BLUETOOTH protocol family
Sep 10 00:23:03 Loki kernel: [ 17.214434] Bluetooth: HCI device and connection manager initialized
Sep 10 00:23:03 Loki kernel: [ 17.214465] Bluetooth: HCI socket layer initialized
Sep 10 00:23:03 Loki kernel: [ 17.214496] Bluetooth: L2CAP socket layer initialized
Sep 10 00:23:03 Loki kernel: [ 17.214530] Bluetooth: SCO socket layer initialized
Sep 10 00:23:04 Loki kernel: [ 17.253584] Bluetooth: HCI UART driver ver 2.3
Sep 10 00:23:04 Loki kernel: [ 17.253634] Bluetooth: HCI UART protocol H4 registered
Sep 10 00:23:04 Loki kernel: [ 17.253779] Bluetooth: HCI UART protocol Three-wire (H5) registered
Sep 10 00:23:04 Loki kernel: [ 17.254157] Bluetooth: HCI UART protocol Broadcom registered
Sep 10 00:23:04 Loki btuart[463]: bcm43xx_init
Sep 10 00:23:04 Loki btuart[463]: Flash firmware /lib/firmware/brcm/BCM43430A1.raspberrypi,model-zero-2-w.hcd
Sep 10 00:23:04 Loki btuart[463]: Set BDADDR UART: b8:27:eb:af:d2:6f
Sep 10 00:23:04 Loki btuart[463]: Set Controller UART speed to 3000000 bit/s
Sep 10 00:23:04 Loki btuart[463]: Device setup complete
Sep 10 00:23:04 Loki systemd[1]: Starting Load/Save RF Kill Switch Status...
Sep 10 00:23:04 Loki systemd[1]: Started Configure Bluetooth Modems connected by UART.
Sep 10 00:23:04 Loki systemd[1]: Started Load/Save RF Kill Switch Status.
Sep 10 00:23:04 Loki systemd[1]: Created slice system-bthelper.slice.
Sep 10 00:23:04 Loki systemd[1]: Starting Raspberry Pi bluetooth helper...
Sep 10 00:23:04 Loki bthelper[977]: Raspberry Pi BDADDR already set
Sep 10 00:23:04 Loki systemd[1]: Finished Raspberry Pi bluetooth helper.
Sep 10 00:23:04 Loki systemd[1]: Starting Bluetooth service...
Sep 10 00:23:04 Loki bettercap-launcher[956]: WARNING: Terminal colors have been disabled, view will be very limited.
Sep 10 00:23:04 Loki bettercap-launcher[956]: bettercap v2.32.1 (built for linux arm64 with go1.21.0) [type 'help' for a list of commands]
Sep 10 00:23:04 Loki bettercap-launcher[956]: no interface matching 'wlan0mon' found.
Sep 10 00:23:04 Loki systemd[1]: bettercap.service: Main process exited, code=exited, status=1/FAILURE
Sep 10 00:23:04 Loki systemd[1]: bettercap.service: Failed with result 'exit-code'.
Sep 10 00:23:04 Loki systemd[1]: bettercap.service: Consumed 1.491s CPU time.
Sep 10 00:23:04 Loki bluetoothd[987]: Bluetooth daemon 5.55
Sep 10 00:23:04 Loki systemd[1]: Started Bluetooth service.
Sep 10 00:23:04 Loki systemd[1]: Reached target Bluetooth.
Sep 10 00:23:04 Loki systemd[1]: Startup finished in 2.933s (kernel) + 15.072s (userspace) = 18.005s.
Sep 10 00:23:04 Loki bluetoothd[987]: Starting SDP server
Sep 10 00:23:04 Loki kernel: [ 18.070406] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 10 00:23:04 Loki kernel: [ 18.070438] Bluetooth: BNEP filters: protocol multicast
Sep 10 00:23:04 Loki kernel: [ 18.070469] Bluetooth: BNEP socket layer initialized
Sep 10 00:23:04 Loki dbus-daemon[382]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.7' (uid=0 pid=987 comm="/usr/libexec/bluetooth/bluetoothd ")
Sep 10 00:23:04 Loki kernel: [ 18.086777] Bluetooth: MGMT ver 1.22
Sep 10 00:23:04 Loki bluetoothd[987]: Bluetooth management interface 1.22 initialized
Sep 10 00:23:04 Loki kernel: [ 18.108943] NET: Registered PF_ALG protocol family
Sep 10 00:23:04 Loki systemd[1]: Starting Hostname Service...
Sep 10 00:23:05 Loki bluetoothd[987]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Sep 10 00:23:05 Loki bluetoothd[987]: sap-server: Operation not permitted (1)
Sep 10 00:23:05 Loki bluetoothd[987]: Failed to set privacy: Rejected (0x0b)
Sep 10 00:23:05 Loki dbus-daemon[382]: [system] Successfully activated service 'org.freedesktop.hostname1'
Sep 10 00:23:05 Loki systemd[1]: Started Hostname Service.
Sep 10 00:23:09 Loki systemd[1]: systemd-rfkill.service: Succeeded.
Sep 10 00:23:09 Loki bthelper[1024]: Changing power off succeeded
Sep 10 00:23:09 Loki bthelper[985]: Changing power on succeeded
Sep 10 00:23:15 Loki systemd[1]: Created slice User Slice of UID 1000.
Sep 10 00:23:15 Loki systemd[1]: Starting User Runtime Directory /run/user/1000...
Sep 10 00:23:15 Loki systemd[1]: Finished User Runtime Directory /run/user/1000.
Sep 10 00:23:15 Loki systemd[1]: Starting User Manager for UID 1000...
Sep 10 00:23:16 Loki systemd[1038]: Queued start job for default target Main User Target.
Sep 10 00:23:16 Loki systemd[1038]: Created slice User Application Slice.
Sep 10 00:23:16 Loki systemd[1038]: Reached target Paths.
Sep 10 00:23:16 Loki systemd[1038]: Reached target Timers.
Sep 10 00:23:16 Loki systemd[1038]: Listening on GnuPG network certificate management daemon.
Sep 10 00:23:16 Loki systemd[1038]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 10 00:23:16 Loki systemd[1038]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 10 00:23:16 Loki systemd[1038]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 10 00:23:16 Loki systemd[1038]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 10 00:23:16 Loki systemd[1038]: Reached target Sockets.
Sep 10 00:23:16 Loki systemd[1038]: Reached target Basic System.
Sep 10 00:23:16 Loki systemd[1038]: Reached target Main User Target.
Sep 10 00:23:16 Loki systemd[1038]: Startup finished in 554ms.
Sep 10 00:23:16 Loki systemd[1]: Started User Manager for UID 1000.
Sep 10 00:23:16 Loki systemd[1]: Started Session 1 of user pi.
Sep 10 00:23:24 Loki systemd[1]: systemd-fsckd.service: Succeeded.
Sep 10 00:23:31 Loki systemd[1]: pwngrid-peer.service: Scheduled restart job, restart counter is at 1.
Sep 10 00:23:31 Loki systemd[1]: Stopped pwngrid peer service..
Sep 10 00:23:31 Loki systemd[1]: Started pwngrid peer service..
Sep 10 00:23:33 Loki systemd[1]: pwngrid-peer.service: Main process exited, code=exited, status=1/FAILURE
Sep 10 00:23:33 Loki systemd[1]: pwngrid-peer.service: Failed with result 'exit-code'.

And successful injection test:

pi@Loki:~ $ sudo aireplay-ng -9 wlan0
00:28:37 Trying broadcast probe requests...
00:28:38 Injection is working!
00:28:39 Found 6 APs

00:28:39 Trying directed probe requests...
00:28:39 E8:9F:80:D9:75:48 - channel: 9 - 'SparkyBubbles'
00:28:39 Ping (min/avg/max): 2.463ms/11.210ms/68.044ms Power: -24.93
00:28:39 30/30: 100%

00:28:39 84:1E:A3:D7:61:E6 - channel: 11 - 'SpectrumSetup-E0'
00:28:44 Ping (min/avg/max): 3.041ms/6.570ms/12.839ms Power: -61.67
00:28:44 6/30: 20%

00:28:44 34:53:D2:CB:50:D7 - channel: 11 - 'SpectrumSetup-D1'
00:28:50 0/30: 0%

00:28:50 EE:9F:80:D9:75:48 - channel: 9 - ''
00:28:51 Ping (min/avg/max): 2.270ms/10.874ms/19.602ms Power: -25.07
00:28:51 30/30: 100%

00:28:51 08:36:C9:FE:DA:5D - channel: 8 - 'NightHawk'
00:28:52 Ping (min/avg/max): 2.222ms/8.989ms/41.809ms Power: -54.65
00:28:52 23/30: 76%

00:28:52 C8:99:B2:1C:28:DB - channel: 11 - 'Verizon_S6TVJP'
00:28:53 Ping (min/avg/max): 2.101ms/4.745ms/11.400ms Power: -57.00
00:28:53 25/30: 83%

Describe the bug
With Raspberry pi zero 2, under v2.5.2 cannot update through OS itself.

pwnlog:

[INFO] [update] turned off wifi recon...
[INFO] error 400: module wifi is not running
[ERROR] [update] error 400: module wifi is not running

To Reproduce
Steps to reproduce the behavior:

1. Boot up
2. sudo pwnagotchi --check-update
3. Check pwnlog

Expected behavior
Update the system as expected

Screenshots
N/A

Environment (please complete the following information):

• Pwnagotchi version: v.2.5.2
• OS version
• Type of hardware: RPi 02w
• Any additional hardware used: N/A

Running 2.3.5 on a Raspberry Pi Zero 2W, I saw the Wi-Fi driver "crash".

Would expect pwnagotchi to start incrementing blind count, so it would auto reboot itself based on this setting:

main.mon_max_blind_epochs = 50

pwnagotchi.log

Description
An error during initialization related to an observation space mismatch throws an exception that than deletes the saved model (brain.nn). It's not entirely clear where the observation space issue stems from, but having just lost a few weeks worth of training 24 hours a day, I have to say that this feels like a bug rather than a feature and doesn't seem like the best course of action given any exception. I'd think this should be handled via the "Fix_Services" plugin by trying a restart first or something, because this seems to have had happened for absolutely no reason after it was rebooted by the Fix_Services plugin. At the very least, we should make a copy of the previous brain.nn model save instead of permanently rm'ing it to the ether.

To Reproduce
It's not clear what steps are needed to repro, but in my case (see logs further below):

1. After Fix_Services plugin reboots due to pwnagotchi error, watch pwnlog for AI loading phase.
2. If any exceptions occur during loading phase, you'll see the log stating the brain.nn model save has been deleted.
3. If no exceptions occur, you can try to force it to happen (can't confirm this repro every time) by killing the three services bettercap, pwngrid-peer, pwnagotchi, and then starting them one by one individually.

Expected behavior
Either we need a more robust implementation for handling exceptions during the init phase which doesn't cause important saved model files to be deleted and restarted. If not, then we should make a copy of the brain.nn model file before removing it, in case there was an unrelated error causing the exception (in my case it was the observation space mismatch).

Logs

21:09:33 [INFO] found monitor interface: wlan0mon
21:09:33 [INFO] supported channels: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153]
21:09:33 [INFO] handshakes will be collected inside /root/handshakes
21:09:33 [INFO] [bettercap] creating new websocket...
21:09:33 [INFO] [epoch 0] duration=00:00:03 slept_for=00:00:00 blind=0 sad=0 bored=0 inactive=1 active=0 peers=0 tot_bond=0.00 avg_bond=0.00 hops=0 missed=0 deauths=0 assocs=0 handshakes=0 cpu=52% mem=20% temperature=36C reward=-0.2
21:09:36 [INFO] [Fix_Services ip link show wlan0mon]: b'4: wlan0mon: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000\n    link/ieee802.11/radiotap brd ff:ff:ff:ff:ff:ff\n'
21:09:36 [INFO] wlan0mon is up.
21:09:36 [INFO] [Fix_Services] Logs look good!
21:09:38 [WARNING] !!! captured new handshake on channel 6, -82 dBm: 74:40:be:75:b8:54 () -> SonarBG [a8:b0:88:48:50:88 (eero inc.)] !!!
21:09:52 [INFO] [AI] creating model ...
21:09:52 [INFO] [AI] loading /root/brain.nn ...
21:09:52 [ERROR] [AI] error while starting AI (Observation spaces do not match: Box(0.0, 1.0, (1, 428), float32) != Box(0.0, 1.0, (1, 503), float32))
(most recent call last):
 File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/ai/__init__.py", line 51, in load
   a2c.load(config['path'], env)
 File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/base_class.py", line 716, in load
   check_for_correct_spaces(env, data["observation_space"], data["action_space"])
 File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/utils.py", line 229, in check_for_correct_spaces
   raise ValueError(f"Observation spaces do not match: {observation_space} != {env.observation_space}")
Observation spaces do not match: Box(0.0, 1.0, (1, 428), float32) != Box(0.0, 1.0, (1, 503), float32)
21:09:52 [INFO] [AI] Deleting brain and restarting.
21:09:56 [INFO] [Fix_Services] plugin loaded.
21:09:56 [INFO] Logtail plugin loaded.

Environmen:

• Pwnagotchi version: 2.5.1
• OS version: Current image 2.5.4
• Type of hardware: Raspberry Pi 3B+

Describe the bug
Ran 2.4.9 on a Raspberry Pi 3B+, seem to work well enough, but after reimaging to 2.5.0, 3B+ won't start up anymore

To Reproduce
Steps to reproduce the behavior:

1. Installed 2.5.0

Expected behavior
Expect it just to work

Screenshots

Environment (please complete the following information):

• Pwnagotchi version 2.5.0
• OS version Linux pwnagotchi3b 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
• Type of hardware Raspberry Pi 3B+

pwnagotchi.log

Describe the bug
I used Raspberry Pi Imager v1.7.5, after choosing the 2.5.0 image, I set the setting to change the password under Advanced Options, but this password doesn't stick, and I have to use the default password to log in.

To Reproduce
Steps to reproduce the behavior:

1. ... Image with 2.5.0 with Raspberry Pi Imager v1.7.5
2. ... Click on Advanced Options in Raspberry Pi Imager, and set password
3. ... Try to log in with completed image with set password and it doesn't work (but default password you set works)

Expected behavior
I'm sure all versions before 2.5.0 worked, where I would set the password in Advanced Options

Screenshots

Environment (please complete the following information):

• Pwnagotchi version 2.5.0
• OS version Linux pwnagotchi4b 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
• Type of hardware Raspberry Pi 4B, 3B+, and 400 were all tested

Describe the bug
AI Brain parameter error

To Reproduce
Steps to reproduce the behavior:

1. Follow instructions
2. Update to 2.4.2

Expected behavior
Brain gets created

Environment (please complete the following information):

• Pwnagotchi version 2.4.2
• Type of hardware Pi0W 2

Additional context
16:20:56 [ERROR] error while starting AI (init() got an unexpected keyword argument 'alpha')
(most recent call last):
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/ai/init.py", line 62, in load
a2c = A2C(SB_A2C_POLICY, env, **config['params'])
init() got an unexpected keyword argument 'alpha'
16:20:56 [INFO] Deleting brain and restarting.
16:20:57 [WARNING] [ai] AI not loaded!

Describe the bug
Since update to 2.6.3 each call to pwnagotchi results in the following error message:

Traceback (most recent call last):
  File "/usr/local/bin/pwnagotchi", line 12, in <module>
    from pwnagotchi import utils
  File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/utils.py", line 168
    for boot_conf in ['/boot/config.yml', '/boot/firmware/config.yml', '/boot/config.toml', '/boot/firmware/config.toml']:
IndentationError: unexpected indent

The pwnagotchi service keeps on restarting due to this.
pwnlog is quiet in regards to this.

To Reproduce
Steps to reproduce the behavior:

1. Fresh image with versin 2.5.4, update to 2.6.3
2. try any sudo pwnagotchi command

Expected behavior
Working pwnagotchi.

Describe the bug
Grid might throw an error about missing tcpdump. I have grid disabled on my tester pi, so I never noticed this issue.

To Reproduce
Steps to reproduce the behavior:

1. enable grid plugin

Expected behavior
Run pwnagotchi with grid enabled, no errors

Environment (please complete the following information):

• Pwnagotchi version 2.5.1
• OS version bullseye 6.1.21

Additional context
Installation instructions:

sudo apt-get install tcpdump

Describe the bug
A clear and concise description of what the bug is.
brain.nn not being created at all. It gos into AI mode but brain.nn is not in /root/

I get this in the log when runing pwnlog from ssh

18:06:39 [INFO] [AI] learning for 50 epochs ...
18:07:17 [INFO] [epoch 18] duration=00:00:37 slept_for=00:00:31 blind=0 sad=0 bored=0 inactive=0 active=18 peers=0 tot_bond=0.00 avg_bond=0.00 hops=0 missed=0 deauths=1 assocs=0 handshakes=0 cpu=2% mem=40% temperature=36C reward=0.18947368421052632
17:56:45 [ERROR] [AI] error while training (could not create a primitive descriptor for a matmul primitive)
(most recent call last):
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/ai/train.py", line 185, in _ai_worker
self._model.learn(total_timesteps=epochs_per_episode, callback=self.on_ai_training_step)
File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/a2c/a2c.py", line 194, in learn
return super().learn(
File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/on_policy_algorithm.py", line 259, in learn
continue_training = self.collect_rollouts(self.env, callback, self.rollout_buffer, n_rollout_steps=self.n_steps)
File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/on_policy_algorithm.py", line 169, in collect_rollouts
actions, values, log_probs = self.policy(obs_tensor)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/policies.py", line 625, in forward
values = self.value_net(latent_vf)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/linear.py", line 114, in forward
return F.linear(input, self.weight, self.bias)
could not create a primitive descriptor for a matmul primitive

To Reproduce
Steps to reproduce the behavior:

1. boot up in AUTO mode
2. wait to go into AI mode
3. ssh to check if brain is in /root/

Expected behavior
A clear and concise description of what you expected to happen.
brain.nn is saved or created.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Pwnagotchi version: 2.4.6
• OS version: um
• Type of hardware: PI4
• Any additional hardware used: nope

Additional context
Add any other context about the problem here.
idk

I found I could "squeeze" out more memory usage by running sudo raspi-config, and under Performance Options, GPU Memory, and then changing the value from 64 to 16 (I'm hoping this change will allow me to run this on the Raspberry Pi Zero 2W (I found the other fork I'm using did this).

Other suggestion to make, increase swap file size in /etc/dphys-swapfile, for me I just set it to CONF_SWAPSIZE=2048 instead of the default 100 on your image.

One addition suggestion non memory related is that assuming you are going to run this on a 4B, install rpi-eeprom, so can upgrade to the latest firmware when one comes out, etc.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Just let it run

Expected behavior

Would expect it to reboot sooner or "fix" the broken service that died

Screenshots
Will upload log file so you can see what happens.

Environment (please complete the following information):

• Pwnagotchi version 2.1
• OS version Linux pwnagotchiz1 6.1.21-v8+ #1642
• Type of hardware Raspberry Pi 3B+ with onboard WiFi disabled and external USB WiFi added

Additional context
Add any other context about the problem here.
pwnagotchi.log

Describe the bug
zero 2 w
clear flash of 2.5.0 with clean config only BT
cant boot up

To Reproduce
Steps to reproduce the behavior:
flash and copy config

Expected behavior
ui and pwnagotchi boots up

Screenshots

/var/log/pwngrid-peer.log <==
15:56:02 inf pwngrid v1.10.4 starting in peer mode ...
15:56:22 inf pwngrid v1.10.4 starting in peer mode ...
15:56:41 inf /etc/pwnagotchi/id_rsa found
15:56:41 inf interface wlan0mon is down, bringing it up ...
15:56:41 !!! error while starting signaling: exit status 255
15:57:11 inf pwngrid v1.10.4 starting in peer mode ...
15:57:13 inf /etc/pwnagotchi/id_rsa found
15:57:13 inf interface wlan0mon is down, bringing it up ...
15:57:13 !!! error while starting signaling: exit status 255
15:57:43 inf pwngrid v1.10.4 starting in peer mode ...
15:57:45 inf /etc/pwnagotchi/id_rsa found
15:57:45 inf interface wlan0mon is down, bringing it up ...
15:57:45 !!! error while starting signaling: exit status 255
15:58:16 inf pwngrid v1.10.4 starting in peer mode ...
15:58:18 inf /etc/pwnagotchi/id_rsa found
15:58:18 inf interface wlan0mon is down, bringing it up ...
15:58:18 !!! error while starting signaling: exit status 255
15:58:48 inf pwngrid v1.10.4 starting in peer mode ...
15:58:50 inf /etc/pwnagotchi/id_rsa found
15:58:51 inf interface wlan0mon is down, bringing it up ...
15:58:51 !!! error while starting signaling: exit status 255

/var/log/pwnagotchi.log <==
15:58:57 [INFO] Logtail plugin loaded.
15:58:57 [INFO] [Fix_Services] plugin loaded.
15:58:57 [INFO] webcfg: Plugin loaded.
15:58:57 [INFO] Session-stats plugin loaded.
15:58:57 [WARNING] ui.fps is 0, the display will only update for major changes
15:58:57 [INFO] Got here
15:58:57 [INFO] initializing waveshare v3 display
15:58:58 [INFO] BT-TETHER: Successfully loaded ...
15:59:03 [INFO] pwnagotchi@42e00c5867d4a7a8f3e604aec29d624decf7961ebaf1cf4dd3081016a61a668e (v2.5.0)
15:59:03 [INFO] entering auto mode ...
15:59:03 [INFO] [AI] bootstrapping dependencies ...
15:59:03 [INFO] web ui available at http://0.0.0.0:8080/
15:59:03 [INFO] connecting to http://localhost:8081/api ...
15:59:07 [INFO] found monitor interface: wlan0mon
15:59:07 [INFO] supported channels: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13]
15:59:07 [INFO] handshakes will be collected inside /root/handshakes
15:59:07 [INFO] error 400: exit status 255: SIOCSIFFLAGS: Operation not possible due to RF-kill

Environment (please complete the following information):

• Pwnagotchi version 2.5.0
• OS version
• Type of hardware pi zero w 2
• Any additional hardware used waveshare_3

https://github.com/jayofelony/pwnagotchi-torch/discussions/45#discussioncomment-7646985

Describe the solution you'd like

Adding buttons in the webui for update, install, upgrade of plugins.

Not sure what this is, but AI can't start on Raspberry Pi Zero 2W since going to 2.2.8

I deleted brain.*, rebooted, and still get this error (but it did start up properly on the 4B following the same procedure).

[2023-09-05 08:50:24,537] [INFO] [epoch 1] duration=00:00:24 slept_for=00:00:22 blind=0 sad=0 bored=0 inactive=0 active=1 peers=2 tot_bond=0.32 avg_bond=0.16 hops=1 missed=0 deauths=0 assocs=2 handshakes=0 cpu=25% mem=60% temperature=66C reward=0.10071428571428571
[2023-09-05 08:50:25,263] [INFO] [ai] creating model ...
[2023-09-05 08:50:25,265] [ERROR] error while starting AI (init() got an unexpected keyword argument 'alpha')
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/ai/init.py", line 63, in load
a2c = A2C(SB_A2C_POLICY, env, **config['params'])
TypeError: init() got an unexpected keyword argument 'alpha'
[2023-09-05 08:50:25,268] [WARNING] [ai] AI not loaded!
[2023-09-05 08:50:26,996] [INFO] new peer pwnagotchix@dd303b616b42dea814aafc29aaad588de5425050107f3f41e4844b4c17f0c3a5 detected (1912 encounters)
[2023-09-05 08:50:30,045] [INFO] new peer pwnagotchi400@34d7114159b654b1212497f7cbc29e8ab2f64aa8c4c6ac47f936c3653dbde29e detected (1239 encounters)
[2023-09-05 08:50:47,250] [INFO] sending association frame to (80:30:dc:17:0f:53 Texas Instruments) on channel 1 [0 clients], -70 dBm...
[2023-09-05 08:50:47,361] [INFO] sending association frame to (80:30:dc:16:fd:11 Texas Instruments) on channel 1 [0 clients], -72 dBm...
[2023-09-05 08:50:47,422] [INFO] [epoch 2] duration=00:00:22 slept_for=00:00:22 blind=0 sad=0 bored=0 inactive=0 active=2 peers=4 tot_bond=0.47 avg_bond=0.12 hops=1 missed=0 deauths=0 assocs=2 handshakes=0 cpu=10% mem=70% temperature=63C reward=0.13404761904761905

Also cant get it to ping google from on usb0 on pi4, i havent tried on eth0.

Hi, i tested the 2.5.4 opi image in my opi zero 3 but without success, after load bettercap the system start an loop in this screen.

opi zero 3 use same chip as opi 2w, they use h618 and sdcard.

Describe the bug

Fresh download and clean install, no modifications.
I'ved tried 2.5.1, 2.5.2 and 2.5.3
RPI 4 8GB
I've tried copying a working config.toml and placing in boot.

Steps to reproduce the behavior:

1. Download
2. Flash
3. Wont boot, No SSH access

Should there be anything in config.toml for a clean fresh install?

Describe the bug
after installng and and loading first time i wanted my pwnagotchi to be with white background
so i edited view.py in /usr/local/lib/python3.9/dist-packages/pwnagotchi/ui/view.py as stated in other guides and in logs after rest is just dont want to find bettercap api and than if i exit the log/ssh i cant back in +pwnagotchi stuck in a bootloop , scrren atleat changed background
To Reproduce
Steps to reproduce the behavior:
just change view.py like in this guide https://nickelcitypixels.com/blog/2023/06/25/dark-mode-girl-pwnagotchi/

Expected behavior
getting white background

Screenshots
can send a video and got reprudoced twice

Environment (please complete the following information):

• Pwnagotchi version 2.5.6 pi0w
• OS version windows' 11
• Type of hardware pi0w
• Any additional hardware used

Additional context
Add any other context about the problem here.

Describe the bug
When bettercap connection fails, the code in bettercap.py, near line 102 reboots. This failure is often a temporary failure while systemd waits 30 seconds to restart bettercap. If the pwnagotchi.reboot() is replaced with a delay and "continue", pwnagotchi will eventually reconnect to bettercap after about 30 seconds.

It does come up without wifi.recon running. Not perfect, but we should be able to figure that out. maybe automatically send "wifi.recon on" after a reconnect if the pwny is in auto/ai mode? If I run my "bcinfo.py" script (which queries bettercap for a list of APs and turns on wifi.recon if it sees 0 APs), the pwnagotchi completely recovers from bettercap crashing and restarting.

To Reproduce
Steps to reproduce the behavior:

1. You know... start pwnagotchi and wait for it to eventually happen.
2. Get bored waiting and trigger the failure by "sudo killall -TERM bettercap"3.
3. watch the logs and see the pony reboot.4.
4. edit the code to replace the reboot with continue
5. repeat, and watch it eventually reconnect

Expected behavior
I get it that sometimes the device is gone and bettercap won't be coming back, but the device isn't always gone. It only needs to reboot if the device is gone.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Pwnagotchi version. jayfelony 2.4.4
• OS version - uhh....
• Type of hardware - pizero2w 43430/1 type
• Any additional hardware used: none. just the pi with no headers yet.

Additional context
Add any other context about the problem here.

Hello. I have been looking arround for a few days now and I cannot seem to figure out why the pwnagotchi always boots into auto/ai mode even when it's powered from the data port connected to the pc.

Any idea how to make it boot into manu mode when powered this way?

Version: 2.5.4 64 bit
Hardware: RP02W

after flash

[email protected]'s password:
Linux pwnagotchi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Aug 27 23:17:43 2023 from fe80::14ed:e1c6:f3d1:fc9c%usb0

SSH is enabled and the default password for the 'pi' user has not been changed.
This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.

pi@pwnagotchi:~ $ tail -f /var/log/pwnagotchi.log
FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/leds/led0/brightness'
[2023-08-27 23:36:48,739] [ERROR] [led] error while blinking
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 63, in _worker
self._blink(pattern)
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 49, in _blink
self._led(0)
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 40, in _led
with open(self._led_file, 'wt') as fp:
FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/leds/led0/brightness'
[2023-08-27 23:38:47,249] [ERROR] [led] error while blinking
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 63, in _worker
self._blink(pattern)
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 49, in _blink
self._led(0)
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 40, in _led
with open(self._led_file, 'wt') as fp:
FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/leds/led0/brightness'
[2023-08-27 23:38:47,274] [INFO] [epoch 12] duration=00:02:08 slept_for=00:01:58 blind=12 sad=0 bored=0 inactive=13 active=0 peers=0 tot_bond=0.00 avg_bond=0.00 hops=0 missed=0 deauths=0 assocs=0 handshakes=0 cpu=4% mem=60% temperature=56C reward=-0.47692307692307695
[2023-08-27 23:38:47,278] [ERROR] [led] error while blinking
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 63, in _worker
self._blink(pattern)
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 49, in _blink
self._led(0)
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 40, in _led
with open(self._led_file, 'wt') as fp:
FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/leds/led0/brightness'
[2023-08-27 23:38:57,311] [ERROR] [led] error while blinking
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 63, in _worker
self._blink(pattern)
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 49, in _blink
self._led(0)
File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/plugins/default/led.py", line 40, in _led
with open(self._led_file, 'wt') as fp:
FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/leds/led0/brightness'

/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/vec_env/base_vec_env.py:234: UserWarning: You tried to call render() but no `render_mode` was passed to the env constructor.
  warnings.warn("You tried to call render() but no `render_mode` was passed to the env constructor.")
INFO:root:[AI] learning for 50 epochs ...
[2023-10-08 10:48:09,557] [INFO] [AI] learning for 50 epochs ...
ERROR:root:[AI] error while training (could not create a primitive descriptor for a matmul primitive)
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/pwnagotchi/ai/train.py", line 185, in _ai_worker
    self._model.learn(total_timesteps=epochs_per_episode, callback=self.on_ai_training_step)
  File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/a2c/a2c.py", line 194, in learn
    return super().learn(
  File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/on_policy_algorithm.py", line 259, in learn
    continue_training = self.collect_rollouts(self.env, callback, self.rollout_buffer, n_rollout_steps=self.n_steps)
  File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/on_policy_algorithm.py", line 169, in collect_rollouts
    actions, values, log_probs = self.policy(obs_tensor)
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/stable_baselines3/common/policies.py", line 625, in forward
    values = self.value_net(latent_vf)
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/linear.py", line 114, in forward
    return F.linear(input, self.weight, self.bias)
RuntimeError: could not create a primitive descriptor for a matmul primitive

If anyone with some AI experience could please provide some explanation it would be much appreciated. I have tried everything I could think of. But to no avail.

Describe the bug
Whenever the screen is refreshed the screen flickers between a deep black background and the inverted state. Also setting it to permanently white background is not possible.
I used the setting ui.display.color = "black" in my config.toml, sice this also seems to be the default. Here is the pwnlog entry for this setting:

14:29:18 [INFO] Session-stats plugin loaded.
14:29:18 [INFO] webcfg: Plugin loaded.
14:29:18 [INFO] [Fix_Services] plugin loaded.
14:29:18 [INFO] grid plugin loaded.
14:29:18 [INFO] [update] plugin loaded.
14:29:19 [WARNING] ui.fps is 0, the display will only update for major changes
14:29:19 [INFO] initializing waveshare 2.13inb v2in13_V4 display
14:29:19 [INFO] Got here
14:29:28 [INFO] pwni@de7691f9de29100ddc2383231f434ce52164982df54bb2b9013ff7251d3fa4af (v2.6.1)
14:29:28 [INFO] entering manual mode ...
14:29:29 [INFO] the last session lasted 21 minutes, 35 seconds (0 completed epochs, trained for 0), average reward:0.0 (min:1000 max:-1000)
14:29:29 [INFO] web ui available at http://[::]:8080/

When I try to change the color to white in config.toml, I get an error about a wrong image size in the pwnlog and the display is permanently flickering between black and white background without showing any pwnagotchi stats or faces. This is what the pwnlog locks like with the setting set to white:

14:37:58 [INFO] Session-stats plugin loaded.
14:37:58 [INFO] [update] plugin loaded.
14:37:58 [INFO] webcfg: Plugin loaded.
14:37:58 [INFO] grid plugin loaded.
14:37:58 [INFO] [Fix_Services] plugin loaded.
14:37:59 [WARNING] ui.fps is 0, the display will only update for major changes
14:37:59 [INFO] initializing waveshare 2.13inb v2in13_V4 display
14:37:59 [INFO] Got here
14:38:08 [WARNING] Wrong image dimensions: must be 122x250
14:38:08 [WARNING] Wrong image dimensions: must be 122x250
14:38:08 [INFO] pwni@de7691f9de29100ddc2383231f434ce52164982df54bb2b9013ff7251d3fa4af (v2.6.1)
14:38:08 [INFO] entering manual mode ...
14:38:09 [INFO] web ui available at http://[::]:8080/
14:38:09 [INFO] the last session lasted 30 minutes, 15 seconds (0 completed epochs, trained for 0), average reward:0.0 (min:1000 max:-1000)
14:38:10 [WARNING] Wrong image dimensions: must be 122x250
14:38:10 [WARNING] Wrong image dimensions: must be 122x250
14:38:16 [WARNING] Wrong image dimensions: must be 122x250
14:38:16 [WARNING] Wrong image dimensions: must be 122x250
14:38:21 [WARNING] Wrong image dimensions: must be 122x250
14:38:21 [WARNING] Wrong image dimensions: must be 122x250
14:38:24 [WARNING] Wrong image dimensions: must be 122x250
14:38:24 [WARNING] Wrong image dimensions: must be 122x250
14:38:28 [WARNING] Wrong image dimensions: must be 122x250
14:38:28 [WARNING] Wrong image dimensions: must be 122x250
14:38:30 [WARNING] Wrong image dimensions: must be 122x250
14:38:30 [WARNING] Wrong image dimensions: must be 122x250
14:38:34 [WARNING] Wrong image dimensions: must be 122x250
14:38:34 [WARNING] Wrong image dimensions: must be 122x250
14:38:36 [WARNING] Wrong image dimensions: must be 122x250
14:38:36 [WARNING] Wrong image dimensions: must be 122x250
14:38:40 [WARNING] Wrong image dimensions: must be 122x250
14:38:40 [WARNING] Wrong image dimensions: must be 122x250
14:38:43 [WARNING] Wrong image dimensions: must be 122x250
14:38:43 [WARNING] Wrong image dimensions: must be 122x250
14:38:46 [WARNING] Wrong image dimensions: must be 122x250
14:38:46 [WARNING] Wrong image dimensions: must be 122x250
14:38:49 [WARNING] Wrong image dimensions: must be 122x250
14:38:49 [WARNING] Wrong image dimensions: must be 122x250
14:38:53 [WARNING] Wrong image dimensions: must be 122x250
14:38:53 [WARNING] Wrong image dimensions: must be 122x250
14:38:56 [WARNING] Wrong image dimensions: must be 122x250
14:38:56 [WARNING] Wrong image dimensions: must be 122x250
14:38:59 [WARNING] Wrong image dimensions: must be 122x250
14:38:59 [WARNING] Wrong image dimensions: must be 122x250

Am I doing something wrong?

To Reproduce
Steps to reproduce the behavior:

1. Install pwnagotchi-torch and update to latest version 2.6.1
2. Include the following lines in your config.toml

ui.display.enabled = true
ui.display.type = "waveshare213inb_v4"
ui.display.color = "white"

3. restart pwnagotchi service
4. Enjoy the lightshow

Expected behavior
I would like to either set a white background with black drawlines or a black background with white drawlines. If either is selected I would like it to not constantly flicker between the color modes.

Environment (please complete the following information):

• v2.6.1
• Raspian OS Buster
• Raspberry Pi 0W
• Waveshare 2.13 e-Paper display V4

Describe the bug
Hi. I'm trying configure 2.5.4 version to get tethered by bluetooth via android to update but nothing happens, it simply doesn't even trying to find the phone, and i don't understand where i should investigate because there's no logs regarding bluetooth

so configuration in config.toml is:

main.plugins.bt-tether.enabled = true
main.plugins.bt-tether.devices.android-phone.enabled = true
main.plugins.bt-tether.devices.android-phone.search_order = 1
main.plugins.bt-tether.devices.android-phone.mac = "XX:XX:XX:XX:XX:XX"
main.plugins.bt-tether.devices.android-phone.ip = "192.168.44.44"
main.plugins.bt-tether.devices.android-phone.netmask = 24
main.plugins.bt-tether.devices.android-phone.interval = 1
main.plugins.bt-tether.devices.android-phone.scantime = 5
main.plugins.bt-tether.devices.android-phone.max_tries = 999
main.plugins.bt-tether.devices.android-phone.share_internet = false
main.plugins.bt-tether.devices.android-phone.priority = 1

Environment

• 2.5.4
• rpi zero 2w
• Android 13

01:01:46 !!! dial tcp: lookup pwngrid-mysql on 8.8.8.8:53: read udp 172.20.10.7: 52025->8.8.8.8:53: i/o timeout
01:02:17 inf pwngrid v1.10.3 starting in server mode ...
01:02:17 inf connecting to pwngrid-mysql:3306 ...
01:02:18 !!! dial tcp: lookup pwngrid-mysql on 8.8.8.8:53: no such host
01:02:49 inf pwngrid v1.10.3 starting in server mode ...
01:02:49 inf connecting to pwngrid-mysql:3306 ...
01:02:54 !!! dial tcp: lookup pwngrid-mysql on 8.8.8.8:53: no such host
01:03:24 inf pwngrid v1.10.3 starting in server mode ...
01:03:24 inf connecting to pwngrid-mysql:3306 ...
01:03:24 !!! dial tcp: lookup pwngrid-mysql on 8.8.8.8:53: no such host
01:03:54 inf pwngrid v1.10.3 starting in server mode ...
01:03:54 inf connecting to pwngrid-mysql:3306 ...
01:03:54 !!! dial tcp: lookup pwngrid-mysql on 8.8.8.8:53: no such host
01:04:24 inf pwngrid v1.10.3 starting in server mode ...
01:04:24 inf connecting to pwngrid-mysql:3306 ...
01:04:24 !!! dial tcp: lookup pwngrid-mysql on 8.8.8.8:53: no such host

/var/log/pwngrid-peer.log <==
10:41:54 inf pwngrid v1.10.3 starting in peer mode ...
10:42:02 inf /etc/pwnagotchi/id_rsa found
10:42:02 inf started beacon discovery and message routing (0 known peers)
10:42:02 inf peer pwnagotchi@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719 e822d51a0d765 signaling is ready
10:42:02 inf pwngrid api starting on 127.0.0.1:8666 ...
10:42:02 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
10:42:04 inf peer advertisement enabled
10:42:12 inf pwngrid v1.10.3 starting in peer mode ...
10:42:14 inf /etc/pwnagotchi/id_rsa found
10:42:14 inf interface wlan0mon is down, bringing it up ...
10:42:14 inf started beacon discovery and message routing (1 known peers)
10:42:14 inf peer pwnagotchi@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719 e822d51a0d765 signaling is ready
10:42:14 inf pwngrid api starting on 127.0.0.1:8666 ...
10:42:19 inf peer advertisement enabled
10:42:22 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 5
10:49:20 inf pwngrid v1.10.3 starting in peer mode ...
10:49:22 inf /etc/pwnagotchi/id_rsa found
10:49:22 inf interface wlan0mon is down, bringing it up ...
10:49:22 inf started beacon discovery and message routing (1 known peers)
10:49:22 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
10:49:22 inf pwngrid api starting on 127.0.0.1:8666 ...
10:49:27 inf peer advertisement enabled
10:49:32 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 9
10:53:18 inf pwngrid v1.10.3 starting in peer mode ...
10:53:21 inf /etc/pwnagotchi/id_rsa found
10:53:21 inf interface wlan0mon is down, bringing it up ...
10:53:21 inf started beacon discovery and message routing (1 known peers)
10:53:21 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
10:53:21 inf pwngrid api starting on 127.0.0.1:8666 ...
10:53:21 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
10:53:25 inf peer advertisement enabled
10:55:09 inf pwngrid v1.10.3 starting in peer mode ...
10:55:11 inf /etc/pwnagotchi/id_rsa found
10:55:11 inf interface wlan0mon is down, bringing it up ...
10:55:11 inf started beacon discovery and message routing (1 known peers)
10:55:11 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
10:55:11 inf pwngrid api starting on 127.0.0.1:8666 ...
10:55:14 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
10:55:16 inf peer advertisement enabled
11:02:59 inf pwngrid v1.10.3 starting in peer mode ...
11:03:01 inf /etc/pwnagotchi/id_rsa found
11:03:01 inf started beacon discovery and message routing (1 known peers)
11:03:01 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
11:03:01 inf pwngrid api starting on 127.0.0.1:8666 ...
11:03:03 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
11:03:06 inf peer advertisement enabled
11:09:34 inf pwngrid v1.10.3 starting in peer mode ...
11:09:36 inf /etc/pwnagotchi/id_rsa found
11:09:36 inf interface wlan0mon is down, bringing it up ...
11:09:36 inf started beacon discovery and message routing (1 known peers)
11:09:36 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
11:09:36 inf pwngrid api starting on 127.0.0.1:8666 ...
11:09:38 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
11:09:38 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
11:09:41 inf peer advertisement enabled
23:36:10 inf pwngrid v1.10.3 starting in peer mode ...
23:36:12 inf /etc/pwnagotchi/id_rsa found
23:36:12 inf interface wlan0mon is down, bringing it up ...
23:36:12 inf started beacon discovery and message routing (1 known peers)
23:36:12 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
23:36:12 inf pwngrid api starting on 127.0.0.1:8666 ...
23:36:16 inf peer advertisement enabled
23:36:18 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 8
00:06:34 inf peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8f0f7365d8e937 102e9a33 lost (inactive for 1801.257722s)
00:29:13 inf pwngrid v1.10.3 starting in peer mode ...
00:29:15 inf /etc/pwnagotchi/id_rsa found
00:29:15 inf interface wlan0mon is down, bringing it up ...
00:29:15 inf started beacon discovery and message routing (1 known peers)
00:29:15 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
00:29:15 inf pwngrid api starting on 127.0.0.1:8666 ...
00:29:20 inf peer advertisement enabled
00:29:24 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 3
12:16:48 err POST https://api.pwnagotchi.ai/api/v1/unit/report/ap (1m0.000934051 s) Post "https://api.pwnagotchi.ai/api/v1/unit/report/ap": context deadline exce eded (Client.Timeout exceeded while awaiting headers)
12:18:27 err POST https://api.pwnagotchi.ai/api/v1/unit/report/ap (1m0.001094155 s) Post "https://api.pwnagotchi.ai/api/v1/unit/report/ap": context deadline exce eded (Client.Timeout exceeded while awaiting headers)
12:40:40 inf peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8f0f7365d8e937 102e9a33 lost (inactive for 1801.002403s)
12:55:46 inf pwngrid v1.10.3 starting in peer mode ...
12:55:48 inf /etc/pwnagotchi/id_rsa found
12:55:48 inf interface wlan0mon is down, bringing it up ...
12:55:48 inf started beacon discovery and message routing (1 known peers)
12:55:48 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
12:55:48 inf pwngrid api starting on 127.0.0.1:8666 ...
12:55:53 inf peer advertisement enabled
12:55:53 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 1
12:57:25 inf peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8f0f7365d8e937 102e9a33 changed session id: 63343a32623a33383a64663a66653a6332 -> 64333a61343a3 7373a32333a35663a3066
12:57:49 inf pwngrid v1.10.3 starting in peer mode ...
12:57:51 inf /etc/pwnagotchi/id_rsa found
12:57:52 inf interface wlan0mon is down, bringing it up ...
12:57:52 inf started beacon discovery and message routing (1 known peers)
12:57:52 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
12:57:52 inf pwngrid api starting on 127.0.0.1:8666 ...
12:57:52 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
13:00:50 inf pwngrid v1.10.3 starting in peer mode ...
13:00:52 inf /etc/pwnagotchi/id_rsa found
13:00:52 inf interface wlan0mon is down, bringing it up ...
13:00:52 inf started beacon discovery and message routing (1 known peers)
13:00:52 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
13:00:52 inf pwngrid api starting on 127.0.0.1:8666 ...
13:00:57 inf peer advertisement enabled
13:00:58 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 6
13:07:48 inf pwngrid v1.10.3 starting in peer mode ...
13:07:50 inf /etc/pwnagotchi/id_rsa found
13:07:50 war error while setting interface wlan0mon in monitor mode: No such dev ice exists
13:07:50 !!! error while starting signaling: error while activating handle: No S uch Device
13:08:34 inf pwngrid v1.10.3 starting in peer mode ...
13:08:36 inf /etc/pwnagotchi/id_rsa found
13:08:36 inf started beacon discovery and message routing (1 known peers)
13:08:36 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
13:08:36 inf pwngrid api starting on 127.0.0.1:8666 ...
13:08:36 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
13:08:39 inf peer advertisement enabled
13:18:34 inf pwngrid v1.10.3 starting in peer mode ...
13:18:36 inf /etc/pwnagotchi/id_rsa found
13:18:37 inf started beacon discovery and message routing (1 known peers)
13:18:37 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
13:18:37 inf pwngrid api starting on 127.0.0.1:8666 ...
13:18:41 inf peer advertisement enabled
13:18:42 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 2
13:38:13 inf pwngrid v1.10.3 starting in peer mode ...
13:38:15 inf /etc/pwnagotchi/id_rsa found
13:38:15 inf interface wlan0mon is down, bringing it up ...
13:38:15 inf started beacon discovery and message routing (1 known peers)
13:38:15 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
13:38:15 inf pwngrid api starting on 127.0.0.1:8666 ...
13:38:16 inf detected new peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8 f0f7365d8e937102e9a33 on channel 10
13:38:20 inf peer advertisement enabled
14:08:32 inf peer aleda@ebd94ff44b1f762e46400151eed4f01b6a03f1a43c8f0f7365d8e937 102e9a33 lost (inactive for 1801.173802s)
14:55:14 inf pwngrid v1.10.3 starting in peer mode ...
14:55:16 inf /etc/pwnagotchi/id_rsa found
14:55:16 inf interface wlan0mon is down, bringing it up ...
14:55:16 inf started beacon discovery and message routing (1 known peers)
14:55:16 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
14:55:16 inf pwngrid api starting on 127.0.0.1:8666 ...
14:55:21 inf peer advertisement enabled
15:42:20 inf pwngrid v1.10.3 starting in peer mode ...
15:42:22 inf /etc/pwnagotchi/id_rsa found
15:42:22 inf interface wlan0mon is down, bringing it up ...
15:42:23 inf started beacon discovery and message routing (1 known peers)
15:42:23 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
15:42:23 inf pwngrid api starting on 127.0.0.1:8666 ...
15:42:27 inf peer advertisement enabled
16:35:52 inf pwngrid v1.10.3 starting in peer mode ...
16:35:55 inf /etc/pwnagotchi/id_rsa found
16:35:55 inf interface wlan0mon is down, bringing it up ...
16:35:55 inf started beacon discovery and message routing (1 known peers)
16:35:55 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
16:35:55 inf pwngrid api starting on 127.0.0.1:8666 ...
16:35:59 inf peer advertisement enabled
17:28:54 inf pwngrid v1.10.3 starting in peer mode ...
17:28:56 inf /etc/pwnagotchi/id_rsa found
17:28:56 inf interface wlan0mon is down, bringing it up ...
17:28:56 inf started beacon discovery and message routing (1 known peers)
17:28:56 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
17:28:56 inf pwngrid api starting on 127.0.0.1:8666 ...
17:29:01 inf peer advertisement enabled
18:26:53 inf pwngrid v1.10.3 starting in peer mode ...
18:26:55 inf /etc/pwnagotchi/id_rsa found
18:26:55 inf interface wlan0mon is down, bringing it up ...
18:26:55 inf started beacon discovery and message routing (1 known peers)
18:26:55 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
18:26:55 inf pwngrid api starting on 127.0.0.1:8666 ...
18:27:00 inf peer advertisement enabled
18:35:59 inf pwngrid v1.10.3 starting in peer mode ...
18:36:01 inf /etc/pwnagotchi/id_rsa found
18:36:01 inf interface wlan0mon is down, bringing it up ...
18:36:02 inf started beacon discovery and message routing (1 known peers)
18:36:02 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
18:36:02 inf pwngrid api starting on 127.0.0.1:8666 ...
18:36:06 inf peer advertisement enabled
01:04:45 inf pwngrid v1.10.3 starting in peer mode ...
01:04:47 inf /etc/pwnagotchi/id_rsa found
01:04:48 inf interface wlan0mon is down, bringing it up ...
01:04:48 inf started beacon discovery and message routing (1 known peers)
01:04:48 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
01:04:48 inf pwngrid api starting on 127.0.0.1:8666 ...
01:04:52 inf peer advertisement enabled
01:19:52 inf pwngrid v1.10.3 starting in peer mode ...
01:19:54 inf /etc/pwnagotchi/id_rsa found
01:19:54 inf interface wlan0mon is down, bringing it up ...
01:19:54 inf started beacon discovery and message routing (1 known peers)
01:19:54 inf peer aleda2@c79022a9ec2a2cd8d01bb3c677e8495b6a827758070f939f719e822 d51a0d765 signaling is ready
01:19:54 inf pwngrid api starting on 127.0.0.1:8666 ...
01:19:58 inf peer advertisement enabled

/var/log/pwnagotchi.log <==
19:30:15 [INFO] [epoch 6] duration=00:00:51 slept_for=00:00:51 blind=6 sad=1 bored=0 inactive=7 active=0 peers=0 tot_bond=0.00 avg_bond=0.00 hops=0 missed=0 deauths=0 assocs=0 handshakes=0 cpu=7% mem=10% temperature=38C reward=-0.45714285714285713
19:30:15 [INFO] [ai] saving model to /root/brain.nn ...
19:30:15 [WARNING] 7 epochs with no activity -> sad
19:30:16 [INFO] [ai] saving /root/brain.json
19:30:26 [INFO] [ai] setting new policy:
19:30:26 [INFO] [ai] ! min_rssi: -125 -> -174
19:30:26 [INFO] [ai] ! ap_ttl: 279 -> 386
19:30:26 [INFO] [ai] ! sta_ttl: 270 -> 183
19:30:26 [INFO] [ai] ! recon_time: 55 -> 10
19:30:26 [INFO] [ai] ! max_inactive_scale: 3 -> 8
19:30:26 [INFO] [ai] ! recon_inactive_multiplier: 3 -> 1
19:30:26 [INFO] [ai] ! hop_recon_time: 23 -> 56
19:30:26 [INFO] [ai] ! min_recon_time: 30 -> 18
19:30:26 [INFO] [ai] ! max_interactions: 1 -> 21
19:30:26 [INFO] [ai] ! max_misses_for_recon: 5 -> 10
19:30:26 [INFO] [ai] ! excited_num_epochs: 14 -> 12
19:30:26 [INFO] [ai] ! bored_num_epochs: 27 -> 14
19:30:27 [INFO] [ai] ! sad_num_epochs: 7 -> 15
19:30:27 [INFO] [ai] ! channels: [3, 4, 6, 8, 9, 10, 11, 36, 44, 48, 56, 100, 104, 112, 120, 132, 136] -> [5, 6, 7, 10, 40, 44, 48, 52, 60, 64, 104, 108, 112, 120, 124, 128, 132, 136, 140]
19:33:01 [INFO] [epoch 7] duration=00:02:46 slept_for=00:02:45 blind=7 sad=0 bored=0 inactive=8 active=0 peers=0 tot_bond=0.00 avg_bond=0.00 hops=0 missed=0 deauths=0 assocs=0 handshakes=0 cpu=27% mem=10% temperature=41C reward=-0.4625
19:33:01 [INFO] [ai] saving model to /root/brain.nn ...
19:33:02 [INFO] [ai] saving /root/brain.json
19:33:11 [INFO] [ai] setting new policy:
19:33:11 [INFO] [ai] ! min_rssi: -174 -> -143
19:33:11 [INFO] [ai] ! sta_ttl: 183 -> 114
19:33:11 [INFO] [ai] ! recon_time: 10 -> 29
19:33:11 [INFO] [ai] ! max_inactive_scale: 8 -> 3
19:33:11 [INFO] [ai] ! recon_inactive_multiplier: 1 -> 2
19:33:11 [INFO] [ai] ! hop_recon_time: 56 -> 18
19:33:11 [INFO] [ai] ! min_recon_time: 18 -> 4
19:33:11 [INFO] [ai] ! max_interactions: 21 -> 1
19:33:11 [INFO] [ai] ! max_misses_for_recon: 10 -> 5
19:33:11 [INFO] [ai] ! excited_num_epochs: 12 -> 21
19:33:11 [INFO] [ai] ! bored_num_epochs: 14 -> 29
19:33:11 [INFO] [ai] ! sad_num_epochs: 15 -> 24
19:33:11 [INFO] [ai] ! channels: [5, 6, 7, 10, 40, 44, 48, 52, 60, 64, 104, 108, 112, 120, 124, 128, 132, 136, 140] -> [2, 4, 9, 10, 40, 44, 52, 56, 60, 100, 112, 124, 128, 132, 136, 140]
19:33:13 [INFO] [epoch 8] duration=00:00:11 slept_for=00:00:10 blind=8 sad=0 bored=0 inactive=9 active=0 peers=0 tot_bond=0.00 avg_bond=0.00 hops=0 missed=0 deauths=0 assocs=0 handshakes=0 cpu=40% mem=10% temperature=42C reward=-0.4666666666666667
19:33:13 [INFO] [ai] saving model to /root/brain.nn ...
19:33:13 [INFO] [ai] saving /root/brain.json
19:33:21 [INFO] [ai] setting new policy:
19:33:21 [INFO] [ai] ! min_rssi: -143 -> -79
19:33:21 [INFO] [ai] ! ap_ttl: 386 -> 390
19:33:21 [INFO] [ai] ! sta_ttl: 114 -> 165
19:33:21 [INFO] [ai] ! recon_time: 29 -> 18
19:33:21 [INFO] [ai] ! max_inactive_scale: 3 -> 8
19:33:21 [INFO] [ai] ! hop_recon_time: 18 -> 42
19:33:21 [INFO] [ai] ! min_recon_time: 4 -> 1
19:33:21 [INFO] [ai] ! max_interactions: 1 -> 22
19:33:21 [INFO] [ai] ! max_misses_for_recon: 5 -> 6
19:33:21 [INFO] [ai] ! excited_num_epochs: 21 -> 11
19:33:21 [INFO] [ai] ! bored_num_epochs: 29 -> 21
19:33:21 [INFO] [ai] ! sad_num_epochs: 24 -> 20
19:33:21 [INFO] [ai] ! channels: [2, 4, 9, 10, 40, 44, 52, 56, 60, 100, 112, 124, 128, 132, 136, 140] -> [3, 4, 6, 11, 36, 44, 48, 64, 100, 104, 116, 120, 124, 128, 132, 136]
19:34:12 [INFO] [epoch 9] duration=00:00:59 slept_for=00:00:58 blind=9 sad=0 bored=0 inactive=10 active=0 peers=0 tot_bond=0.00 avg_bond=0.00 hops=0 missed=0 deauths=0 assocs=0 handshakes=0 cpu=29% mem=10% temperature=42C reward=-0.47000000000000003
19:34:12 [INFO] [ai] saving model to /root/brain.nn ...
19:34:12 [INFO] [ai] saving /root/brain.json

Describe the bug

To Reproduce
Steps to reproduce the behavior:

1. pwngrid -version should return 1.10.4

Expected behavior
Properly reporting to opwngrid.xyz

Environment (please complete the following information):

• Pwnagotchi version 2.5.1

Additional context
64-bit users should rebuild their pwngrid or reflash next update

Describe the bug

Bluetooth has a notch to keep crashing and dying connected to my phone (Fold 4 Samsung).

To Reproduce

Steps to reproduce the behavior:

1. Pair and trust phone via bluetoothctl
2. Add mac address in config.toml
3. Just let gotchi sit through out and wait for the crash to happened. Fastest to crash is 5mins tops. Longest run is an hour.

Screenshots

Environment (please complete the following information):

Version	2.5.4
Build	Pwnagotchi-Torch by Jayofelony
uname	Linux Phr34kz 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

https://opwngrid.xyz/search/c937ecfddb8ec5d71b6a4cc700cb90a8ba35bcf5f098f9c5059a8f4de433c7df

• Type of hardware: 02w
• Any additional hardware used: PiSugar 2 (2 led), Waveshare v4 and Samsung Galaxy Fold 4 (Android 13)

Additional context

Noticed - "a2dp-sink profile connect failed for" in systemctl status bluetooth

did

sudo apt-get install pulseaudio-module-bluetooth
sudo killall pulseaudio
pulseaudio --start    
sudo systemctl restart bluetooth

and added load-module module-bluez5-discover in /etc/pulse/default.pa to no avail but it did prolong the crash period together with --noplugin=sap as stated in here. Bluetooth audio slider on bluetooth settings in mobile have to manually be turned on.

Reference:
https://askubuntu.com/questions/1172000/a2dp-sink-profile-connect-failed
https://raspberrypi.stackexchange.com/questions/40839/sap-error-on-bluetooth-service-status

Others:

• Changed DNS from 1.1.1.1 to 8.8.4.4 as well in https://github.com/jayofelony/pwnagotchi-torch/blob/pwnagotchi-torch/builder/data/etc/dhcpcd.conf. 1.1.1.1 DNS is a slow DNS for me.

• Changed DNS from 9.9.9.9 to 8.8.8.8 in https://github.com/jayofelony/pwnagotchi-torch/blob/pwnagotchi-torch/pwnagotchi/plugins/default/bt-tether.py. Quad 9 DNS is a slow DNS for me as well.

• Changed

#self.set('friend_face', peer.face())
self.set('friend_face', ' (⌐■_■)')            

in https://github.com/jayofelony/pwnagotchi-torch/blob/pwnagotchi-torch/pwnagotchi/ui/view.py so as peer face does not appear as /CUSTOM-FACES/LOOK-R.PNG on both device and web ui

• Changed

def _on_face_change(self, old, new):
self._advertisement['face'] = '(⌐■_■)'
grid.set_advertisement_data(self._advertisement)

in https://github.com/jayofelony/pwnagotchi-torch/blob/pwnagotchi-torch/pwnagotchi/mesh/utils.py so as peer face does not appear as /CUSTOM-FACES/LOOK-R.PNG in https://opwngrid.xyz/

Describe the bug
Since reimaging to 2.4.7, can no longer get this to work with a Raspberry Pi 3B+

To Reproduce
Installed 2.4.7

Expected behavior
Just to work as it did with 2.4.6

Environment (please complete the following information):

• Pwnagotchi version 2.4.7
• OS version Linux pwnagotchi3b 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
• Type of hardware Raspberry Pi 3B+
• Any additional hardware used None

Additional context
Seemed to work just fine with previous versions, at one time it didn't work with one of the "older" versions, but since had been resolved in a recent release, etc.
pwnagotchi.log

I need your help to come with new stuff you want added, so please if you find something interesting open a PR!!

Describe the bug
Flashed a RPi 3b and got it up and running. I currently have a ZeroW that is up and running as well running 1.5.5. Both have personality.advertise = true. The ZeroW is seeing my 3b pwnagotchi, but the 3b is not seeing the ZeroW.

To Reproduce
Steps to reproduce the behavior:

1. ZeroW running 1.5.5
2. RPi 3b running 2.5.6
3. Power up both devices, wait for them to search for eachother

Expected behavior
Both devices see eachother, not just the ZeroW on 1.5.5 seeing the RPi 3b running 2.5.6

Screenshots

Environment (please complete the following information):

• Pwnagotchi version 2.5.6

Additional context
Add any other context about the problem here.

Somehow the armhf pwngrid version got corrupted.

cd ~
wget https://github.com/jayofelony/pwngrid/releases/download/v1.10.5/pwngrid-1.10.5-armhf.zip
unzip pwngrid-1.10.5-armhf.zip
sudo systemctl stop pwngrid-peer.service
sudo mv pwngrid /usr/local/bin
sudo chmod +x /usr/local/bin/*
sudo systemctl restart pwngrid-peer.service
sudo rm -r *

Run these commands to revert back to 1.10.5

Running 2.2.9.1 on a Raspberry Pi 3B+ with internal Wi-Fi adapter

Looking in the /var/log/pwnagotchi.log, I see this:

[INFO] supported channels: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11]

Would I expect to see 5ghz channels as well?

On my Raspberry Pi 4B with internal Wi-Fi adapter I see this:

[INFO] supported channels: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 144, 149]

While on a Raspberry Pi Zero 2W with internal Wi-Fi adapter I see this:

[INFO] supported channels: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11]

Maybe just need to compile a newer driver for 3B+?

Describe the bug
Hi, went through the logs and had this error:

12:07:47 inf connecting to pwngrid-mysql:3306 ...
12:07:47 !!! dial tcp: lookup pwngrid-mysql on 8.8.8.8:53: no such host

Trying to understand why would it look for a mysql server :D
Appreciate your thoughts on this :) Thanks!

To Reproduce
Steps to reproduce the behavior:

1. ...
2. ...
3. ...

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Pwnagotchi version
• OS version
• Type of hardware
• Any additional hardware used

Additional context
Add any other context about the problem here.

To confirm it wasn't my config.toml, I removed it and only using the default.toml file and still won't start.

pwnagotchi.log

Should we also stop this service as well?
pwngrid-peer.service