we have a FusionHub with one or more public ip address (one for each customer), and more B One as client on the customer site.
At each customer site we have one main connection (fiber) on WAN 1 and one secondary connection (satellite) on WAN2.
What we want to achieve is to have the public IP address (/32) configured on the FusionHub (maybe using VRF?) routed to the wan on the B One using a PtP (/30 or 29) between the fusionHub and the B One primary wan.
Then have the same IP routed via a SpeedFusion VPN thourgh the secondary WAN if the primary WAN fail.
So the goal is: if the primary WAN on the customer B One is working, the public ip address is routed/forward via the primary WAN.
IF the primary WAN fail, the customer will get the address routed through the secondary WAN via the VPN.
(the traffic flow alaways through the fusionhub)
You don’t want the customer’s public IP from the FusionHub routed to any WAN interface, you want it directed to the IP address of the server behind the B One that is going to provide service.
Let us say the Lan address of the server in question is 192.168.1.100.
You establish Speed Fusion between the B one and the Fusion Hub… setting both Wan1 and Wan2 in the SF Vpn configuration to the FH
Then you select port forwarding on the FH from the FH Customer IP. → 192.168.1.100 for the desired ports.
Today you are port forwarding on the B One… For this service you move the port forwarding from the B One to the FH… and then the SDWAN SpeedFusion VPN handles the routing for you. There is only a single NAT translation at the FH. The SF VPN gives you all of the bonding or failover that you configure.
If you don’t want NAT you can direct the /32 directly to the server in question but it won’t be the wan interface, the server in question will need to have a static route from the BOne for its /32. I usually use loopback interfaces if I really need a complete /32 at a host, but normally port forwarding for the NAT is enough.
technically speaking, i want the customer public IP on a loopback interface of the customer router.
So i want to route this public IP from/through the primary WAN and from/through the VPN.
I know how to do that in Mikrotik/Cisco, but want to know how to do that in peplink
Peplink products don’t really do internal loopbacks like cisco/juniper etc.
You can have a route from the peplink devices to the customer router. and use OSFP or BGP to share the routes, but you can’t stand up a loopback on the peplink.
What is the customer going to do with that loopback on their router?
