Just like many other League addicts, ever since the Vanguard incident, TFT has been a no-go....
except it isn't, since the Android version works just as fine, after some tweaks!
opkg update | |
opkg install dnsproxy | |
# Ensure, that the NTP server can work without DNS | |
uci del system.ntp.server | |
uci add_list system.ntp.server='194.177.4.1' # 0.openwrt.pool.ntp.org | |
uci add_list system.ntp.server='213.222.217.11' # 1.openwrt.pool.ntp.org | |
uci add_list system.ntp.server='80.50.102.114' # 2.openwrt.pool.ntp.org | |
uci add_list system.ntp.server='193.219.28.60' # 3.openwrt.pool.ntp.org | |
uci commit system |
#!/bin/sh | |
# Set kernel parameters in /etc/sysctl.conf | |
cat << EOF > /etc/sysctl.conf | |
# Increase maximum number of open file descriptors | |
fs.file-max = 1000000 | |
# Increase maximum number of inotify instances per user | |
fs.inotify.max_user_instances = 8192 |
server: | |
########################################################################### | |
# BASIC SETTINGS | |
########################################################################### | |
# Time to live maximum for RRsets and messages in the cache. If the maximum | |
# kicks in, responses to clients still get decrementing TTLs based on the | |
# original (larger) values. When the internal TTL expires, the cache item | |
# has expired. Can be set lower to force the resolver to query for data | |
# often, and not trust (very large) TTL values. | |
cache-max-ttl: 86400 |
# IPv6 Configuration | |
# -> note that I have disabled ip6 for our internet-connection (wan/eth0) because | |
# -> my upstream/ISP (still) does not do IPv6. The rest, even localhost, does ip6 stuff. | |
net.ipv6.conf.all.disable_ipv6 = 0 | |
net.ipv6.conf.default.disable_ipv6 = 0 | |
net.ipv6.conf.lo.disable_ipv6 = 0 | |
net.ipv6.conf.eth0.disable_ipv6 = 1 | |
net.ipv6.conf.wan.disable_ipv6 = 1 | |
# Packet Forwarding |