Re: Expected 3.3 > 3.4 conversion

["Chris Zakelj" <c.zakelj@ieee.org>]

>From everybody's messages, I'm getting the gist that 3.4 is pretty much
settled down at this point :)  If (as Chuck says) the CVS freeze is
happening in just a couple weeks and only bugfixes will go into it at that
point, it seems that I won't have any trouble using a -current snapshot on
the production machine.  Of course, knowing how slow telcos move when
installing DSL, it's entirely possible that 3.4 will be out a while before
the line's active and the hardware installed anyway.

How about part 2 of my question...  Have there been any syntactical/command
changes to pf.conf that might throw me for a loop since this past June (when
everyone here helped me figure out what I was doing wrong on my first
setup)?  Without the changes, I'm expecting to be able to use lines such as

rdr on el0 proto tcp from any to any port 10310 -> 192.168.0.31 80
rdr on el0 proto tcp from any to any port 10320 -> 192.168.0.32 80

to use a nonstandard port to identify which internal webserver i'd like to
fetch pages from.  Using these non-standard ports seems to be the most
straightforward method of doing this (of course if someone has a better
method, I'm all ears!).