Thank you very much for your answer!
There was indeed a missing route. I added the following routes:
Client: sudo route add -net 192.168.163.128 netmask 255.255.255.128 gw
192.168.163.20 dev eth2
Instanz:sudo route add -net 192.168.163.0 netmask 255.255.255.128 gw
10.0.0.1 dev eth0
And after
Hello guys, I am dealing with a strange phenomenon my StackOps environment.
The thing is like this:
I am running a single-node stackops deployment in a little /25 network. The
installation and the few configurations I had to do afterwards went just
fine, no problems so far. I was also able to
On Thu, Mar 22, 2012 at 10:47 AM, Nicolas Odermatt oderma...@gmail.comwrote:
Hello guys, I am dealing with a strange phenomenon my StackOps environment.
The thing is like this:
I am running a single-node stackops deployment in a little /25 network.
The installation and the few configurations
Hi Nicolas, thanks for using our distro!
Just to summarize:
- Single node
- Management network: 192.168.163.0/25 = 192.168.163.1 to 192.168.163.126.
Let's assume gateway = 192.168.163.1
- Service Network: 192.168.163.128/25 = 192.168.163.129 to 192.168.163.254.
gateway should be = 192.168.163.129
4 matches
Mail list logo