Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
25% Recurring Discount on NVMe VPS
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
CloudLinux
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Help gre tunnel ip pinged, and doest work

hi not working gre tunnel. please help, thankyou.

server 1 ifconfig:
208.115.109.66/29
or
208.115.109.66/32

gre tunnel setup:

Public IPv4 server 1: 208.115.109.66
Public IPv4 server 2: 135.181.213.247
IP block I want to use on server 2: 208.115.109.66 server ip
server 2 new gateway route gre tunnel:
208.115.109.67
vps ip:
208.115.109.68
208.115.109.69
208.115.109.70
Run this on server all::
sudo echo 'net.ipv4.ip_forward=1' >> /etc/sysctl.conf
sudo sysctl -p

Run this on server 1:

ip tunnel add gre1 mode gre remote 135.181.213.247 local 208.115.109.66 ttl 255
ip link set gre1 up

Run this on server 2:

ip tunnel add gre1 mode gre remote 208.115.109.66 local 135.181.213.247 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 208.115.109.67 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 208.115.109.67 table 666
ip route add default dev gre1 table 666
ip route add 208.115.109.67 dev eno1 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 208.115.109.67 dev eno1

You should be able to ping 208.115.109.67 now..

Use the following network config in the adapter of your VM:

IP address: 208.115.109.68
Mask: 255.255.255.248 (depends on the subnet)
Gateway: 208.115.109.67

Comments

  • is this a question or a solution

    Thanked by 1Erisa
  • nszervernszerver Member
    edited October 2023

    I have a question because it doesn't work, what could be wrong with server 1 at the moment:
    ip address load network: 208.115.109.66/29

  • network:
    version: 2
    renderer: networkd
    ethernets:
    id0:
    match:
    macaddress: 00:30:48:d3:86:64
    addresses:
    - 208.115.109.66/29
    gateway4: 208.115.109.65
    nameservers:
    addresses:
    - 127.0.0.1

Sign In or Register to comment.