PPPOE-CONNECT(8)

💖 PPPOE-CONNECT(8) 💖

ok so bestie, this is a page from the System Manager's Manual, and it's about pppoe-connect — a little shell script that runs your PPPoE link like a boss. it's giving "quietly holding your whole internet together" energy. 🌸

---

✨ NAME ✨

pppoe-connect — a shell script that manages a PPPoE link. she's the manager. she handles it. 🫶

---

🌟 SYNOPSIS 🌟

pppoe-connect [config_file]

pppoe-connect interface user [config_file]

---

🎀 DESCRIPTION 🎀

pppoe-connect is a shell script that manages a PPPoE connection using the Roaring Penguin user-space PPPoE client. iconic honestly. 👑

If you omit config_file, the default file /etc/ppp/pppoe.conf is used. no config? she's got a fave, don't worry. 💅

If you supply interface and user, then they override the Ethernet interface and user-name settings in the configuration file. like, you're the main character now, your args win. ✨

🚨 okay bestie, listen: normally you should not invoke pppoe-connect directly. instead, use pppoe-start to bring up the PPPoE connection. pppoe-connect is the backstage crew, not the opener. 🙈

So here's the whole vibe: pppoe-connect first reads a configuration file. then it brings up a PPPoE connection. 🦋

If the connection ever drops, a message is logged to syslog, and pppoe-connect re-establishes the connection. she does not let it go. she's persistent like that. 💪

In addition, each time the connection is dropped or cannot be established, pppoe-connect executes the script /etc/ppp/pppoe-lost if it exists and is executable. (yes, only if it exists and is executable — no sneaky half-configured scripts getting run, periodt.) 🔥

The shell script pppoe-stop causes pppoe-connect to break out of its loop, bring the connection down, and exit. so pppoe-stop is the "we're done here" text. 😌

---

🔧 TECHNICAL DETAILS 🔧

pppoe-connect uses the following shell variables from the configuration file:

• ETH — the Ethernet interface connected to the DSL modem (for example, eth0). that's the plug-in spot. 🔌
• USER — the PPPoE user-id (for example, b1xxnxnx@sympatico.ca). that's you, that's your login, bestie. 💜
• PIDFILE — a file in which to write the process-ID of the pppoe-connect process (for example, /var/run/pppoe.pid). and here's the cute part: two additional files ($PIDFILE.pppd and $PIDFILE.pppoe) hold the process-ID's of the pppd and pppoe processes, respectively. so three little ID files, all matching, all besties. 🎀

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 and pppoe-stop. multitasking queen behavior. 👑✨

---

🌈 AUTHOR 🌈

pppoe-connect was written by Dianne Skoll <dianne@skoll.ca>. absolute legend, we stan. 💖

The pppoe home page is https://dianne.skoll.ca/projects/rp-pppoe/. go say hi, iykyk. 🧚

---

🌸 SEE ALSO 🌸

pppoe(8), pppoe-start(8), pppoe-stop(8), pppd(8), pppoe.conf(5), pppoe-setup(8), pppoe-status(8), pppoe-sniff(8), pppoe-server(8), pppoe-relay(8)

---

ok that's the whole page!! 💅 this one came from the 4th Berkeley Distribution, and it's dated 21 February 2000 — yes, vintage, yes, still serving. slay, drink water, and go run pppoe-start instead of calling this script directly, mwah 🫶💖✨