ip.networking.forwarding (or something like that - i'm currently not on that server)

NAT
from vr0 on 192.168.0.0/16 to (vr0) - something similar

All computers, and cable modem are connected to switch.

The problem is, that it seems to me that network is crashing on this setup. I've came to that conclusion because, sometimes I can ping outside, but most of the times I can't (for example, from ten attempts only one succeeds, and when it succeeds it only works for short period of time - couple of seconds).
From OpenBSD server everything works fine.
Inside local network everything also works fine.
But when I try to surf using computer from within the network, I need to refresh page couple of times for it to load (and most of the time, it doesn't load fully).

I wanted to say no at first, but I'm not so sure J65nko.. but I can't confirm this either.

In the PF FAQ the following is mentioned for the ext_addr member of the nat keyword.

Quote:

Originally Posted by http://www.openbsd.org/faq/pf/nat.html#config

1) The name of the external network interface in parentheses ( ). This tells PF to update the rule if the IP address(es) on the named interface changes. This is highly useful when the external interface gets its IP address via DHCP or dial-up as the ruleset doesn't have to be reloaded each time the address changes.

2) The name of a network interface followed by either one of these modifiers:

In addition, the :0 modifier can be appended to either an interface name or to any of the above modifiers to indicate that PF should not include aliased IP addresses in the substitution. These modifiers can also be used when the interface is contained in parentheses. Example: fxp0:network:0.

Still, I'm not sure how this would work though.. perhaps like:nat on vr0 inet from 192.168.0.0/16 to any -> (vr0:network:0).

I actually do this now. I have an OBSD 4.3 box NAT'ing my desktop to my ADSL router using a single NIC. The OBSD box and the desktop talk to each other via the 4 port switch built into the ADSL router (which is also how the OBSD box talks to the ADSL router.) In my production environment at work I would never recommend this. However, this is my home, and the double traffic isn't detrimental at such low levels... just cuts down the effective bandwidth that can be utilized in half.