Hendrik Sattler wrote:
Some people may want to put everything related to network config in 1 file to ease the management, other people may put it in /etc/ppp/chap-secrets or anywhere else, they are all supported.Am Sonntag 17 Februar 2008 schrieb namnd:The ppp stanza should not contain authentication information. Especially since username/password only covers the most simple authentication method. And other parts could use a auth tag, too (ethernet, wlan, etc.).In this case, the configuration is as easy as: <interface name="fpt1" type="ppp"> <ppp type="pppoe" options="" depend_on="tap1" username="***" password="***"/> <network id="11" name="FPT1" auto="1"/> </interface>Additionally, the options attribute sounds like a work-around.
No doubt, each interface type may has its own authentication configuration (such as wlan interface will support WPA). The idea is that there is a template for external daemon (such as pppd, openvpn, vtun, ...) lying somewhere else, netupdown takes the template and fill the place holders with the content in the main config file, save the final conf file in /var/run, and starts the daemon. This template mechanism solves many problems fixed conf file can not do, such as binding local IP address to the dynamic IP address of a ppp interface.
The options attribute is used for people who need to configure parameters aren't defined in the template, this work arround is necessary for some of my cases.
Best regards, Nam