Could someone explain to me this question I have:
- If I have a class A IP, for example IP 10.XXX, is 10.0.0.0 not taken because it is the network IP and 10.255.255.255 is not taken because it is broadcast?
I am studying networks and a question has arisen regarding IP addressing.
IP addresses are class A, B and C mainly.
- The A indicates that there are 8 bits for the network and 24 bits for the host, that means that I have 256 possible networks and 16 million computers for each network, right?
- The B indicates that there are 16 bits for network and 16 for host, that means 65,000 networks and 65,000 computers in each network?
Please someone explain to me what I'm doing wrong...
It's possible?
speaking of IP networks in general, and the Internet in particular, although not limited to these, but also including local networks (on this side of the router)
Is there any way in which two processes/machines/even viruses can communicate other than through a domain name and an IP??
and in a certain way, the domain name has to be converted into an IP through a DNS resolution
I ask in the context of cybersecurity and mechanisms that malwares have to communicate with each other, one way is to know the IP of the C&C or the victim, and use it directly. And the other, from what I see, is to "encode" a domain type xyxyxyxxyxyx.xyxyxy.tk and use this as a bridge for the IP C&C or IP of the victim
Context I have been blocked by sonicwall for the game league of legends to connect to the network. I have access to the sonicwall and have already tried loads of things to see if I can override the rules that block that for me.
From the Access Rules - this rule appeared denied
And indeed, I enabled it, I ping some IP address grouped in LOL-Services and it is successful. What happens is that doing a network study of the game tells me this:
Ping to 138.0.13.100 Game Servers (MIA):
Haciendo ping a 138.0.13.100 con 32 bytes de datos:
Estad¡sticas de ping para 138.0.13.100:
Paquetes: enviados = 4, recibidos = 0, perdidos = 4
(100% perdidos),
Prueba 3 de 8: LQ:
No se puede resolver el nombre del sistema de destino lqak.la1.lol.riotgames.com.
Prueba 4 de 8: LQ2:
Traza a la direcci¢n prod.la1.lol.riotgames.com [66.151.33.24]
sobre un m ximo de 20 saltos:
1 24 ms 42 ms 18 ms 10.141.16.1
2 35 ms 16 ms 15 ms 10.166.51.26
3 20 ms 15 ms 15 ms 10.166.51.25
4 30 ms 38 ms 31 ms static-adsl200-24-34-84.epm.net.co [200.24.34.84]
5 38 ms 34 ms 39 ms static-adsl200-24-34-107.epm.net.co [200.24.34.107]
6 29 ms 29 ms 30 ms 206.223.124.158
7 45 ms 44 ms 44 ms globenet-81.as52320.net [200.16.69.81]
8 67 ms 65 ms 64 ms globenet-60.as52320.net [200.16.69.60]
9 73 ms 72 ms 75 ms 138.204.238.163
10 74 ms 81 ms 77 ms 104.160.136.52
11 * * * Tiempo de espera agotado para esta solicitud.
12 * * * Tiempo de espera agotado para esta solicitud.
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * * Tiempo de espera agotado para esta solicitud.
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 * * * Tiempo de espera agotado para esta solicitud.
20 * * * Tiempo de espera agotado para esta solicitud.
Prueba 6 de 8: NA:
Traza a 192.64.170.107 sobre caminos de 20 saltos como m ximo.
1 16 ms 17 ms 19 ms 10.141.16.1
2 21 ms 15 ms 23 ms 10.166.51.26
3 15 ms 15 ms 16 ms 10.166.51.25
4 16 ms 22 ms 21 ms static-adsl200-24-33-235.epm.net.co [200.24.33.235]
5 61 ms 60 ms 63 ms static-adsl200-24-33-243.epm.net.co [200.24.33.243]
6 70 ms 60 ms 61 ms jax-b1-link.telia.net [62.115.146.170]
7 76 ms 76 ms * atl-b22-link.telia.net [62.115.119.155]
8 86 ms 85 ms 88 ms chi-b21-link.telia.net [62.115.113.19]
9 86 ms 98 ms 92 ms riot-ic-315569-chi-b21.c.telia.net [62.115.63.66]
10 88 ms 91 ms 89 ms 104.160.131.44
11 90 ms 90 ms 89 ms 104.160.131.101
12 * * * Tiempo de espera agotado para esta solicitud.
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * * Tiempo de espera agotado para esta solicitud.
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 * * * Tiempo de espera agotado para esta solicitud.
20 * * * Tiempo de espera agotado para esta solicitud.
What worries me the most is that in no menu of the sonicwall is anything related to those IP addresses that are being blocked.
What dou you recommend?
Good morning, I am installing a VPN server in such a way that I have two virtual machines, one of them has the OpenVPN service and the other one has an Apache service running, both machines are in the same network segment 10.8.0.1 (VPN) and 10.8.0.3 (Apache) the Apache virtual machine does not have Internet access while VPN does, we have a static address and a forwarded port on the Router.
This is our server.conf file configuration:
dev tun
proto udp
port 1194
ca /etc/openvpn/easy-rsa/keys/ca.crt
cert /etc/openvpn/easy-rsa/keys/vpn.crt
key /etc/openvpn/easy-rsa/keys/vpn.key
dh /etc/openvpn/easy-rsa/keys/dh2048.pem
server 10.8.0.0 255.255.255.0
ifconfig 10.8.0.1 10.8.0.2
push "route 10.8.0.1 255.255.255.255"
push "route 10.8.0.0 255.255.255.0"
push "route 192.168.1.220 255.255.255.0"
push "redirect-gateway def1"
client-to-client
duplicate-cn
keepalive 10 120
tls-auth /etc/openvpn/easy-rsa/keys/ta.key 0
cipher AES-256-CBC
comp-lzo
user nobody
group nogroup
persist-key
persist-tun
status /var/log/openvpn-status.log 20
log /var/log/openvpn.log
verb1
When establishing a VPN connection from the client, whether Windows or OSx connects perfectly, it even browses the Internet from this new public IP, but nevertheless it is unable to ping with the machine that has Apache and thanks the VPN is already inside your own network. It is as if OpenVPN made small subnets every time someone connects, since the network mask that it assigns to the client is always 255.255.255.252