On 5/18/09 9:46 AM, Stuart Henderson wrote:
As a test, can you try it without using the 192.168.20.1-192.168.20.10
address range format, and see if that behaves any better? You can use
this instead: {192.168.20.0/29 192.168.20.8/31 192.168.20.10}
I already tried with 192.168.21.1, 192.168.21.2
As a test, can you try it without using the 192.168.20.1-192.168.20.10
address range format, and see if that behaves any better? You can use
this instead: {192.168.20.0/29 192.168.20.8/31 192.168.20.10}
In gmane.os.openbsd.misc, you wrote:
> Scenario:
>
> int_if with two ip addresses in two diff
Scenario:
int_if with two ip addresses in two differents lans (192.168.20.254,
192.168.21.254).
more aliases in the external interfaces
nat rules: every 10 internals ip use an external address for the nat.
everything works fine, except for the second internal ip address. ip
from 192.168.21.0/2
Scenario:
int_if with two ip addresses in two differents lans (192.168.20.254,
192.168.21.254).
more aliases in the external interfaces
nat rules: every 10 internals ip use an external address for the nat.
everything works fine, except for the second internal ip address. ip
from 192.168.21.0/24
4 matches
Mail list logo