Re: Wrong route reserved

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============6486645731729983450==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig8D3BC65251DA615AF30CC86E"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig8D3BC65251DA615AF30CC86E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Theo Schlossnagle schrieb:
>
>
> You have 192.168..x.y in your verbiage, but 10.0.78.y in your config.=20
> The inconsistency is a bit confusing -- if you want to change the IPs,
> make sure to change them consistently everywhere.
Sorry about that. I noticed by the time I hit the enter key to send it,
as you always do with such things.
Meant is that additionally to the correct direct route 10.0.78.224/27
the faulty route 10.0.78.0/24 is added to the routing tables.
>
> 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.
hmmm.... Well, if there is a way to configure a "default" IP address in
wackamole I must have missed it. However the base addresses that Spread
use do lie in that network. 10.0.78.232, 10.0.78.226 and 10.0.78.248.
That's the IP addresses their own hostnames resolve to - by DNS or by
the /etc/hosts file. All are checked and without flaw. Spread is started
with "-n <hostname>" in all cases and that <hostname> is indeed the
hostname the host is known by itsself and all other related systems.

>
> 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).
Well, that sounds like what happens here. However, the computers' "own"
IP addresses do lay in the network 10.0.78.224/27. Could it have
something to do with the way spread and wackamole work together? The
spread configuration is hardly touched, it just starts with a
"Spread_Segment 10.0.78.255:4803" clause including he host names and
their IP addresses. Maybe Spread misinterprets the 10.0.78.255 so that
it is indeed in a class C network, even though it only meant to be the
network's broadcast address. And in result wackamole causes all IP
addresses to drop.


--------------enig8D3BC65251DA615AF30CC86E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHPKw0Y7BnBH/xFu8RAjReAKC1AmvwkVE+JyQNFi38C5SQ97FtuwCeKrla
h7QInNx9w/Xj5n1FXJicS3I=
=bgAD
-----END PGP SIGNATURE-----

--------------enig8D3BC65251DA615AF30CC86E--


--===============6486645731729983450==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
wackamole-users mailing list
[email protected]
http://lists.backhand.org/mailman/listinfo/wackamole-users

--===============6486645731729983450==--