Jeff Quast [EMAIL PROTECTED] resonded to my request about interface card names with
> > > It would be nice if there is only one interface type on the computer to > > > > define a macro automatically for them, I suggest $id0 $id1 etc. That way > > > > pf config files could be more portable, particularly in the case of a > > > > server machine that only has one interface. > > > > > > not 100% sure what you mean here, but if you mean being able to refer to > > > hme0, hme1, hme2, hme3, and hme4 simply as hme--then it's already > > there. > > > > > > > No I meant interface. So have I have, depending up the machine, > > fxp0 and ste0 as far as the filter goes there is no difference > > between them. I ran into this when I put a local pf up on two > > nameservers. > > The machines had different interface cards, so two pf.conf that should > > have > > been identical are not! > > You said yourself, they don't have identical interface cards!! > Thats the silliest thing I've ever read! With several NIC's, I > wouldn't know which NIC is my DMZ, external, or internal interface! > What a disaster! For instance, in Linux, where your ethernet > interfaces are named eth0, eth1, and so on, it becomes extremely > hazerdous to change network cards, because the eth2 you just replaced > suddenly becomes eth0 and so on. I can't tell you how many times I've > had to sit and individually plug in each NIC one by one and pinging > things to figure out which NIC is which, even though they are all > different brands. Sorry for the wording. I was taking about using pf in separate machines (in my case they happened to be my name servers). Each machine has one interface card. Both machines are running local firewalls. The only difference between the pf.conf on each machine, is the requirement to name the interface card. Linux may name each interface card same prefix but OpenBSD doesn't.
