Changes

Jump to: navigation, search

Configuration file

477 bytes added, 21:59, 18 October 2011
no edit summary
*: Creates a scope for settings options on an interface, or at leasts makes sure that it exists. For example <tt>interface em0 { interface pfsync0 {</tt> will create an interface of type <tt>pfsync</tt> (which happens to handle firewall state synchronization) on the physical interface <tt>em0</tt>. This is probably a bad example, as such an interface is automatically created by the <tt>cluster-syncport</tt> keyword.
** <tt>group</tt> ''quoted string''
**: Assign the interface to a group, which is also a very good way to give interfaces names. For example<tt>interface em0 { group "wan"</tt> will bla bla</p>
! Keywords !! !! Description || Example
|-
| <tt>interface</tt> ''ifname'' <tt>{</tt> || Creates a scope for settings options on an interface, or at leasts makes sure that it exists. For example <tt>interface em0 { interface pfsync0 {</tt> will create an interface of type <tt>pfsync</tt> (which happens to handle firewall state synchronization) on the physical interface <tt>em0</tt>. This is probably a bad example, as such an interface is automatically created by the <tt>cluster-syncport</tt> keyword. || <tt>interface em0 { interface pfsync0 {</tt>
|-
| || <tt>interface</tt> ''ifname'' <tt> { || group</tt> ''quoted string'' || Assign the interface to a group, which is also a very good way to give interfaces names. ||<tt>interface em0 { group "wan"</tt>
|}

Navigation menu