Luigi's Polteguster - photo drop

Skip to main content

Search This Blog

Luigi's Polteguster - photo drop

on October 14, 2018

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Projects

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

Proxmark3 - Getting Started

Now with installation complete I was able to run Proxmark. Out of habit with the back and forth I had when flashing my Proxmark3, I check to see that the device is detect by running the command: ~$lsusb This is used to list usb buses and get information about devices connected them, and as we can see on bus 001 Device 003 our Proxmark3 is listed. I also then ensure that the port has be assigned by running ~$sudo dmesg| grep -i usb and can see it has been properly assigned to ttyAMC0 I can now change directories to /proxmark3 and attempt to launch it ~$cd proxmark3 ~$sudo ./client/proxmark3 /dev/ttyACM0 Above you can see information on the board as it loads and we can now perform a few tests. Although we have made a number of steps to ensure we are connected to the proxmark3, we can run a pin test to validate communication to the board. proxmark3>hw ping Ping successful Next we should run a hardware tune to test the tuning of the ante

Proxmark3 - VM installation Kali Linux

While the Wiki does an excellent step by step installation of the Proxmark, I thought I would write on my experience as I did overlook a step of configuration that lead to some brief confusion. It should also be noted that there are multiple recommendations made of avoiding installation on a virtual machine, though I was able to accomplish this with no issues. Another note would be that the USB interface used is identified in the picture below. The side USB interface is for powering for standalone or field mode operation in combination with a power source such as a battery pack. Windows 10 If you are running a virtual machine, your host machine needs to have the appropriate driver in order for your device to be accessible to your VM. We must first download and extract the following https://github.com/Gator96100/ProxSpace/archive/master.zip Once extracted we need to disable driver signature verification. There are two ways to achieve this: Option #1 enable test signing Right click CMD

Use Windows Hotspot for Airlink Oculus Meta Quest 2

Airlink is an amazing feature of the Quest 2 and configuring it allows users to "unthether" from the long USB and utilize wifi to link to your PC for PCVR - and it works amazing! The trouble at this time is specifications are vague as the feature is experimental and advice seems to point users toward dedicated 802.11ax "Wifi 6" routers configured to access points - which seem unnecessarily expensive. My motherboard (AORUS Elite) has an Intel wireless dual band 802.11ac integrated adapter that went unutilized. While trying to work out the best way to minimize latency over my network, I thought I would try to utilize this adapter. The follow are my notes regarding this configuration with the assumption of the Airlink experimental feature already being enabled on your headset. Configuration notes Hardware spec: Oculus branded Quest 2 AMD R9 3900X 32GB of RAM 1TB NVMe SSD X570 AORUS Elite Wifi ROG Strix RTX 3070 Under your adapter settings in device manager, there are

Luigi's Polteguster - photo drop

Comments

Post a Comment