OpenVZ Forum


Home » General » Support » iproute issue
iproute issue [message #53050] Sat, 02 December 2017 11:54
mangelot is currently offline  mangelot
Messages: 12
Registered: January 2012
Junior Member
From: *adsl-surfen.hetnet.nl
Hello,

I'm Having a problem with an multiple gateway setup, And I'm a NOOB with it. .

HN
eth0 ip4: xxx.xxx.25.10
eth1 ipv6: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:25:10

CT number 100
venet ip xxx.xxx.25.11 and ipv6: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:25:11
this setup works perfect.


But I wanted to add the xxx.xxx.31.xx ip also to the same HN.
so I added ipv4: xxx.xxx.31.10 to eth1 on the HN together with the ipv6.
I can connect to both ipv4 on the HN and ipv6 is still working.
so the HN seems configured right.


However when i get inside the CT 100 (which doesn't have a xxx.xxx.31.xxx ip)

I can ping the HN (xx.xx.25.xx and xx.xx.31.xx )
I can ping other CT on the same HN (with ipv4 xx.xx.25.xx and ipv6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:25:xx)
I can also ping outside to example www.google.com (with ipv4 and ipv6)

But now our problem:
On our network there is another server that also uses ip xxx.xxx.31.xx but we cannot ping that server with ipv4 (ipv6 works) from inside the CT 100





rule-eth0
from 178.251.25.0/24 table gateway25

rule-eth1
from 178.251.31.0/24 table gateway31

route-eth0
throw 178.251.31.0/24 table gateway31
throw 178.251.25.0/24 table gateway25
default via 178.251.25.1 dev eth0 table gateway25

route-eth1
throw 178.251.25.0/24 table gateway25
throw 178.251.31.0/24 table gateway31
default via 178.251.31.1 dev eth1 table gateway31




www.mangelot-hosting.nl

[Updated on: Sat, 02 December 2017 12:21]

Report message to a moderator

Previous Topic: Problem withe Debian 9 Template, not Working
Next Topic: Is OPREN VZ at the End and is not developed?
Goto Forum:
  


Current Time: Thu Dec 14 22:45:04 GMT 2017