Hi tech@,
Below you can find what I think is a typo and an error. As far as I
understand it the IP shown could only be reached if you match the
subnet segment.
Kind regards.
--
Pablo Méndez Hernández
--- faq/pf/example1.html.orig 2016-01-10 20:44:21.926795536 +0100
+++ faq/pf/example1.html 2016-01-10 20:47:33.346114559 +0100
@@ -143,9 +143,9 @@
Take this example and adjust to fit your needs:
<p>
<blockquote><pre>
-option domain-name-servers 192.168.1.1;
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.1;
+ option domain-name-servers 192.168.1.1;
range 192.168.1.4 192.168.1.254;
host myserver {
fixed-address 192.168.1.2;
@@ -163,8 +163,9 @@
RFC 1918</a> address space here if you prefer, or even a public IP block
if you have one. Using this example, clients will query a local DNS server,
detailed in a later section. If you don't plan on using a local DNS server,
-replace <tt>192.168.1.1</tt> in the <tt>option routers</tt> line with the
-address of your preferred upstream DNS server (<tt>8.8.8.8</tt>, for example).
+replace <tt>192.168.1.1</tt> in the <tt>option domain-name-servers</tt> line
+with the address of your preferred upstream DNS server (<tt>8.8.8.8</tt>,
+for example).
<p>
<hr>
<h2 id="pf">Firewall</h2>
