Skip to content

Instantly share code, notes, and snippets.

View cryptopepe's full-sized avatar
🐢
NotAllFrogs

cryptopepe cryptopepe

🐢
NotAllFrogs
View GitHub Profile
Node / Iquidus Explorer Setup for Dummies
Pulse Crypto is used in this example.
This Tutorial is going to create a Daemon (node) and install Explorer.
THIS IS NOT GOING TO CREATE A GUI CLIENT.
Follow the instructions in [whatever coin name] docs folder Unix build - some builds are different.
I setup this up on both Ubuntu 15.10 and 16.04 with no issues.
You can create an account on vultr and get $50 free to be used in 2 months.
@cryptopepe
cryptopepe / hfsc-shape.sh
Created March 3, 2019 02:29 — forked from eqhmcow/hfsc-shape.sh
HFSC - linux traffic shaping's best kept secret
#!/bin/bash
# As the "bufferbloat" folks have recently re-discovered and/or more widely
# publicized, congestion avoidance algorithms (such as those found in TCP) do
# a great job of allowing network endpoints to negotiate transfer rates that
# maximize a link's bandwidth usage without unduly penalizing any particular
# stream. This allows bulk transfer streams to use the maximum available
# bandwidth without affecting the latency of non-bulk (e.g. interactive)
# streams.
@cryptopepe
cryptopepe / socket.io.js
Created March 8, 2019 09:27 — forked from vene/socket.io.js
socketio-client 0.9.16 fork
/*! Socket.IO.js build:0.9.16, development. Copyright(c) 2011 LearnBoost <dev@learnboost.com> MIT Licensed */
/* Modifications by Vlad Niculae <vlad@vene.ro>
Available at https://gist.github.com/vene/c0657d854ae74a4511d2
Forked from https://raw.githubusercontent.com/Automattic/socket.io-client/ \
0.9.16/dist/socket.io.js
Changes:
@cryptopepe
cryptopepe / osxvpnrouting.markdown
Created June 9, 2020 00:44
Routing tips for VPNs on OS X

Routing tips for VPNs on OS X

When VPNs Just Work™, they're a fantastic way of allowing access to a private network from remote locations. When they don't work it can be an experience in frustration. I've had situations where I can connect to a VPN from my Mac, but various networking situations cause routing conflicts. Here are a couple of cases and how I've been able to get around them.

Specific cases

Case 1: conflicting additional routes.

In this example the VPN we are connecting to has a subnet that does not conflict with our local IP, but has additional routes that conflict in some way with our local network's routing. In my example the remote subnet is 10.0.x.0/24, my local subnet is 10.0.y.0/24, and the conflicting route is 10.0.0.0/8. Without the later route, I can't access all hosts on the VPN without manually adding the route after connecting to the VPN: