\n| <\/td>\n | \n DEMAND<\/b><\/p>\n<\/td>\n | <\/td>\n | \n If set to a number, the link is activated on demand and brought down after after DEMAND<\/b> seconds. If set to no<\/b>, the link is kept up all the time rather than being activated on demand.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n DNSTYPE<\/b><\/p>\n One of NOCHANGE<\/b>, SPECIFY<\/b> or SERVER<\/b>. If set to NOCHANGE, pppoe-connect<\/b> will not adjust the DNS setup in any way. If set to SPECIFY, it will re-write \/etc\/resolv.conf with the values of DNS1 and DNS2. If set to SERVER<\/b>, it will supply the usepeerdns<\/i> option to pppd<\/b>, and make a symlink from \/etc\/resolv.conf to \/etc\/ppp\/resolv.conf.<\/p>\n DNS1, DNS2<\/b><\/p>\n IP addresses of DNS servers if you use DNSTYPE=SPECIFY.<\/p>\n NONROOT<\/b><\/p>\n If the line NONROOT=OK<\/b> (exactly like that; no whitespace or comments) appears in the configuration file, then pppoe-wrapper<\/b> will allow non-root users to bring the conneciton up or down. The wrapper is installed only if you installed the rp-pppoe-gui package.<\/p>\n USEPEERDNS<\/b><\/p>\n If set to “yes”, then pppoe-connect<\/b> will supply the usepeerdns<\/i> option to pppd<\/b>, which causes it to obtain DNS server addresses from the peer and create a new \/etc\/resolv.conf<\/b> file. Otherwise, pppoe-connect<\/b> will not supply this option, and pppd<\/b> will not modify \/etc\/resolv.conf<\/b>.<\/p>\n CONNECT_POLL<\/b><\/p>\n How often (in seconds) pppoe-start<\/b> should check to see if a new PPP interface has come up. If this is set to 0, the pppoe-start<\/b> simply initiates the PPP session, but does not wait to see if it comes up successfully.<\/p>\n CONNECT_TIMEOUT<\/b><\/p>\n How long (in seconds) pppoe-start<\/b> should wait for a new PPP interface to come up before concluding that pppoe-connect<\/b> has failed and killing the session.<\/p>\n\n\n| <\/td>\n | \n PING<\/b><\/p>\n<\/td>\n | <\/td>\n | \n A character which is echoed every CONNECT_POLL<\/b> seconds while pppoe-start<\/b> is waiting for the PPP interface to come up.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n FORCEPING<\/b><\/p>\n A character which is echoed every CONNECT_POLL<\/b> seconds while pppoe-start<\/b> is waiting for the PPP interface to come up. Similar to PING<\/b>, but the character is echoed even if pppoe-start<\/b>\u2019s standard output is not a tty.<\/p>\n PIDFILE<\/b><\/p>\n A file in which to write the process-ID of the pppoe-connect process (for example, \/var\/run\/pppoe.pid<\/b>). Two additional files ($PIDFILE.pppd and $PIDFILE.pppoe) hold the process-ID\u2019s of the pppd<\/b> and pppoe<\/b> processes, respectively.<\/p>\n SYNCHRONOUS<\/b><\/p>\n An indication of whether or not to use synchronous PPP (yes<\/b> or no<\/b>). Synchronous PPP is safe on Linux machines with the n_hdlc line discipline. (If you have a file called “n_hdlc.o” in your modules directory, you have the line discipline.) It is not recommended<\/i> on other machines or on Linux machines without the n_hdlc line discipline due to some known and unsolveable race conditions in a user-mode client.<\/p>\n CLAMPMSS<\/b><\/p>\n The value at which to “clamp” the advertised MSS for TCP sessions. The default of 1412 should be fine.<\/p>\n LCP_INTERVAL<\/b><\/p>\n How often (in seconds) pppd<\/b> sends out LCP echo-request packets.<\/p>\n LCP_FAILURE<\/b><\/p>\n How many unanswered LCP echo-requests must occur before pppd<\/b> concludes the link is dead.<\/p>\n PPPOE_TIMEOUT<\/b><\/p>\n If this many seconds elapse without any activity seen by pppoe<\/b>, then pppoe<\/b> exits.<\/p>\n FIREWALL<\/b><\/p>\n One of NONE, STANDALONE or MASQUERADE. If NONE, then pppoe-connect<\/b> does not add any firewall rules. If STANDALONE, then it clears existing firewall rules and sets up basic rules for a standalone machine. If MASQUERADE, then it clears existing firewall rules and sets up basic rules for an Internet gateway. If you run services on your machine, these simple firewall scripts are inadequate; you\u2019ll have to make your own firewall rules and set FIREWALL to NONE.<\/p>\n PPPOE_EXTRA<\/b><\/p>\n Any extra arguments to pass to pppoe<\/b><\/p>\n PPPD_EXTRA<\/b><\/p>\n Any extra arguments to pass to pppd<\/b><\/p>\n LINUX_PLUGIN<\/b><\/p>\n If non-blank, the full path of the Linux kernel-mode PPPoE plugin (typically \/etc\/ppp\/plugins\/rp-pppoe.so<\/b>.) This forces pppoe-connect<\/b> to use kernel-mode PPPoE on Linux 2.4.x systems. This code is experimental and unsupported. Use of the plugin causes pppoe-connect<\/b> to ignore CLAMPMSS, PPPOE_EXTRA, SYNCHRONOUS and PPPOE_TIMEOUT.<\/p>\n By using different configuration files with different PIDFILE settings, you can manage multiple PPPoE connections. Just specify the configuration file as an argument to pppoe-start<\/b> and pppoe-stop<\/b>.<\/p>\n | |