abgrund at silberdrache
Nov 15, 2007, 5:56 AM
Views: 1893
Permalink
|
Hello,
I am having a problem with a route being reserved at the startup of a
two servers that should *not* be reserved. It's a debian Linux system
and didn't make any trouble before wackamole was installed. Now, every
time it starts up it adds a route for 192.168.0.0/24 to be routed
directly to the remote hosts, which is not possible. Correct would be to
only route 192.168.0.160/27 directly. This behavior causes the servers
to not be accessible in the office I work at, even though it does work
from pretty much everywhere else.
Could anyone tell my why wackamole does this and how I may keep it from
doing so? This wrong routing table entry is really causing a lot trouble
here in the office.
Björn Keil
Here is my wackamole config file (note that the first two bytes of the
IP addresses have been changed):
Spread = 4803
SpreadRetryInterval = 5s
Group = wack1
Control = /var/run/wackamole/wackamole.it
Prefer { eth0:10.0.78.230/27 eth0:10.0.78.240/27 eth0:10.0.78.243/27
eth0:10.0.78.245/27 }
VirtualInterfaces {
{ eth0:10.0.78.230/27 eth0:10.0.78.240/27 eth0:10.0.78.243/27
eth0:10.0.78.245/27 }
{ eth0:10.0.78.227/27 eth0:10.0.78.241/27 eth0:10.0.78.244/27
eth0:10.0.78.246/27 }
}
Arp-Cache = 90s
Notify {
eth0:10.0.78.225/32
arp-cache
}
balance {
AcquisitionsPerRound = all
interval = 4s
}
mature = 5s
|
signature.asc
Wrong route reserved
