thiagokokada

[Vivo Fibra] Usando RTF3507VW-N1 em modo bridge

Por que usar o RTF3507VW-N1 em modo bridge?

O roteador Askey RTF3507VW-N1 fornecido pela Vivo tem vários problemas:

• Existe um cache interno de DNS (usando o dnsmasq?) bugado: ao fazer a mesma requisição DNS duas vezes seguidas, a primeira resposta vem correta, porém na seguinte temos:

saivert

Overly long sound card descriptions is a problem and they sometimes cause problems for some GUIs as pavucontrol where you need to make the window very wide in order to accommodate the strings. With pulseaudio you can rename them directly in pavucontrol by right-clicking the Port dropdown as long as you have the module-device-manager pulseaudio module loaded. Here is how to do the same in pipewire:

Add something like the following to your `/etc/pipewire/media-session.d/alsa-monitor.conf/ file:

    {
        matches = [
            {
                node.name = "alsa_output.pci-0000_02_02.0.analog-stereo"
            }

gpchelkin

#!/bin/bash

# Tested on Linux Mint 18.3 / Ubuntu 16.04 with PulseAudio 8.0.
# No need for superuser.
# You can map it to keyboard shortcut and press when bluetooth audio starts lagging.
# Reference:
# https://askubuntu.com/a/171165/373130
# https://askubuntu.com/a/72076/373130
      
BLUEZCARD=`pactl list cards short | grep bluez | awk '{print $1}'`

Pulimet

adb help // List all comands

== Adb Server
adb kill-server
adb start-server 

== Adb Reboot
adb reboot
adb reboot recovery 
adb reboot-bootloader

cryzed

Disclaimer: Please follow this guide being aware of the fact that I'm not an expert regarding the things outlined below, however I made my best attempt. A few people in IRC confirmed it worked for them and the results looked acceptable.

Attention: After following all the steps run gdk-pixbuf-query-loaders --update-cache as root, this prevents various gdk-related bugs that have been reported in the last few hours. Symptoms are varied, and for Cinnamon the DE fails to start entirely while for XFCE the icon theme seemingly can't be changed anymore etc.

Check the gist's comments for any further tips and instructions, especially if you are running into problems!

Screenshots

Results after following the guide as of 11.01.2017 13:08:

t413

#!/usr/bin/env sh
## update.sh - manage a OpenWRT LetsEncrypt https instalation
# HOWTO: 
# - put update.sh in its own directory (like /root/.https)
# - run ./update.sh your.domain.com (that domain needs to point to your router)
#  * this get an issued cert from letsencrypt.org using the webroot verification method
#  * also installs curl and ca-certificates packages
# - use crontab -e; add the line `0 0 * * * "/root/.https/update.sh" >>/root/.https/log.txt 2>&`
#  * this runs the update every day, logging everything to log.txt
#

ctrl-freak

https://stackoverflow.com/a/18003462/348146

None of these suggestions worked for me, because Android was appending a sequence number to the package name to produce the final APK file name (this may vary with the version of Android OS). The following sequence of commands is what worked for me on a non-rooted device:

1. Determine the package name of the app, e.g. com.example.someapp. Skip this step if you already know the package name.

   adb shell pm list packages

   Look through the list of package names and try to find a match between the app in question and the package name. This is usually easy, but note that the package name can be completely unrelated to the app name. If you can't recognize the app from the list of package names, try finding the app in Google Play using a browser. The URL for an app in Google Play contains the package name.

mmasaki

# /etc/systemd/system/iperf.service
[Unit]
Description=iperf server
After=syslog.target network.target auditd.service

[Service]
ExecStart=/usr/bin/iperf -s

[Install]
WantedBy=multi-user.target

wpscholar

Typing vagrant from the command line will display a list of all available commands.

Be sure that you are in the same directory as the Vagrantfile when running these commands!

Creating a VM

• vagrant init -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.
• vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.

Starting a VM

• vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)

willurd

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000