Carlito,
Some more detail would be helpful.
Are you using VPP purely as a host, or are VPP acting as a router with other
nodes behind it?
For the VPP as a host case, I'd prefer to use a scoped/zoned address approach.
E.g.
ping 8.8.8.8@wan0
Source address selection should then pick a source addre
eer supports it and FIB
can use this for link state monitoring.
/neale
-Message d'origine-
De : au nom de carlito nueno
Date : vendredi 16 août 2019 à 00:20
À : "bbal...@juniper.net"
Cc : "vpp-dev@lists.fd.io"
Objet : Re: [vpp-dev] Help with two interfaces
Hi Balaji,
As far as I know, VPP doesn't have link monitoring to switch routes.
But as you said, I added a cron job to check link status and switch
routes on failure.
I added each interface route to a particular FIB table. This way I am
able to use ping 8.8.8.8 source wan0 or wan1.
Is this the co
Not sure there is a way to do this without a routing protocol.
Don't think there is link monitoring or path monitoring to switch the default
route to backup route.
Maybe you can have a cron job that check the link status and next hop
connectivity and switch the route when there is a failure.
G
Sorry for not being clear.
Each of the interfaces is connected to a different network (ISP). The
scenario is of dual WAN.
One ISP is providing static address and other is providing DHCP.
wan1 is receiving DHCP.
If I ONLY have:
ip route add 0.0.0.0/0 via 172.78.10.158 wan0
then I am able to ping
I am assuming wan1 is also connected to same network as wan0, is that correct?
Curious, what is your use case for wanting to have two interface connected to
same network?
Also, check to see if you got an address from DHCP and try to ping the next hop
first.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You re
Your VPP configs look fine. I can only guess at general network issues.
My first guess would be that the DHCP process did not complete, yet.
For my second guess, this:
vpp# ping 8.8.8.8 source wan1
means take the source address from wan1, but this:
ip route add 0.0.0.0/0 via 172.78.10.1
