Hot answers tagged ip
These addresses are coming from your private network or are somehow spoofed. Addresses from 10.0.0.0 to 10.255.255.255 are reserved for private networks (not connected to the internet) http://tldp.org/HOWTO/IP-Masquerade-HOWTO/addressing-the-lan.html
Edited following OP's clarification on the use case: You can not do that using the latest official release of bash (currently 4.3.30 according to this page). lib/sh/netopen.c shows that bash opens a UDP socket (SOCK_DGRAM) then directly tries to connect without looking at the ip address to determine whether it would make sense to set specific socket options ...
Those IP Address will have no Country of Origin, as they are deemed Private Class A addresses. From my /etc/hosts file: # # According to RFC 1918, you can use the following IP networks for private # nets which will never be connected to the Internet: # # 10.0.0.0 - 10.255.255.255 # 172.16.0.0 - 172.31.255.255 # ...
You would want to add this to the iptables in order to block an IP: iptables -A INPUT -s <ipaddress> -j DROP Per the man pages: DROP means to drop the packet on the floor.
The problem with blocking on IP is the person on the attacking end will just move to another IP, if they're intent on attacking your IP. The fail2ban facility is extremely effective at blocking IPs, so IPs block for certain periods of time + then unblock. This ensures if you incorrectly block an IP by accident, it will eventually unblock. Using fail2ban ...
Apparently your router cannot 'bounce' the connections that arrive from internal network, like explained f.e. in IPF FAQ, so your next best option is to use a proxy on the external network.
Only top voted, non community-wiki answers of a minimum length are eligible