| Age | Commit message (Collapse) | Author | Files |
|---|
|
|
|
subdirectory of the source code. The OE autotools.bbclass runs the autoconf
stuff in ${S}, so you need to change ${S} to the src subdirectory to get it
to work. But ${S} is also where patches are appplied, so you can't patch the
config files and other things which aren't in the src directory. So add some
autoconf at the top level which just says there's a sub-autoconf project in
the src subdirectory, fix up the patches, remove the sed hacks and add a new
patch to do what the sed hacks were doing before.
|
|
* Seperate out the server, sniff and relay programs from the main
package.
* Add an init script for the server.
* Add templates to the AC_DEFINE's in the configure script so the
variables are correctly added to the header. Without this the
variables don't get added and server and relay complain about not
being able to be used on linux 2.0 system.
|
|
* Recommend ppp-oe, which is the PPPoE plugin module for PPP to
enable the kernel mode PPPoE which is a lot faster, has lower
latency and uses less CPU.
* Remove the module path from the configuration file since it's wrong
and it's not needed.
* Don't check for the location of echo on the host, just use
/bin/echo - it's only needed for the script that rp-pppoe installs.
|
|
* The source for version 3.5 hasn't been available for a long time.
* Make sure pppoe is installed suid root.
* Always try to reconnect, pppd handles stop/starting pppoe. This prevents
lots of annoying problems with pppoe totally giving up (debian patch)
* Accept PPPoE packets from multicast addresses (debian patch)
* Don't check the version of the hosts ppp, we don't support the older
versions of ppp anyway so just remove those checks.
* RDEPEND on ppp, which is needed to use pppoe
* Hard code pppd and id paths, don't search for them on the host system.
|
