Download the PPPoE Client - EnterNet 100 for Linux (tested on RED HAT) here: enternet100src_linux.zip
How-To for EnterNet 100 for Linux, PPPoE Client, Version 1.300.000
This outline of how to install was prepared for use on Red Hat Linux 5.2,
6.0, and 6.1.
Place files: pppoed, start-pppoe, and stop-pppoe in the directory
/usr/local/bin.
You can use a different binary directory, but you will need to reflect
those changes in the start-pppoe shell script.
Edit the shell script start-pppoe, follow the comments in the area marked off
as "User Changeable Area". Be sure to put in your correct USERID in the
start-pppoe file. If you were given a specific Service Name to use and/or
Access Concentrator, make those changes as well.
Update /etc/ppp/chap-secrets and pap-secrets with your login UserID and
password information provided by your service provider.
Below are examples of pap-secrets file entries:
# Secrets for Authentication using PAP
# Client server secret IP address
myuserid * donttell *
If you need more information about the pap-secrets or chap-secrets file see
the man pages for pppd.
Place options.pppoe in the /etc/ppp directory.
If you do not have an Ethernet NIC installed, install one now. Refer to
NET3-HOWTO or Linux-related documentation for help on setting up networking.
"ifconfig" can be used to list the network interfaces currently up and running
on you system. Most network install procedures/programs/scripts will want an
IP address for the Ethernet NIC. Use an address such as 10.1.1.1 from the
private address list. Do not configure the NIC for DHCP or bootp.
The command line below is used to put the ethernet port in a usable state for
doing PPPoE. This line is included in the start-ppppoe script:
ifconfig eth0 0.0.0.0 up -broadcast -arp
This has the effect of stopping all IP activities on the ethernet interface,
thereby enabling it to send and receive only PPPoE packets.
Note: Leaving an old IP address on any network interface
that is of the same sub-network, as the one your PPPoE
connection uses, may cause either connection failure or
routing confusion. An IP Address from the list of private
addresses should not be a problem.
You will need to update the file /etc/resolv.conf with Sentex DNS informaiton. An updated
file may look like this: