SD-WAN and PPPoE

[alex_buric]

I have Fortigate 60D with FortiOS 6.06 First ISP - static IP

Second ISP - PPPoE

When I add both of them to SD-WAN and make a static route 0.0.0.0/0.0.0.0 to SD-WAN interface in routing table appear two line:

Routing table for VRF=0
S* 0.0.0.0/0 [1/0] via 193.200.32.2, ppp1
                   [1/0] via 31.128.69.193, wan2

But after few seconds (5-6) line with ppp1 interface disappearing

[alex_buric]

I think problem with distance/priority.

I can change distance for PPPoE connection, but can'n for static

[emnoc]

For SDWAN you should not need to do that. 

Ken Felix

[alex_buric]

Does anyone has same problem?

[ede_pfau]

This behavior is correct.

"There can only be ONE..."

in this case, default route.

What exactly is your problem with this? Do you want to prefer the PPPoE WAN connection? Then steer that with SD-WAN policy.

[alex_buric]

ede_pfau wrote:

This behavior is correct.

"There can only be ONE..."

in this case, default route.

What exactly is your problem with this? Do you want to prefer the PPPoE WAN connection? Then steer that with SD-WAN policy.

Behavior is incorrect.

There is routing table from another Fortigate with four WAN uplinks in SD-WAN:

Routing table for VRF=0
S* 0.0.0.0/0 [1/0] via 195.24.130.193, edge-trifle
                         [1/0] via 62.64.83.77, edge-kyivstar
                         [1/0] via 83.170.209.241, hub-kyivstar
                         [1/0] via 195.24.148.9, hub-trifle

As you can see - all gateways have the same distance/priority and present in routing table permamently.

But all of them a static fiber connection

On another Fortigate:

WAN1 - static fiber

WAN2 - ADSL PPPoE

After settings up necessary configuration routing table looks fine:

Routing table for VRF=0
S* 0.0.0.0/0 [1/0] via 193.200.32.2, ppp1
                   [1/0] via 31.128.69.193, wan2

But after 10-20 seconds default from ppp1 interface disappearing

S* 0.0.0.0/0 [1/0] via 31.128.69.193, wan2
                  

[ede_pfau]

As I said, it is correct.

Unless you specify ALL distances and priorities with equal values - which gives you ECMP, that is load-balancing via routes.

Question still remains unanswered: what is your goal? Use both paths? Prefer the other?

[alex_buric]

ede_pfau wrote:

As I said, it is correct.

Unless you specify ALL distances and priorities with equal values - which gives you ECMP, that is load-balancing via routes.

Question still remains unanswered: what is your goal? Use both paths? Prefer the other?

We do not understand each other...

I do not set any distances and priorities when I configure static connection.

But I can set distance for DHCP or PPPoE connection. I have already played with this. Effect is the same: 10-15 seconds looks good, after that PPPoE route is absent.

I have many configuration  SD-WAN configurations:

DHCP and PPPoE - works fine

Static and Static - works fine

Static and PPPoE - not working

[alex_buric]

ede_pfau wrote:

Question still remains unanswered: what is your goal? Use both paths? Prefer the other?

My goal - use both of WAN links

Balancing: Source-Destination IP

[localhost]

Maybe a performance SLA is removing the pppoe route? (Network->Performance SLA)

You have checked the event logs (system and router)? Perhaps its showing the reason why the route got removed.

I'd also debug the pppoe connection.

diag debug reset diag debug enable diag debug application pppoed -1

And verify with ping the pppoe gateway is still reachable:

execute ping-options interface <pppoe interface>

execute ping <gateway ip>