VPN is up but no routing to the branch office

  • 1
  • Question
  • Updated 5 years ago
  • Answered
Hello,

i'm working on this problem for a few weeks and don't know what else i could try. I hope you guys could help me. I really appreciate that...

we installed a HiveOS-VA with eth0 192.168.1.45/24. The purpose is to setup a branch office connected through a vpn. In the Branch office there is a BR200-WP. I already managed to build the vpn (phase 1 and 2 are ok). In the HiveManager the 2 triangles are green.

In the monitor overview i can see that the interface ip of the HiveOS-VA is 172.18.185.129 and af the BR200-WP in the branch office is 172.18.186.1.

i'm not able to ping the ip of the branch office from inside our LAN. The gateway is managed by a provider so that makes it more difficult but the provider already add a route that al the traffic destined to the branch office subnet 172.18.0.0/16, should be forwarded to the HiveOS-VA ip 192.168.1.45.

Please ask me for more logs are details if this is not clear enough?
I hope we could get this worked.

Thanks in advance...

Seppe
Photo of Giuseppe

Giuseppe

  • 16 Posts
  • 1 Reply Like

Posted 5 years ago

  • 1
Photo of Bill Lundgren

Bill Lundgren, Employee

  • 21 Posts
  • 12 Reply Likes
On the VA configuration, did you add an "internal" route for 192.168.1.0/24? YOu will need a route on the BR to get back to corporate, and as you mentioned, the route on your core, pointing to the VA, to get traffic to the remote branches.

You'll need an internal route for every subnet you need the branches to be able to reach.
Photo of Giuseppe

Giuseppe

  • 16 Posts
  • 1 Reply Like
Hello Bill,

we complete rebuild the config just to test the vpn. Here you can see the vpn is up.



here is the routing table of the BR200



routing table of the VA-HiveOS



I can't ping the BR200 interface ip 172.20.212.1 from the VA-HiveOS.
The same for the other direction.
There is no entry in the routing table for the other networks?

Thanks,
Seppe