thomasschaeferm

Considerations about hosting at home (no business contracts, only private customers) regarding internet protocol and DNS, e.g. for remote access of Raspberry Pi, syncloud, nextcloud, owncloud ...

#	type of access(server) / short description	comments, use cases, problems	client connection via	usage trend
1.	IPv4 public address - directly connected	servers in data centers, PCs terminating ppp-sessions, smart phones with special APN-settings	IPv4	↓
2.	IPv4 private address, with NAT at own router	historical DSL, user needs tcp/udp port forwarding for own server at own router (upnp or manually)	IPv4	↘
3.	IPv4 private address, with NAT at ISP-level (carrier grade NAT)	widely used by mobile internet service providers and some stupid fiber ISP, user needs relays (third party server) or PCP (isn’t available), usually no server possib

thomasschaeferm

<plist version="1.0">
<dict>
<key>ConsentText</key>
<dict>
<key>default</key>
<string>Installs APN web.vodafone.de IPv4v6</string>
</dict>
<key>PayloadContent</key>
<array>
<dict>

thomasschaeferm

#!/bin/bash

PREFIX="$1"
IFACE="$2"

ip netns add jool
ip link add name to_jool typ veth peer name to_world
ip link set up dev to_jool
ip link set dev to_world netns jool
ip netns exec jool ip link set up dev to_world

thomasschaeferm

#!/bin/sh -e
hostname=$1
device=$2
file=$HOME/.dynv6.addr6
[ -e $file ] && old=`cat $file`

if [ -z "$hostname" -o -z "$token" ]; then
  echo "Usage: token=<your-authentication-token> [netmask=64] $0 your-name.dynv6.net [device]"
  exit 1
fi