A few of my VULTR cloud nodes has this issue. About every other day we need to apply these sudo commands in order to get incoming connections. I believe this occurs on Ded 12 only.
Any thoughts?
sudo iptables -P INPUT ACCEPT
sudo iptables -P OUTPUT ACCEPT
sudo iptables -P FORWARD ACCEPT
sudo iptables -F
Ken N6KNE
Doesn’t that essentially open every port to the world? Probably not the policy you’re looking for. My nodes all have a policy of drop everything except specified UDP and TCP ports, but I’m not using Vultr.
Sounds like you need to change firewall rules on the Vultr portal, or you can remove your machine from the firewall group and manage it yourself with raw iptables, UFW or similar. It’s been a minute since I managed a Vultr node, but that’s what I remember. Their firewall implementation is managed from outside the virtual machine.
This sudo info did come from VULTR but I definitely understand what you're saying. Thanks for your reply. I'm not at all knowledgeable with vultr firewall.
the Vultr network is really really fast and it's probably a very bad idea to open the firewall to everything flying around!
as you begin configuring and testing, restricting packet accepts to only your home netblock or even just your public-IP-of-the-day is sufficient (allowing the allstarlink.org addresses will become necessary, too)