Thats rather strange.
Mine shows:
# Load balancing anchor - slbd updates
rdr-anchor "slb"
rdr on $lan proto tcp from any to { ! 10.0.0.0/24 10.0.69.0/24
192.168.1.0/24 } port 21 -> 127.0.0.1 port 8021
rdr on $opt1 proto tcp from any to { ! 10.0.0.0/24 10.0.69.0/24
192.168.1.0/24 } port 21 -> 127.0.0.1 port 8022
Notice how its using the optional interface name instead of the
interfaces description. Try running cvs_sync.sh releng_1 and get on
the absolute latest and greatest version if you are on the full
installation platform.
On 3/14/06, Derrick MacPherson <[EMAIL PROTECTED]> wrote:
> RELENG_1_SNAPSHOT_03-12-2006
>
> I have 2 boxes that are synced, and I am getting an error that the macro
> dmz is not defined - the section of rules.debug is:
>
> # Load balancing anchor - slbd updates
> rdr-anchor "slb"
> rdr on $lan proto tcp from any to any port 21 -> 127.0.0.1 port 8021
> rdr on $dmz proto tcp from any to any port 21 -> 127.0.0.1 port 8022
> rdr on $sync proto tcp from any to any port 21 -> 127.0.0.1 port 8023
>
>
> and loading via pfctl -f /tmp/rules.debug shows the dmz and sync macros
> not defined. I thought this might have been some issue with the names on
> the DMZ interface being changed from OPT1 to DMZ, and it used the syntax
> dmz instead, but it doesn't appear so.
>
>
> Any ideas of whats happening? Let me know what other info you need
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
