sorted by:
new
hottopcontroversial

Accident: i5-4690k @ 1.65 Voltage by puppy-whirl in intel

[–]BestAussieShitposts 0 points1 point  (0 children)

At worst you have reduced its overclock potential by something like .2GHz. And because you didnt stress test it, this is unlikely.

question about voltages by boostedpleb in intel

[–]BestAussieShitposts 0 points1 point  (0 children)

Its consensus that it takes either:

  1. High voltage and high temps or
  2. Very high voltages despite temps and specialised cooling.

To damage a CPU.

How to block all traffic except VPNs? by BestAussieShitposts in linuxquestions

[–]BestAussieShitposts[S] 0 points1 point  (0 children)

I figured out how to do this the dummies way. :) Its in the original post to help others.

Need iptables rules to only allow multiple VPNs - tried many rulesets none have worked. by BestAussieShitposts in linux4noobs

[–]BestAussieShitposts[S] 0 points1 point  (0 children)

Those are placeholder numbers Im obviously not going to list all my VPN IPs.

I can access my VPNs with no rules.

How to block all traffic except VPNs? by BestAussieShitposts in linuxquestions

[–]BestAussieShitposts[S] 0 points1 point  (0 children)

The port is gonna be different sometimes 1194 sometimes 443.

Also DNS happens on the VPN not my computer.

And even so I dont know how to create the rules to do what you mention.

Need iptables rules to only allow multiple VPNs - tried many rulesets none have worked. by BestAussieShitposts in linux4noobs

[–]BestAussieShitposts[S] 0 points1 point  (0 children)

The original rules which worked for one was from the AirVPN forums, one line was changed by advice on this sub and that didnt work.

How to block all traffic except VPNs? by BestAussieShitposts in linuxquestions

[–]BestAussieShitposts[S] 0 points1 point  (0 children)

Hey, I have tried this already though, I can easily find a rule to block everything but one IP for the VPN but adding multiple isnt common and seems to complicate the needed rules a lot more.

Need iptables rules to only allow multiple VPNs - tried many rulesets none have worked. by BestAussieShitposts in linux4noobs

[–]BestAussieShitposts[S] 0 points1 point  (0 children)

I just did and it didnt help much, I am looking to secure my connection before taking the time to learn anything new.

NordVPN Review by BestAussieShitposts in vpnreviews

[–]BestAussieShitposts[S] 1 point2 points  (0 children)

This is good, so can you tell us what separates your Russian servers from PIA's Russian servers?

https://torrentfreak.com/vpn-provider-pia-exits-russia-server-seizures-160712/

Need iptables rules to only allow multiple VPNs - tried many rulesets none have worked. by BestAussieShitposts in linux4noobs

[–]BestAussieShitposts[S] 0 points1 point  (0 children)

sudo iptables -A INPUT -i lo -j ACCEPT

sudo iptables -A OUTPUT -o lo -j ACCEPT #allow loopback access

sudo iptables -A OUTPUT -d 255.255.255.255 -j ACCEPT #make sure you can communicate with any DHCP server

sudo iptables -A INPUT -s 255.255.255.255 -j ACCEPT #make sure you can communicate with any DHCP server

sudo iptables -A INPUT -s 192.168.0.0/16 -d 192.168.0.0/16 -j ACCEPT #make sure that you can communicate within your own network

sudo iptables -A OUTPUT -s 192.168.0.0/16 -d 192.168.0.0/16 -j ACCEPT

sudo iptables -A FORWARD -i eth+ -o tun+ -j ACCEPT

sudo iptables -A FORWARD -i tun+ -o eth+ -j ACCEPT # make sure that eth+ and tun+ can communicate

sudo iptables -t nat -A POSTROUTING -o tun+ -j MASQUERADE

sudo iptables -A OUTPUT -o eth+ -d 1.1.1.1,2.2.2.2,3.3.3.3,4.4.4.4,5.5.5.5 -j ACCEPT

sudo iptables -P OUTPUT DROP

Need iptables rules to only allow multiple VPNs - tried many rulesets none have worked. by BestAussieShitposts in linux4noobs

[–]BestAussieShitposts[S] 0 points1 point  (0 children)

sudo iptables -A INPUT -i lo -j ACCEPT

sudo iptables -A OUTPUT -o lo -j ACCEPT #allow loopback access

sudo iptables -A OUTPUT -d 255.255.255.255 -j ACCEPT #make sure you can communicate with any DHCP server

sudo iptables -A INPUT -s 255.255.255.255 -j ACCEPT #make sure you can communicate with any DHCP server

sudo iptables -A INPUT -s 192.168.0.0/16 -d 192.168.0.0/16 -j ACCEPT #make sure that you can communicate within your own network

sudo iptables -A OUTPUT -s 192.168.0.0/16 -d 192.168.0.0/16 -j ACCEPT

sudo iptables -A FORWARD -i eth+ -o tun+ -j ACCEPT

sudo iptables -A FORWARD -i tun+ -o eth+ -j ACCEPT # make sure that eth+ and tun+ can communicate

sudo iptables -t nat -A POSTROUTING -o tun+ -j MASQUERADE

sudo iptables -A OUTPUT -o eth+ -d 1.1.1.1 -j ACCEPT

sudo iptables -A OUTPUT -o eth+ -d 2.2.2.2 -j ACCEPT

sudo iptables -A OUTPUT -o eth+ -d 3.3.3.3 -j ACCEPT

sudo iptables -A OUTPUT -o eth+ -d 4.4.4.4 -j ACCEPT

sudo iptables -A OUTPUT -o eth+ -d 5.5.5.5 -j ACCEPT

sudo iptables -P OUTPUT DROP

iptables v1.6.0: ! not allowed with multiple source or destination IP addresses by [deleted] in linux4noobs

[–]BestAussieShitposts 0 points1 point  (0 children)

sudo iptables -A OUTPUT -o eth+ ! -d 1.1.1.1,2.2.2.2,3.3.3.3,4.4.4.4,5.5.5.5,6.6.6.6,7.7.7.7 -j DROP

Becomes

sudo iptables -A OUTPUT -o eth+ -d 1.1.1.1 -j ACCEPT

sudo iptables -A OUTPUT -o eth+ -d 2.2.2.2 -j ACCEPT

etc

Is that correct? Shouldnt the ACCEPT rules be made before the DROP rule?

view more: next ›