Date: Wed, 14 May 2014 19:58:51 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44832 - head/en_US.ISO8859-1/books/faq Message-ID: <201405141958.s4EJwp64024027@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Wed May 14 19:58:50 2014 New Revision: 44832 URL: http://svnweb.freebsd.org/changeset/doc/44832 Log: More rewording around "you". Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Wed May 14 15:52:23 2014 (r44831) +++ head/en_US.ISO8859-1/books/faq/book.xml Wed May 14 19:58:50 2014 (r44832) @@ -4628,7 +4628,7 @@ options SYSVMSG # enable for </question> <answer> - <para>Yes, if you configure X for a 5 button mouse. To + <para>Yes, if X is configured for a 5 button mouse. To do this, add the lines <literal>Buttons 5</literal> and <literal>ZAxisMapping 4 5</literal> to the <quote>InputDevice</quote> section of @@ -5146,8 +5146,8 @@ Key F15 A A Menu Wo xlink:href="&url.books.handbook;/userppp.html">Handbook entry on user PPP</link>.</para> - <para>If you are using kernel-mode PPP or have an Ethernet - connection to the Internet, you need to use &man.natd.8;. + <para>If the + connection to the Internet is over Ethernet, use &man.natd.8;. A tutorial can be found in the <link xlink:href="&url.books.handbook;/network-natd.html">natd</link> section of the Handbook.</para> @@ -5176,10 +5176,10 @@ Key F15 A A Menu Wo </question> <answer> - <para>Yes. If you want to use NAT over a user PPP + <para>Yes. For instructions on how to use NAT over a PPP connection, see the <link xlink:href="&url.books.handbook;/userppp.html">Handbook - entry on user PPP</link>. If you want to use NAT over + entry on PPP</link>. To use NAT over some other sort of network connection, look at the <link xlink:href="&url.books.handbook;/network-natd.html">natd</link> @@ -5205,7 +5205,7 @@ Key F15 A A Menu Wo <screen>&prompt.root; <userinput>ifconfig ed0 alias 172.16.141.5 netmask 0xffffff00</userinput></screen> - <para>You can read more about this in the &os; <link + <para>More information can be found in the &os; <link xlink:href="&url.books.handbook;/configtuning-virtual-hosts.html">Handbook</link>.</para> </answer> </qandaentry> @@ -5249,23 +5249,11 @@ Key F15 A A Menu Wo </question> <answer> - <para>&os; supports multicast host operations by default. - If you want your box to run as a multicast router, you - need to recompile your kernel with the - <literal>MROUTING</literal> option and run - &man.mrouted.8;. &os; will start &man.mrouted.8; at boot - time if the flag <literal>mrouted_enable</literal> is set - to <literal>YES</literal> in - <filename>/etc/rc.conf</filename>.</para> - - <note> - <para>In recent &os; releases, the &man.mrouted.8; - multicast routing daemon, the &man.map-mbone.8; and - &man.mrinfo.8; utilities have been removed from the base - system. These programs are now available in the &os; - Ports Collection as - <package>net/mrouted</package>.</para> - </note> + <para>Install the <package>net/mrouted</package> package + or port and add + <literal>mrouted_enable="YES"</literal> to + <filename>/etc/rc.conf</filename> start this service at + boot time.</para> </answer> </qandaentry> @@ -5289,25 +5277,25 @@ Key F15 A A Menu Wo </question> <answer> - <para>If you have compiled your kernel with the - <literal>IPFIREWALL</literal> option, you need to be aware + <para>If the kernel is compiled with the + <literal>IPFIREWALL</literal> option, be aware that the default policy is to deny all packets that are not explicitly allowed.</para> - <para>If you had unintentionally misconfigured your system - for firewalling, you can restore network operability by - typing the following while logged in as <systemitem + <para>If the firewall is unintentionally misconfigured, + restore network operability by + typing the following as <systemitem class="username">root</systemitem>:</para> <screen>&prompt.root; <userinput>ipfw add 65534 allow all from any to any</userinput></screen> - <para>You can also set + <para>Consider setting <literal>firewall_type="open"</literal> in <filename>/etc/rc.conf</filename>.</para> - <para>For further information on configuring a &os; + <para>For further information on configuring this firewall, see the <link - xlink:href="&url.books.handbook;/firewalls.html">Handbook + xlink:href="&url.books.handbook;/firewalls-ipfw.html">Handbook chapter</link>.</para> </answer> </qandaentry> @@ -5320,11 +5308,11 @@ Key F15 A A Menu Wo </question> <answer> - <para>Possibly because you want to do network address - translation (NAT) and not just forward packets. A - <quote>fwd</quote> rule does exactly what it says; it - forwards packets. It does not actually change the data - inside the packet. Say we have a rule like:</para> + <para>Possibly because network address + translation (NAT) is needed instead of just forwarding packets. A + <quote>fwd</quote> rule only + forwards packets, it does not actually change the data + inside the packet. Consider this rule:</para> <screen>01000 fwd <replaceable>10.0.0.1</replaceable> from any to <replaceable>foo 21</replaceable></screen> @@ -5332,9 +5320,9 @@ Key F15 A A Menu Wo <replaceable>foo</replaceable> arrives at the machine with this rule, the packet is forwarded to <replaceable>10.0.0.1</replaceable>, but it still has the - destination address of <replaceable>foo</replaceable>! + destination address of <replaceable>foo</replaceable>. The destination address of the packet is - <emphasis>not</emphasis> changed to + not changed to <replaceable>10.0.0.1</replaceable>. Most machines would probably drop a packet that they receive with a destination address that is not their own. Therefore, @@ -5357,10 +5345,11 @@ Key F15 A A Menu Wo </question> <answer> - <para>You can redirect FTP (and other service) request with - the <package>sysutils/socket</package> port. - Replace the service's command line to call - <command>socket</command> instead, like so:</para> + <para>FTP and other service requests can be redirected with + the <package>sysutils/socket</package> package or port. + Replace the entry for the service in <filename>/etc/inetd.conf</filename> to call + <command>socket</command>, as seen in this example for + <application>ftpd</application>:</para> <programlisting>ftp stream tcp nowait nobody /usr/local/bin/socket socket <replaceable>ftp.example.com</replaceable> <replaceable>ftp</replaceable></programlisting> @@ -5394,9 +5383,9 @@ Key F15 A A Menu Wo </question> <answer> - <para>You are running a program that requires the Berkeley - Packet Filter (&man.bpf.4;), but it is not in your kernel. - Add this to your kernel config file and build a new + <para>The running application requires the Berkeley + Packet Filter (&man.bpf.4;), but it was removed from a custom kernel. + Add this to the kernel config file and build a new kernel:</para> <programlisting>device bpf # Berkeley Packet Filter</programlisting> @@ -5426,9 +5415,9 @@ Key F15 A A Menu Wo </question> <answer> - <para>This is the kernel telling you that some activity is - provoking it to send more ICMP or TCP reset (RST) - responses than it thinks it should. ICMP responses are + <para>This kernel message indicates that some activity is + provoking it to send a large amount of ICMP or TCP reset (RST) + responses. ICMP responses are often generated as a result of attempted connections to unused UDP ports. TCP resets are generated as a result of attempted connections to unopened TCP ports. Among @@ -5449,27 +5438,26 @@ Key F15 A A Menu Wo </listitem> </itemizedlist> - <para>The first number in the message tells you how many + <para>The first number in the message indicates how many packets the kernel would have sent if the limit was not in - place, and the second number tells you the limit. You can - control the limit using the - <varname>net.inet.icmp.icmplim</varname> sysctl variable - like this, where <literal>300</literal> is the limit in + place, and the second indicates the limit. This limit + is controlled using + <varname>net.inet.icmp.icmplim</varname>. This example + sets the limit to <literal>300</literal> packets per second:</para> <screen>&prompt.root; <userinput>sysctl net.inet.icmp.icmplim=300</userinput></screen> - <para>If you do not want to see messages about this in your - log files, but you still want the kernel to do response - limiting, you can use the - <varname>net.inet.icmp.icmplim_output</varname> sysctl - variable to disable the output like this:</para> + <para>To disable these messages + without disabling response + limiting, use + <varname>net.inet.icmp.icmplim_output</varname> + to disable the output:</para> <screen>&prompt.root; <userinput>sysctl net.inet.icmp.icmplim_output=0</userinput></screen> - <para>Finally, if you want to disable response limiting, you - can set the <varname>net.inet.icmp.icmplim</varname> - sysctl variable (see above for an example) to + <para>Finally, to disable response limiting completely, + set <varname>net.inet.icmp.icmplim</varname> to <literal>0</literal>. Disabling response limiting is discouraged for the reasons listed above.</para> </answer> @@ -5482,13 +5470,13 @@ Key F15 A A Menu Wo </question> <answer> - <para>This means that some device on your local Ethernet is + <para>This means that some device on the local Ethernet is using a MAC address in a format that &os; does not recognize. This is probably caused by someone experimenting with an Ethernet card somewhere else on the - network. You will see this most commonly on cable modem + network. This is most commonly seen on cable modem networks. It is harmless, and should not affect the - performance of your &os; machine.</para> + performance of the &os; system.</para> </answer> </qandaentry> @@ -5529,14 +5517,14 @@ Key F15 A A Menu Wo into the process from being able to break into the wider system.</para> - <para>The process is said to be able to - <quote>play</quote> inside the walls. That is, - nothing the process does in regards to executing code - is supposed to be able to breech the walls so you do - not have to do a detailed audit of its code to be able + <para>The process is be able to + run inside the walls. + Since nothing the process does in regards to executing code + is supposed to be able to breech the walls, + a detailed audit of its code is not needed in order to be able to say certain things about its security.</para> - <para>The walls might be a user ID, for example. + <para>The walls might be a user ID, for example. This is the definition used in the &man.security.7; and &man.named.8; man pages.</para> @@ -5645,14 +5633,11 @@ Key F15 A A Menu Wo enabled.</para> <para>The securelevel of a running system can not be - lowered as this would defeat its purpose. If you need - to do a task that requires that the securelevel be - non-positive (e.g., an - <buildtarget>installworld</buildtarget> or changing the - date), you will have to change the securelevel setting in - <filename>/etc/rc.conf</filename> (you want to look for - the <varname>kern_securelevel</varname> and - <varname>kern_securelevel_enable</varname> variables) and + lowered as this would defeat its purpose. If a task + requires that the securelevel be + non-positive, change the <varname>kern_securelevel</varname> and + <varname>kern_securelevel_enable</varname> variables in + <filename>/etc/rc.conf</filename> and reboot.</para> <para>For more information on securelevel and the specific @@ -5699,8 +5684,8 @@ Key F15 A A Menu Wo queries. Recent versions of it choose a new, random UDP port for each query. This may cause problems for some network configurations, especially if a firewall blocks - incoming UDP packets on particular ports. If you want to - get past that firewall, you can try the + incoming UDP packets on particular ports. To + get past that firewall, try the <literal>avoid-v4-udp-ports</literal> and <literal>avoid-v6-udp-ports</literal> options to avoid selecting random port numbers within a blocked @@ -5717,7 +5702,7 @@ Key F15 A A Menu Wo </warning> <para>Congratulations, by the way. It is good practice to - read your &man.sockstat.1; output and notice odd + read &man.sockstat.1; output and notice odd things!</para> </answer> </qandaentry> @@ -5747,39 +5732,37 @@ Key F15 A A Menu Wo <answer> <para>Do not worry. <systemitem class="username">toor</systemitem> is an - <quote>alternative</quote> superuser account (toor is root - spelt backwards). Previously it was created when the - &man.bash.1; shell was installed but now it is created by - default. It is intended to be used with a non-standard - shell so you do not have to change <systemitem - class="username">root</systemitem>'s default shell. + <quote>alternative</quote> superuser account, where toor is root + spelled backwards. It is intended to be used with a non-standard + shell so the default shell for <systemitem + class="username">root</systemitem> does not need to change. This is important as shells which are not part of the base - distribution (for example a shell installed from ports or - packages) are likely to be installed in + distribution, but are instead installed from ports or + packages, are installed in <filename>/usr/local/bin</filename> which, by default, resides on a different file system. If <systemitem class="username">root</systemitem>'s shell is located in - <filename>/usr/local/bin</filename> and - <filename>/usr</filename> (or whatever file system - contains <filename>/usr/local/bin</filename>) is not - mounted for some reason, <systemitem + <filename>/usr/local/bin</filename> and the + file system + containing <filename>/usr/local/bin</filename>) is not + mounted, <systemitem class="username">root</systemitem> will not be able to - log in to fix a problem (although if you reboot into - single-user mode you will be prompted for the path to a - shell).</para> + log in to fix a problem and will have to reboot into + single-user mode in order to enter the path to a + shell.</para> <para>Some people use <systemitem class="username">toor</systemitem> for day-to-day <systemitem class="username">root</systemitem> tasks with a non-standard shell, leaving <systemitem class="username">root</systemitem>, with a standard - shell, for single-user mode or emergencies. By default - you cannot log in using <systemitem + shell, for single-user mode or emergencies. By default, a + user cannot log in using <systemitem class="username">toor</systemitem> as it does not have a password, so log in as <systemitem class="username">root</systemitem> and set a password - for <systemitem class="username">toor</systemitem> if you - want to use it.</para> + for <systemitem class="username">toor</systemitem> before + using it to login.</para> </answer> </qandaentry> </qandaset> @@ -5796,30 +5779,28 @@ Key F15 A A Menu Wo </question> <answer> - <para>You should first read the &man.ppp.8; manual page and + <para>First, read &man.ppp.8; and the <link xlink:href="&url.books.handbook;/ppp-and-slip.html#userppp">PPP - section of the Handbook</link>. Enable logging with the + section of the Handbook</link>. To assist in + troubleshooting, enable logging with the following command:</para> <programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting> <para>This command may be typed at the &man.ppp.8; command - prompt or it may be entered in the - <filename>/etc/ppp/ppp.conf</filename> configuration file - (the start of the <literal>default</literal> section is - the best place to put it). Make sure that - <filename>/etc/syslog.conf</filename> (see - &man.syslog.conf.5;) contains the lines below and the file + prompt or it may be entered at the start of the + <literal>default</literal> section + in <filename>/etc/ppp/ppp.conf</filename>. Make sure that + <filename>/etc/syslog.conf</filename> contains the lines below and the file <filename>/var/log/ppp.log</filename> exists:</para> <programlisting>!ppp *.* /var/log/ppp.log</programlisting> - <para>You can now find out a lot about what is going on from - the log file. Do not worry if it does not all make sense. - If you need to get help from someone, it may make sense to - them.</para> + <para>A lot about what is going can be learned from + the log file. Do not worry if it does not all make sense as + it may make sense to someone else.</para> </answer> </qandaentry> @@ -5829,23 +5810,22 @@ Key F15 A A Menu Wo </question> <answer> - <para>This is usually because your hostname will not + <para>This is usually because the hostname will not resolve. The best way to fix this is to make sure that - <filename>/etc/hosts</filename> is consulted by your - resolver first by editing - <filename>/etc/host.conf</filename> and putting the - <literal>hosts</literal> line first. Then, put an - entry in <filename>/etc/hosts</filename> for your local - machine. If you have no local network, change your + <filename>/etc/hosts</filename> is read first by the + by ensuring that the <literal>hosts</literal> line is listed first in + <filename>/etc/host.conf</filename>. Then, put an + entry in <filename>/etc/hosts</filename> for the local + machine. If there is no local network, change the <systemitem>localhost</systemitem> line:</para> <programlisting>127.0.0.1 foo.example.com foo localhost</programlisting> - <para>Otherwise, add another entry for your host. + <para>Otherwise, add another entry for the host. Consult the relevant manual pages for more details.</para> - <para>You should be able to successfully <command>ping -c1 - `hostname`</command> when you are done.</para> + <para>When finished, verify that this command is successful: + <command>ping -c1 `hostname`</command>.</para> </answer> </qandaentry> @@ -5856,27 +5836,23 @@ Key F15 A A Menu Wo </question> <answer> - <para>First, check that you have got a default route. By - running <command>netstat -rn</command> (see - &man.netstat.1;), you should see two entries like - this:</para> + <para>First, check that a default route exists. This command + should display two entries:</para> <programlisting>Destination Gateway Flags Refs Use Netif Expire default 10.0.0.2 UGSc 0 0 tun0 10.0.0.2 10.0.0.1 UH 0 0 tun0</programlisting> - <para>This is assuming that you have used the addresses from - the Handbook, the manual page, or from - <filename>ppp.conf.sample</filename>. If you do not have - a default route, it may be because you forgot to add the - <literal>HISADDR</literal> line to - <filename>ppp.conf</filename>.</para> + <para>If + a default route is not listed, make sure that the + <literal>HISADDR</literal> line has been added to + <filename>/etc/ppp/ppp.conf</filename>.</para> <para>Another reason for the default route line being - missing is that you have mistakenly set up a default - router in your <filename>/etc/rc.conf</filename> (see - &man.rc.conf.5;) file and you have omitted the line below - from <filename>ppp.conf</filename>:</para> + missing is that a default + route has been added to <filename>/etc/rc.conf</filename> + and this line is missing + from <filename>/etc/ppp/ppp.conf</filename>:</para> <programlisting>delete ALL</programlisting> @@ -5894,20 +5870,20 @@ default 10.0.0.2 UG </question> <answer> - <para>This error is usually due that the following section - is missing in your + <para>This error is usually because the following section + is missing in <filename>/etc/ppp/ppp.linkup</filename>:</para> <programlisting>MYADDR: delete ALL add 0 0 HISADDR</programlisting> - <para>This is only necessary if you have a dynamic IP - address or do not know the address of your gateway. If - you are using interactive mode, you can type the following - after entering <literal>packet mode</literal> (packet mode + <para>This is only necessary for a dynamic IP + address or when the address of the default gateway is unknown. When + using interactive mode, the following can be typed in + after entering packet mode. Packet mode is indicated by the capitalized <acronym>PPP</acronym> in - the prompt):</para> + the prompt:</para> <programlisting>delete ALL add 0 0 HISADDR</programlisting> @@ -5950,10 +5926,10 @@ add 0 0 HISADDR</programlisting> </question> <answer> - <para>If you have Link Quality Reporting (LQR) configured, - it is possible that too many LQR packets are lost between + <para>If Link Quality Reporting (<acronym>LQR</acronym>) is configured, + it is possible that too many <acronym>LQR</acronym> packets are lost between your machine and the peer. &man.ppp.8; deduces that the - line must therefore be bad, and disconnects. LQR is + line must therefore be bad, and disconnects. <acronym>LQR</acronym> is disabled by default and can be enabled with the following line:</para> @@ -5969,8 +5945,8 @@ add 0 0 HISADDR</programlisting> <answer> <para>Sometimes, on a noisy phone line or even on a line - with call waiting enabled, your modem may hang up because - it thinks (incorrectly) that it lost carrier.</para> + with call waiting enabled, the modem may hang up because + it incorrectly thinks that it lost carrier.</para> <para>There is a setting on most modems for determining how tolerant it should be to temporary losses of carrier. @@ -5989,30 +5965,30 @@ add 0 0 HISADDR</programlisting> apparent explanation. The first thing to establish is which side of the link is hung.</para> - <para>If you are using an external modem, try + <para>When using an external modem, try using &man.ping.8; to see if the <acronym>TD</acronym> - light is flashing when you transmit data. If it flashes - (and the <acronym>RD</acronym> light does not), the + light is flashing when data is transmitted. If it flashes + but the <acronym>RD</acronym> light does not, the problem is with the remote end. If <acronym>TD</acronym> does not flash, the problem is local. With an internal - modem, you will need to use the <literal>set + modem, use the <literal>set server</literal> command in <filename>ppp.conf</filename>. When the hang occurs, - connect to &man.ppp.8; using &man.pppctl.8;. If your - network connection suddenly revives (PPP was revived due - to the activity on the diagnostic socket) or if you cannot - connect (assuming the <literal>set socket</literal> - command succeeded at startup time), the problem is local. - If you can connect and things are still hung, enable local - async logging with <literal>set log local async</literal> + connect to &man.ppp.8; using &man.pppctl.8;. If the + network connection suddenly revives due + to the activity on the diagnostic socket, or if it will not + connect but the <literal>set socket</literal> + command succeeded at startup time, the problem is local. + If it can connect but things are still hung, enable local + logging with <literal>set log local async</literal> and use &man.ping.8; from another window or terminal to - make use of the link. The async logging will show you the + make use of the link. The async logging will show the data being transmitted and received on the link. If data is going out and not coming back, the problem is remote.</para> <para>Having established whether the problem is local or - remote, you now have two possibilities:</para> + remote, there are now two possibilities:</para> <itemizedlist> <listitem> @@ -6035,17 +6011,15 @@ add 0 0 HISADDR</programlisting> </question> <answer> - <para>There is very little you can do about this. Most ISPs - will refuse to help if you are not running a µsoft; - OS. You can <literal>enable lqr</literal> in your - <filename>ppp.conf</filename>, allowing &man.ppp.8; to + <para>There is very little that can be done about this. Many ISPs + will refuse to help users not running a µsoft; + OS. You can <literal>enable lqr</literal> in + <filename>/etc/ppp/ppp.conf</filename>, allowing &man.ppp.8; to detect the remote failure and hang up, but this detection - is relatively slow and therefore not that useful. You may - want to avoid telling your ISP that you are running - user-PPP.</para> + is relatively slow and therefore not that useful.</para> <para>First, try disabling all local compression by adding - the following to your configuration:</para> + the following to the configuration:</para> <programlisting>disable pred1 deflate deflate24 protocomp acfcomp shortseq vj deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting> @@ -6053,12 +6027,11 @@ deny pred1 deflate deflate24 protocomp a <para>Then reconnect to ensure that this makes no difference. If things improve or if the problem is solved completely, determine which setting makes the difference - through trial and error. This will provide good - ammunition when you contact your ISP (although it may make - it apparent that you are not running a µsoft; - product).</para> + through trial and error. This is good information for + the ISP, although it may make + it apparent that it is not a µsoft; system.</para> - <para>Before contacting your ISP, enable async logging + <para>Before contacting the ISP, enable async logging locally and wait until the connection hangs again. This may use up quite a bit of disk space. The last data read from the port may be of interest. It is usually ASCII @@ -6066,9 +6039,9 @@ deny pred1 deflate deflate24 protocomp a fault</errorname>, <errorname>Core dumped</errorname>).</para> - <para>If your ISP is helpful, they should be able to enable + <para>If the ISP is helpful, they should be able to enable logging on their end, then when the next link drop occurs, - they may be able to tell you why their side is having a + they may be able to tell why their side is having a problem.</para> </answer> </qandaentry> @@ -6079,18 +6052,18 @@ deny pred1 deflate deflate24 protocomp a </question> <answer> - <para>Your best bet here is to rebuild &man.ppp.8; with + <para>In this case, rebuild &man.ppp.8; with debugging information, and then use &man.gdb.1; to grab a stack trace from the <application>ppp</application> process that is stuck. To rebuild the <application>ppp</application> utility with debugging - information, you can type:</para> + information, type:</para> <screen>&prompt.root; <userinput>cd /usr/src/usr.sbin/ppp</userinput> &prompt.root; <userinput>env DEBUG_FLAGS='-g' make clean</userinput> &prompt.root; <userinput>env DEBUG_FLAGS='-g' make install</userinput></screen> - <para>Then you should restart <application>ppp</application> + <para>Then, restart <application>ppp</application> and wait until it hangs again. When the debug build of <application>ppp</application> hangs, start <application>gdb</application> on the stuck process by @@ -6098,9 +6071,9 @@ deny pred1 deflate deflate24 protocomp a <screen>&prompt.root; <userinput>gdb ppp `pgrep ppp`</userinput></screen> - <para>At the <application>gdb</application> prompt, you can + <para>At the <application>gdb</application> prompt, use the <command>bt</command> or <command>where</command> - commands to get a stack trace. Save the output of your + commands to get a stack trace. Save the output of the <application>gdb</application> session, and <quote>detach</quote> from the running process by typing <command>quit</command>.</para> @@ -6114,12 +6087,12 @@ deny pred1 deflate deflate24 protocomp a </question> <answer> - <para>Occasionally, just after connecting, you may see + <para>Occasionally, just after connecting, there may be messages in the log that say <errorname>Magic is same</errorname>. Sometimes, these messages are harmless, and sometimes one side or the other exits. Most PPP implementations cannot survive this problem, and even - if the link seems to come up, you will see repeated + if the link seems to come up, there will be repeated configure requests and configure acknowledgments in the log file until &man.ppp.8; eventually gives up and closes the connection.</para>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405141958.s4EJwp64024027>