jesus at omniti
Nov 15, 2007, 6:06 AM
Post #2 of 3
(3543 views)
Permalink
|
On Nov 15, 2007, at 8:56 AM, Björn Keil wrote:
> 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
You have 192.168..x.y in your verbiage, but 10.0.78.y in your config.
The inconsistency is a bit confusing -- if you want to change the IPs,
make sure to change them consistently everywhere.
If you have, then:
Note that you must have a non-wackamole managed IP address on on each
subnet you intend to have wackamole managed IPs on. This "management"
IP will maintain the network interface in the kernel including the
routing table.
Also, in the VirtualInterfaces section, try putting /32 as your
netmask. Many systems require that the first IP on an interface be
correctly netmasked, but all additional logical interfaces must be
brought up with a 255.255.255.255 (or /32) netmask. This is true on
FreeBSD and some Linuxes as well.
Wackamole has no routing code in it whatsoever, so the only reason the
routing on the box would change is if you don't have a management IP
on the wackamole-managed subnets. This would cause wackamole to drop
all IPs at startup and them bring them back up -- loosing the route
information (which is why a management IP is required).
Hope this helps -- it's a guess.
--
Theo Schlossnagle
Esoteric Curio -- http://lethargy.org/
OmniTI Computer Consulting, Inc. -- http://omniti.com/
_______________________________________________
wackamole-users mailing list
wackamole-users [at] lists
http://lists.backhand.org/mailman/listinfo/wackamole-users
|
signature.asc
