New answers tagged


Giving each website its own address makes it easier to see which website traffic is for on the network. This can help with accounting, attack detection and prevention and things like that. It may also make it easier to move a website to a different server because you can just move the address with it. If you're not doing things like that's the benefits are ...


They scan to know if you are at risk, thus to hack you later on if they can get their hand on those files. It's often php config's file (with database password in it), wordpress's config file, etc.. Like on my server I see RDP's attempt too, welcome to the internet... ps. Many use fail2ban to block those ip after in an automatic's manner. Fail2ban ...


Thanks for the above answer, but what worked for me is: iptables -t mangle -A OUTPUT -p tcp -m multiport --dports 80,443 -j MARK --set-mark 0x1 iptables -t nat -A POSTROUTING -o tun0 -j MASQUERADE sysctl -w net.ipv4.conf.tun0.rp_filter=2 ip rule add fwmark 0x1 lookup 201 ip route add default dev tun0 table 201


Use rule-based policy routing. Netfilter will add mark to packets: iptables -t mangle -A PREROUTING -p tcp -m multiport --dports 80,443 -j MARK --set-mark 0x1 then Linux should be told if it sees this mark it should use alternate routing table: ip rule add fwmark 0x1 lookup 201 and you need a route in that table: ip route add default via [your-...

Top 50 recent answers are included