rp-pppoe is a PPPoE client and server suite for Linux. It is fully RFC-compliant and supports cookies, relay-IDs, and multiple simultaneous PPPoE discovery phases. It is cleanly coded and fairly efficient, and supports kernel-mode PPPoE on Linux 2.4 and 2.6.
| Tags | Networking |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX BSD NetBSD Linux Solaris |
Recent releases


Changes: Compilation problems on various platforms were fixed. The Makefiles now obey DESTDIR to relocate installed files. The kernel-mode PPPoE plugin is easier to compile, since you do no longer need to specify the path to pppd.h if it's installed under /usr/include.


Changes: A new pppoe-server option lets you limit the number of sessions per MAC address. Various minor bugs were fixed.


Changes: The code was refactored to shrink the size of the pppoe-executable. The ability to omit debugging code was also added. A bug in the MD5 code that caused pppoe-server to segfault on 64-bit architectures was fixed.


Changes: A new -O option was added to pppoe-server to specify a different options file for pppd (instead of the default /etc/ppp/pppoe-server-options). A typo in the firewall-standalone sample firewall script and one in pppoe-connect were fixed. Some incorrect coding in configure.in was fixed. pppoe-server now prepends "nic-" to the interface name if used with the kernel-mode plugin, allowing the use of any Ethernet interface (not just ones starting with "eth").


Changes: The kernel-mode plugin works again; it was broken by changes to the pppd program. A long-standing bug in the pppoe-server program (which called pppd with arguments in the wrong order) has been fixed. All the adsl-* scripts have been renamed to pppoe-* for consistency and to more accurately describe their function. The kernel-mode plugin can use any interface if you prefix the interface name with "nic-"; it's no longer restricted to interfaces that start with "eth". The userland pppoe program runs as "nobody" rather than "root" once the session has started.
- All comments
Recent commentsRe: Roaring Penguin PPPoE client
% I how configure this client.
Just run adsl-setup and follow the prompts. Or run the GUI ((tkpppoe) and fill in the fields. It's pretty intuitive.
Re: Roaring Penguin PPPoE client
This PPPoE client works with Linux RedHat 9.0??
and I how configure this client.
It excuses by my ingles.
Re: Roaring Penguin PPPoE client
rp-pppoe is great software.. should be included
with more CDROM distributions, imho (particularly
with adsl on the rise as a solution for home
networking)..
ive noticed a wierd bug though, when i recompiled
rp-pppoe for kernel 2.4.2: the pppoe kernel-mode
works, but only root has access to the connection.
has this happened to anyone else? is there an
easy fix?
Re: Roaring Penguin PPPoE client
> Linux 2.4.0 isn't really bleeding edge
> anymore. PPPoE in the kernel plus pppd
> 2.4.0 works like a charm.
It does indeed. And the latest rp-pppoe (2.8) supports kernel-mode PPPoE, but with the same simple setup and start/stop scripts as user-mode PPPoE.
Re: Roaring Penguin PPPoE client
> I have had great success with the
> Roaring Penguin client and my PacBell
> DSL account.
> It runs in userspace, which means it's
> not super-efficient, but I also don't
> have to worry about a bleeding-edge
> kernel module crashing my firewall. At
> full tilt on my 1.5Mbps DSL line, the
> pppoe CPU usage has spiked up to as high
> as 70% on my 486 router/firewall. This
> is fine with me, but something to think
> about if you are using a low-powered
> machine with other duties besides just
> routing.
Linux 2.4.0 isn't really bleeding edge anymore. PPPoE in the kernel plus pppd 2.4.0 works like a charm.