I’m trying to edit a custom dnsbl group from my mobile device, however, the blocklist table format is too wide for the enclosing view and I cannot scroll to the right to expose the edit button control.
Is there any way around this without a laptop?
IOS 26.5
pfSense+ 26.03.1
pfBlockerNG-devel 3.2.16
I have been using a set of old flash drives forever and a day. One has curiously stopped working on my Mac Studio and I'm hoping somebody can help me figure out how to get it working again.
Last week I overwrote the flash drive in question with the latest Debian Trixie ISO using Balena Etcher on my M4 Pro Mac Studio running Sequoia 15.7.5 (at the time, now 15.7.7). That Flash drive boots and was used to install Debian on my MacBookAir 2013 just fine (missing Broadcom wifi support/operability not withstanding). I have several other flash drives that are currently similarly loaded with Proxmox VE 9.1, Batocera, and other Debian/Linux images that still mount as valid drives on my Mac Studio. It's just this one flash drive that no longer mounts and I'm at a loss as to why.
If I plug it into the MBA13 running Debian, I see the drive with lsdsk/lsusb, etc... and can mount it just fine. As a test, I've used 'part' on Debian to overwrite the partition table (GPT) and create a HFS+ partition. Even after this, the device is still not recognized on the Studio in any USB-A port or via USB-A-to-C adapter. A reminder that the other flash drives of the same brand work fine, and this drive worked fine until the Debian image overwrite.
In the System Information USB device tree, when this device is plugged in, it appears as a blank line under the appropriate USB Hub device. The name is just blank. The product ID, vendor ID, version, serial number and location ID appear correctly... MacOS just can't read the rest of it.
This flash drive does not appear in diskutil, Finder, or Balena Etcher for use.
There LED on the flash drive does not illuminate or blink at all as it does on other systems when plugged into the Studio.
Any recommendations on triage for this drive - other than the obvious to just use it on systems that still work with it or erase it and trash it?