All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Need some help on setting up GRE tunnel with PVE 7
I have followed: https://lowendtalk.com/discussion/156850/howto-tunnel-ddos-protected-ovh-ip-to-vms-in-other-datacenter/ to setup a GRE tunnel, but i faced some issues:
My server 1 is OVH server with a additional /30 block,(142.16), with a orig IP 54.39
My server 2 is DediSpec with a /29 , I want to attach the/30 from my OVH server.(173.208)
Here are my steps:
`ip tunnel add gre1 mode gre remote 173.208.xxx.26 local 54.39.xxx.49 ttl 255
ip link set gre1 up
Run this on server 2:
ip tunnel add gre1 mode gre remote 54.39.xxx.49 local 173.208.xxx.26 ttl 255
ip link set gre1 up
Then we need to create a route on server 1 that will route the IP traffic over the GRE tunnel
Run this on server 1:
ip route add 142.44.xxx.16/30 dev gre1
The next step is to route data from the GRE tunnel to the bridge and back.
Run this on server 2:
ip rule add from 142.44.xxx.16/30 table 666
ip route add default dev gre1 table 666
ip route add 142.44.xxx.16/30 dev br0 table 666
Last thing to do is to add the a IP the to bridge. This is gonna be the gateway for you VM's!
Use the second IP of the range!
Run this on server 2:
ip addr add 142.44.xxx.16/30 dev br0 *
- I encountered a br0 not found error, so I used brctrl to create one . `
The situation now is, when I ping the 142.44 from the dedispec, it keeps saying check the firewall, and the IP isn't working correctly too, where did I make mistake?
What I can think of, maybe the be br 0, should replace by vmbr0?
Thanks for the help.
Comments
Did you disable vMAC with OVH? This method will only work if the IPs are routed, not when they are on-link.
Also: did you enable ip_forward and disable rp_filter in sysctl?
How can I disable it? I'm using SoYouStart.
Do I need to config the additional IP to the SoYouStart server first?
I've enabled ipv4 forward, rp filter, not yet.
Thanks