Theo wrote...
> You shouldn't be required to have any IPs on an interface for it to be
> used by wackamole. And it should work fine with two physical interfaces
> in the same subnet (though your routing table maybe confusing and/or
> wrong). If it doesn't work, there is a bug in wackamole.
Ok, I must have something fundamental confused. I'm missing something
IP-wise....Let me explain how I see it, and perhaps someone can tell me
where my thinking is FUBARed.
In a non-wackamole world, you don't put addresses on the same interface that
are in the same subnet UNLESS the additional (or 'alias') addresses use a
host subnet mask (255.x4). So I would think that if the interface you tell
wackamole to use already has a single non-VIP on it, it would have a
"normal" subnet mask of 255.255.255.0 for a class C. Then any additional
vip's that get assigned to that interface (in the same subnet) should have a
subnet mask of 255.255.255.255. Thus, I would think that the most common
settings for the netmask in wackamole.conf for a class C where the intf has
a nonVIP on it would be 255.255.255.255 yet all the docs I THINK show
255.255.255.0 for class C examples.
Case in point...
192.168.75.22 255.255.255.0 is the non-vip on int fxp0
Then, ANY addresses that wackamole puts on that interface (that are in the
same subnet) should not have a subnet mask of 255.255.255.0, it should be
255.255.255.255. Correct?
Another situation...
You have one interface (non-VIP) with 192.168.75.22 255.255.255.0 on it. You
want to use a different interface for all wackamole VIP's. How could you
possibly specify a correct netmask using the current wackamole parameters?
What I mean is, let's say you want 192.168.76.1-254 as VIP's on this 2nd
interface. Wackamole should assign the FIRST ip on this "blank" interface
with a subnet of 255.255.255.0, and any additional VIP's it throws on that
same interface should use 255.255.255.255. However, you can only specify a
single netmask in wackamole.conf. So while wackamole may go ahead and assign
the address & netmask, I would think it would be bizarre from an IP
standpoint.
So, am I really missing something here (very likely) or is wackamole only
designed to hand out IP's to an interface that already has a non-wackamole
IP address on it, and you would always specify 255.255.255.255 as your
netmask in wackamole.conf?
Thanks for any assistance to get me out of my confusion.
Jay West
---
[This E-mail scanned for viruses by Declude Virus]
> You shouldn't be required to have any IPs on an interface for it to be
> used by wackamole. And it should work fine with two physical interfaces
> in the same subnet (though your routing table maybe confusing and/or
> wrong). If it doesn't work, there is a bug in wackamole.
Ok, I must have something fundamental confused. I'm missing something
IP-wise....Let me explain how I see it, and perhaps someone can tell me
where my thinking is FUBARed.
In a non-wackamole world, you don't put addresses on the same interface that
are in the same subnet UNLESS the additional (or 'alias') addresses use a
host subnet mask (255.x4). So I would think that if the interface you tell
wackamole to use already has a single non-VIP on it, it would have a
"normal" subnet mask of 255.255.255.0 for a class C. Then any additional
vip's that get assigned to that interface (in the same subnet) should have a
subnet mask of 255.255.255.255. Thus, I would think that the most common
settings for the netmask in wackamole.conf for a class C where the intf has
a nonVIP on it would be 255.255.255.255 yet all the docs I THINK show
255.255.255.0 for class C examples.
Case in point...
192.168.75.22 255.255.255.0 is the non-vip on int fxp0
Then, ANY addresses that wackamole puts on that interface (that are in the
same subnet) should not have a subnet mask of 255.255.255.0, it should be
255.255.255.255. Correct?
Another situation...
You have one interface (non-VIP) with 192.168.75.22 255.255.255.0 on it. You
want to use a different interface for all wackamole VIP's. How could you
possibly specify a correct netmask using the current wackamole parameters?
What I mean is, let's say you want 192.168.76.1-254 as VIP's on this 2nd
interface. Wackamole should assign the FIRST ip on this "blank" interface
with a subnet of 255.255.255.0, and any additional VIP's it throws on that
same interface should use 255.255.255.255. However, you can only specify a
single netmask in wackamole.conf. So while wackamole may go ahead and assign
the address & netmask, I would think it would be bizarre from an IP
standpoint.
So, am I really missing something here (very likely) or is wackamole only
designed to hand out IP's to an interface that already has a non-wackamole
IP address on it, and you would always specify 255.255.255.255 as your
netmask in wackamole.conf?
Thanks for any assistance to get me out of my confusion.
Jay West
---
[This E-mail scanned for viruses by Declude Virus]