Skip to content

Instantly share code, notes, and snippets.

  • Are any IGMP/MLD messages coming from the mesh?
  • Is the node / br-client regularly (20s) querying (IGMP/MLD query messages)?
  • Are IPv6 destinations still reachable fine?
  • With two hosts connected to an AP via wifi, do multicast packets arrive with a mangled destination MAC address?
  • Does the output of "$ bridge mdb show dev br-client" look sane? That is, are there no entries for bat0? (package: http://openwrt.draic.info/chaos_calmer/15.05/ar71xx/generic/packages/base/ip-bridge_4.0.0-1_ar71xx.ipk)
  • Does removing the MULTICAST_OUT_ICMPV6 rules in /lib/gluon/ebtables/105-mcast-drop-mld still prevent IGMP/MLD messages from the mesh?
  • Put two to eight nodes in a room, connected to the mesh. How greenish or redish are the link qualities shown with or without these patches?
  • Are IPv6 link-local multicast addresses from hosts on the same node still pingable fine? (e.g. get address via "$ ip maddr show dev $dev" on a host, try to ping it from another host on the same node)
  • Optional: Try to stream a video
@T-X
T-X / test.sh
Created May 26, 2016 05:10
test and memory monitoring script for a setup with many global TT entries
#!/bin/bash
DIR=/mnt/dev
OUT=/mnt/dev/logs
DST="fe80::6670:2ff:feae:72e4%eth1"
num=10
wait_for_link() {
echo -n "Waiting for link..."
var EstimoteSticker = require('./estimote-sticker');
var heapdump = require('heapdump');
EstimoteSticker.on('discover', function(estimoteSticker) {
// console.log(estimoteSticker);
});
EstimoteSticker.startScanning();
#!/bin/bash
BATDIR="/mnt/batman-adv-t_x"
BATALGO="BATMAN_IV"
NUMNODES=3
modules="batman-adv"
modules_extern=
$ ./zcutil/build.sh
+++ readlink -f ./zcutil/build.sh
++ dirname /mnt/main/linus/dev/zcash/zcutil/build.sh
+ cd /mnt/main/linus/dev/zcash/zcutil/..
+ LCOV_ARG=
+ HARDENING_ARG=--enable-hardening
+ TEST_ARG=
+ '[' x = x--enable-lcov ']'
+ '[' x = x--disable-tests ']'
+ MINING_ARG=
#!/bin/sh
# License: CC0
MODULESFILE="$1"
MODULESDIR="/lib/modules/4.4.102"
NUMRUNS=30
drop_caches() {
/usr/lib/autoupdater/download.d/95drop_caches > /dev/null
@T-X
T-X / meson8b-odroidc1.dts+mmc
Created January 22, 2018 09:30
Tried against a 4.15-rc8 kernel, meson8b-odroidc1.dts+mmc crashes. Removing the card detection and replacing it with the "non-removable" attribute (meson8b-odroidc1.dts+mmc+nonremovable) works without crashes.
/*
* Copyright 2015 Endless Mobile, Inc.
* Author: Carlo Caione <carlo@endlessm.com>
*
* This file is dual-licensed: you can use it either under the terms
* of the GPL or the X11 license, at your option. Note that this dual
* licensing only applies to this file, and not this project as a
* whole.
*
* a) This library is free software; you can redistribute it and/or
#!/bin/sh
exec /usr/bin/gdb -ex "set follow-fork-mode child" -ex run -ex bt -ex quit --args ~/install/bin/seaf-server "$@" 2>&1 | tee /tmp/seaf-server-$$-`date +%s`.log
#!/bin/sh
valgrind ~/install/bin/seaf-server "$@" 2>&1 | tee /tmp/seaf-server-$$-`date +%s`.log
Trying to boot a Debian Stretch (stable) with the 4.14.13 kernel
from a VM host running Debian oldoldstable
(uname -a: Linux kamino 3.2.0-4-amd64 #1 SMP Debian 3.2.89-2 x86_64 GNU/Linux)
results in:
[ 0.000000] Linux version 4.14.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-0.bpo.3-amd64 root=UUID=6f810b9c-5b6e-4b3a-8af0-a86bbb924159 ro console=ttyS0
[ 0.000000] x86/fpu: x87 FPU will use FXSAVE
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009bbff] usable