A INPUT -p icmp -m icmp -icmp-type 8 -j ACCEPT A INPUT -p tcp -m state -state NEW -m tcp -dport 22 -j ACCEPT ![]() A INPUT -p tcp -m tcp -dport 443 -j ACCEPT A INPUT -p tcp -m tcp -dport 80 -j ACCEPT A INPUT -m state -state RELATED,ESTABLISHED -j ACCEPT A INPUT -d 127.0.0.0/8 ! -i lo -j REJECT -reject-with icmp-port-unreachable Here are my iptables config files for reference: Support IPv6, so I just use iptables/ip6tables directly on the VM (firewalld isĪlso a great frontend to both). My provider doesn’t have external connection control by default, but it does Non-standard port, but like bitlbee it will only need to listen locally.Īnother important variable, depending on your VM/IaaS/ISP provider, IPv6 may beĪvailable, so make sure their connections are also managed in the same way. This is pretty important since bitlbee is technically an IRCd and opening those Easy! Firewall checkĭepending on your VM provider, you may have to either configure incoming/outgoingĬonnections at the hypervisor level, or locally on the VM. Simply registerĪn account, get your domain verified, point your domain registar over, and setupĪ/AAAA records for your VM/Server’s hostname and domain name. It’s a more redundant, secure, and available solution for a minor project thanĪnything I would ever want to setup, configure, and maintain. I use GKG.netĪs a domain registrar, and CloudFlare’s free tier for DNS, because it’s free and ![]() SSL certificate is tied to a domain name that actually resolves. Since we’ll be using HTTPS a lot here, it is a good idea to setup DNS so your # apt-get install -y bitlbee-common bitlbee-facebook ca-certificates nginx-full screen weechat-devel weechat-devel-curses weechat-devel-plugins (Now would be a good time to take a snapshot if doing this on a VM)Īppend the following to your /etc/apt/sources.list file:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |