Automatic routing table refresh

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Automatic routing table refresh

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Automatic routing table refresh
Automatic routing table refresh
2023-02-13 12:37:56
Hardware Version: V2
Firmware Version: 2.0.0 Build 20160922 Rel.68676(s)

Good morning everyone!

I have a doubt and it's because i can't find the information about this topic in TP-Link devices.

I have my default gateway which next hop is my router1 192.168.10.3, as always.

0.0.0.0/0       192.168.10.3         1

But I was configuring a network which switchs routes, after testing by ping (it's a feature in my Mikrotik routers, so it switches the routes automatically based on ping and distance in this routes).

I need to route as backup for default gateway my router2 192.168.10.7, but i'm not sure that this T1600 is capable of testing routes, and after all I have no clue about the state of the routes, as in my Mikrotik devices... So the question is: is it enough to configure this route to my router2 with a distance of 2 (router1 with distance 1) and i'm sure that if my router1 is unreacheable, my switch will forward packets to my router2? Or this is not a feature for this device?

Thank you!

  0      
  0      
#1
Options
4 Reply
Re:Automatic routing table refresh
2023-02-22 16:52:37

  @skeletor3p ward

  0  
  0  
#2
Options
Re:Automatic routing table refresh
2023-02-23 04:37:34

  @skeletor3p 

 

Not a feature.  Not even a feature on TPlink routers...so definitely not on their switches.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#3
Options
Re:Automatic routing table refresh
2023-02-23 15:58:12

  @d0ugmac1 Thank You! Then, the only solution is to manually change my routes when router1 is down.

  0  
  0  
#4
Options
Re:Automatic routing table refresh
2023-02-23 16:33:37 - last edited 2023-02-23 16:34:35

  @skeletor3p 

 

I don't know if you need to do it manually, couldn't you just do something like:

 

0.0.0.0/0       192.168.10.3         1

0.0.0.0/0       192.168.10.7         10

 

That's not as smart as dynamic testing, but it should provide failover at least to .7 in the event that .3 is no longer viable

 

If you have a local machine that's up 24/7 you could emulate the ping test and route update with a script running on that machine/vm/docker image/???

 

 

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#5
Options

Information

Helpful: 0

Views: 631

Replies: 4

Related Articles