Business Community > Gateways > Policy Routing with two ISPs (not Omada-based!)
< Gateways

Policy Routing with two ISPs (not Omada-based!)

Policy Routing with two ISPs (not Omada-based!)

Policy Routing with two ISPs (not Omada-based!)
Policy Routing with two ISPs (not Omada-based!)
3 weeks ago - last edited 3 weeks ago
Tags: #VLAN & Multi-Networks #Routing
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.3.0 Build 20250428 Rel.18967

Hej there!

 

Has anyone successfully applied Policy Routing with the ER605?
The purpose is simply to split traffic between two ISPs - but either I am overseeing something or the router is doing something odd:

 

1. WAN1, connected to ISP1 (Dynamic IP)

2. WAN2, connected to ISP2 (PPPoE)

3. LAN "pbx", subnet 192.168.231.0/30 (with vlan "231" assigned to it)

4. IP Group "pbx" defined, which refers to subnet, mentioned above

5. Load Balancing enabled

5. Policy Routing "pbx" defined (and enabled), which covers "ALL" services for IP source and destination group "pbx" and "WAN2" (Mode: "Only")

 

Gateway IP is reachable from the PBX and vice-versa.

 

That's it, so far.

And no success, so far as well.

 

Anything obvious I may have overseen?
Regrettably, there's no real HowTo (and if so, I wasn't able to to find it) for this matter.

 

 

Open for great ideas or simple thoughts to get this solved.

 

Thanks in advance,

Edray

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Policy Routing with two ISPs (not Omada-based!)-Solution
3 weeks ago - last edited 3 weeks ago

Hej  @Clive_A !

 

Thanks for coming back.

 

Not sure what's confusing you with my description

 

But the good news are: I could resolve the issue a minute ago:

 

When doing PR, it is essential that the source and destination networks are covered by the defined IP Group.

In my attempt I set both, src and dst, to "pbx" - a group covers the affected LAN ("pbx"), only.

Doing so, the router can't send anything to WAN2, as it is not part of the used IP Group.

 

As soon as the destination IP group was set to the predefined group "IPGROUP_ANY" it works as expected.

 

Remains another question, which is how to change a default route priority (e.g. metric) when having multiple default routes?

The least preferred solution would be another PR entity which sends anything but "pbx" to WAN1...

 

I will browse the KB for this...

 

 

Thanks!

No I only have to find out how to set a post as "resolved" ;-)

Recommended Solution
  1  
  1  
#3
Options
3 Reply
Re:Policy Routing with two ISPs (not Omada-based!)
3 weeks ago - last edited 3 weeks ago

  @Edray 

Not sure what your title means. Not sure about your description as well.

Edray wrote

Hej there!

 

 

Gateway IP is reachable from the PBX and vice-versa.

 

That's it, so far.

And no success, so far as well.

 

Howto, you can find both on the forum and the official website using the keywords Policy Routing.  

  1  
  1  
#2
Options
Re:Policy Routing with two ISPs (not Omada-based!)-Solution
3 weeks ago - last edited 3 weeks ago

Hej  @Clive_A !

 

Thanks for coming back.

 

Not sure what's confusing you with my description

 

But the good news are: I could resolve the issue a minute ago:

 

When doing PR, it is essential that the source and destination networks are covered by the defined IP Group.

In my attempt I set both, src and dst, to "pbx" - a group covers the affected LAN ("pbx"), only.

Doing so, the router can't send anything to WAN2, as it is not part of the used IP Group.

 

As soon as the destination IP group was set to the predefined group "IPGROUP_ANY" it works as expected.

 

Remains another question, which is how to change a default route priority (e.g. metric) when having multiple default routes?

The least preferred solution would be another PR entity which sends anything but "pbx" to WAN1...

 

I will browse the KB for this...

 

 

Thanks!

No I only have to find out how to set a post as "resolved" ;-)

Recommended Solution
  1  
  1  
#3
Options
Re:Policy Routing with two ISPs (not Omada-based!)
3 weeks ago

  @Edray 

Edray wrote

Hej  @Clive_A !

 

Thanks for coming back.

 

Not sure what's confusing you with my description

 

But the good news are: I could resolve the issue a minute ago:

 

When doing PR, it is essential that the source and destination networks are covered by the defined IP Group.

In my attempt I set both, src and dst, to "pbx" - a group covers the affected LAN ("pbx"), only.

Doing so, the router can't send anything to WAN2, as it is not part of the used IP Group.

 

As soon as the destination IP group was set to the predefined group "IPGROUP_ANY" it works as expected.

 

Remains another question, which is how to change a default route priority (e.g. metric) when having multiple default routes?

The least preferred solution would be another PR entity which sends anything but "pbx" to WAN1...

 

I will browse the KB for this...

 

 

Thanks!

No I only have to find out how to set a post as "resolved" ;-)

By default, clients can access the gateway IP address without a problem. If you have not restricted them by ACL or blocked remote access.

  0  
  0  
#4
Options

Information

Helpful: 0

Views: 252

Replies: 3

Tags

VLAN & Multi-Networks Routing
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.