sexta-feira, janeiro 10, 2020

Icom IC-706MKgII digital modes / usb menu settings



The 706 comes with some power-on factory defaults that you will want to change. The recommended changes make the radio easier to operate. First, let’s set up the power-on defaults.

Go to Initial Set Mode by power off, hold Lock button and power on. Refer to the initial setup items on pages 50-55.
Items 34-37 - CI-V settings: Leave the address at 58H; change BAUD to 19200, turn CI-V TRN on, and leave 731 off. To operate with computer control and digital modes, see the interface section later herein, as well as my article on the digital-modes.



Change Power-On Defaults



Item 1 - Mode Select: You can turn off modes that you don’t want the Mode button to select in its rotation: Unless you have an external FSK RTTY system connected, turn off RTTY mode. Most of us on RTTY are now operating AFSK RTTY via a computer, where you’ll be running on SSB.



Item 7 - RF/SQL: This requires some explanation! Set to RF/SQL, the knob will act as RF gain from 7-12-O’clock, and Squelch from 12-7-O’clock. Set item 7 to RF/SQL and set the knob to about 12:30 and you’ll never have to mess with it again. If set to Auto, you’ll have to crank it around every time you switch from SSB/CW to FM modes. The “RF/SQL” setting is the most convenient.

Item 8 - Sub-dial: Set it to RIT if you operate HF. This makes the Memory Channel knob operate as a RIT while in VFO-A/B modes. Regardless of where you set this setting, the knob will still operate as Memory Channel while in the MEMOry mode.

Item 20 - Auto Repeater: This should definitely be changed from the default. Set it to “On 2” and the 2 meter band will automatically set the right offset when you are in the range of the usual repeater bands — 600 negative below 147, and 600 positive when above 147. This will save you a lot of extra offset-setting while you are programming your repeater channels. Also sets the usual +5.00 MHz offset for 440 repeaters.


Item 24 - AM NB: Set to “off” and the Noise Blanker will be disabled on AM reception, where it will otherwise cause distortion to strong AM signals.



Items 34-37 - CI-V settings: Leave the address at 58H; change BAUD to 19200, turn CI-V TRN on, and leave 731 off. To operate with computer control and digital modes, see the interface section later herein, as well as my article on the digital-modes.


Now power off, and on, and go to the Q menu, by holding in the Display button.



quinta-feira, novembro 28, 2019

PXE Boot Live Kali Linux | Kali Linux Live Network Booting | Booting Kali Linux Live over HTTP


Need to read first

In short therms you only need to grab live files from ISO and configure menu as follow

label Kali^Live
        menu label Kali^Live
        kernel vmlinuz
        append vga=788 initrd=initrd.img append boot=live components fetch=http://192.168.1.1/filesystem.squashfs

-------

Download Kali PXE Netboot Images


Now, we need to create a directory to hold the Kali Netboot image and download the image we wish to serve from the Kali repos.

mkdir -p /tftpboot 
cd /tftpboot 
 # for 64 bit systems:  
wget http://repo.kali.org/kali/dists/kali/main/installer-amd64/current/images/netboot/netboot.tar.gz 
 # for 32 bit systems:  
wget http://repo.kali.org/kali/dists/kali/main/installer-i386/current/images/netboot/netboot.tar.gz 
tar zxpf netboot.tar.gz 
 rm netboot.tar.gz



Configure Target to Boot From Network


With everything configured, you can now boot your target system and configure it to boot from the network. It should get an IP address from your PXE server and begin booting Kali.



Booting Over HTTP ?

In this example, we will obtain the kernel, initrd, and squashfs filesystem we need from a full Kali Linux release ISO from within the “live” directory. We copy the initrd and kernel into the TFTP root folder, while the squashfs file goes into the web root:

mkdir /mnt/iso 
 mount -o loop kali-linux-1.1.0a-amd64.iso /mnt/iso/  
cp /mnt/iso/live/{initrd.img,vmlinuz} /tftpboot/ 
cp /mnt/iso/live/filesystem.squashfs /var/www/ 
 apachectl start



In this example, we’ll obtain the kernel, initrd, and squashfs filesystem from a full Kali Linux release ISO (in the “live” directory) and then proceed to boot the kernel and initrd over PXE. Once the boot screen appears, we need to alter a few boot parameters as shown in the screenshot below:


Or menu, can look like this

label Kali^Live
        menu label Kali^Live
        kernel vmlinuz
        append vga=788 initrd=initrd.img append boot=live components fetch=http://192.168.1.1/filesystem.squashfs


As the squashfs filesystem loads to RAM, the filesystem itself can’t be larger than the amount of RAM available on the computer – meaning that for booting a standard Kali ISO as shown above, we’d need at least 4 GB of RAM. Of course, this can be remedied by making smaller, custom Kali ISO images, perhaps with different toolsets and uses.



quinta-feira, novembro 14, 2019

android tools linux user in plugdev group; are your udev rules wrong?

https://github.com/M0Rf30/android-udev-rules/blob/master/android-udev.conf

android tools linux user in plugdev group; are your udev rules wrong?


# Clone this repository
git clone https://github.com/M0Rf30/android-udev-rules.git
cd android-udev-rules
# Copy rules file
sudo cp -v 51-android.rules /etc/udev/rules.d/51-android.rules
# OR create a sym-link to the rules file - choose this option if you'd like to update your udev rules using git.
sudo ln -sf "$PWD"/51-android.rules /etc/udev/rules.d/51-android.rules
# Change file permissions
sudo chmod a+r /etc/udev/rules.d/51-android.rules
# If adbusers group already exists remove old adbusers group
groupdel adbusers
# add the adbusers group if it's doesn't already exist
sudo mkdir -p /usr/lib/sysusers.d/ && sudo cp android-udev.conf /usr/lib/sysusers.d/
sudo systemd-sysusers # (1)
# OR on Fedora:
groupadd adbusers
# Add your user to the adbusers group
sudo usermod -a -G adbusers $(whoami)
# Restart UDEV
sudo udevadm control --reload-rules
sudo service udev restart
# OR on Fedora:
sudo systemctl restart systemd-udevd.service
# Restart the ADB server
adb kill-server
# Replug your Android device and verify that USB debugging is enabled in developer options
adb devices
# You should now see your device