Static Routing buggy in my router
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
My TP-Link device "forgets" the static routes I assigned to block IP addresses
I have to activate them again for them to work, if I restart the router these routes do not work
I want to block the IP range of the Badoo social network
When are you going to fix this bug?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @damvs
Will the static routing table still display the rule you've configured, but it doesn't take effect, or the rule disappears? Can I have the detailed network layout that how do you want to achieve via this static routing setting?
Can I know who is your ISP? Does it provide an IPv6 connection?
- Copy Link
- Report Inappropriate Content
Will the static routing table still display the rule you've configured, but it doesn't take effect, or the rule disappears? Can I have the detailed network layout that how do you want to achieve via this static routing setting?
Doesn't take effect
Can I know who is your ISP? Does it provide an IPv6 connection?
Is a local ISP in Spain, don't have IPv6 connection. I bought the router on my own
- Copy Link
- Report Inappropriate Content
Hi @damvs
Can I have the detailed network layout that how do you want to achieve via this static routing setting? Can you please explain it in more detail? We will check if that can be achieved or not.
- Copy Link
- Report Inappropriate Content
@Kevin_Z What I want is to block access (range) to that IP, that is why I have invented a different route (to my router) so that it does not allow access to the domains associated with said IP
- Copy Link
- Report Inappropriate Content
@damvs This is the ping of Badoo
C:\Users\equipo>ping 31.222.67.112
Haciendo ping a 31.222.67.112 con 32 bytes de datos:
Respuesta desde 31.222.67.112: bytes=32 tiempo=46ms TTL=48
Respuesta desde 31.222.67.112: bytes=32 tiempo=47ms TTL=48
Respuesta desde 31.222.67.112: bytes=32 tiempo=47ms TTL=48
Respuesta desde 31.222.67.112: bytes=32 tiempo=47ms TTL=48
Estadísticas de ping para 31.222.67.112:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 46ms, Máximo = 47ms, Media = 46ms
- Copy Link
- Report Inappropriate Content
This is the ping of Badoo
C:\Users\equipo>ping 31.222.67.112
Haciendo ping a 31.222.67.112 con 32 bytes de datos:
Respuesta desde 31.222.67.112: bytes=32 tiempo=46ms TTL=48
Respuesta desde 31.222.67.112: bytes=32 tiempo=47ms TTL=48
Respuesta desde 31.222.67.112: bytes=32 tiempo=47ms TTL=48
Respuesta desde 31.222.67.112: bytes=32 tiempo=47ms TTL=48
Estadísticas de ping para 31.222.67.112:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 46ms, Máximo = 47ms, Media = 46ms
When i re-active the Static Routing
C:\Users\equipo>ping 31.222.67.112
Haciendo ping a 31.222.67.112 con 32 bytes de datos:
Respuesta desde 192.168.0.1: Host de destino inaccesible.
Respuesta desde 192.168.0.1: Host de destino inaccesible.
Respuesta desde 192.168.0.1: Host de destino inaccesible.
Respuesta desde 192.168.0.1: Host de destino inaccesible.
Estadísticas de ping para 31.222.67.112:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 429
Replies: 6
Voters 0
No one has voted for it yet.