Welcome to the EzPPP project page
The project formerly known as xppp
Click here for another screen shot.
News:
- February 20, 1997: Beta 8 is released. I broke EzPPP rather badly in
beta 7. It's much better now. It's amazing what a difference 2 lines make...
- February 16, 1997: Beta 7 is released. Fixed bugs in the script creator.
If you were unable to use EzPPP because of a "Expecting: ~", your
problems are over. EzPPP no longer waits for the PPP packet before
exec'ing the pppd daemon, it just waits for two seconds
after finishing the script. Re-written debug window allows scrolling and
resizing.
- The pppd daemon dies if it can't find the /etc/ppp/options file, so
please disregard my suggestion to remove it. Just make sure that there
are not any options in it.
- I usually wouldn't put this in a project page, but I'm sure most
people visiting this page wouldn't like being charged an extra dollar an
hour for connect time, so visit the
FCC's Access Charge Reform bill.
Downloadable Software
The staticly linked version is probably the best choice for Linux
beginners
Site | Description | Version | Link |
Primary |
EzPPP Compiled ELF, Shared Libs, Docs, and Source |
Version 1.0 Beta 8 |
ezppp-1.0B8.tar.gz |
Primary |
EzPPP Compiled ELF, Docs, Staticly Linked Libs |
Version 1.0 Beta 8 |
ezppp-1.0B8-static.tar.gz |
EzPPP is distributed under the GNU >= 2.0 Licencing Agreement.
Documentation
README First! (Really)
- Make sure that the path to the pppd daemon points to the REAL pppd
program, not a script as it does in Slackware96. If your EzPPP program doesn't
have the path of the real pppd daemon, pppd will fork off and EzPPP will think
the pppd daemon died, remove the DNS entries from /etc/resolv.conf, and go
back into "Connect" mode.
- You need to have write permission to /etc/resolv.conf so that EzPPP can
dynamicly add/remove DNS entries from the file. If you don't have such
permissions, the DNS entries will have to be entered into resolv.conf by root
manually.
- Remove options from the /etc/ppp/options file so that pppd
won't see it, and will take it's options from the command line. You can
customize pppd options on a account-by-account basis using the Edit default
pppd Arguments button in the Edit Account window. But.... *DANGER* Every
line you add is an equivalent to one, non-spaced argument which is passed
to pppd. Here is an example: to set the Maximum Transmission Unit you
would enter "mtu" as one argument and "296" as the NEXT argument, not "mtu
296" as one argument. If you did, the pppd daemon wouldn't recognize it
and would fail.
I've used the Qt C++ GUI toolkit for this program. The toolkit is free
to Linux users under a GNU-type licence. You can check them out at
http://www.troll.no.
I've done all my work on an Intel machine, but if anyone would like to
get it ported over to Linux on some other system, drop me some e-mail at
cameron@serv.net. This isn't my own
e-mail address, so put something like "ezppp" in the subject so it gets to
me,and keep an eye on this page because I'll have my own e-mail address by the
beginning of February.
Here are some of the features:
- No more chat program
- GUI interface for script creation; supports hangup/answer for callback
security
- no more #$%@# chat program
- multiple accounts
Here are some things which I'd like to do for a final, or second version
release:
- start the kernel ppp directly, no pppd daemon
- have a terminal login session automagically create a login script;
I've written the base code for this, but there are many, many special
cases to look out for with something like this
- add a "dial from location..." section
- accounting information on the main xppp window, like k/sec,
time on, etc...
Some things that really should be done but I'll never do:
- change the format of the .ezppprc file from a binary file to a editable
text file
Last modified February 20, 1997
Jay
Painter