Hello All,
I succeeded in creating a pppoe server with bering useing only the
"standard" pppoe.lrp and ppp.lrp
This is one method, there might exists others.
apart from the pppoe settings, i will account for later the setup is
identical to that of a dialin ppp server .
So experts for that item might help. (please ;) )
You have to uncomment the modules as used for pppoe
also in /etc/modules
slhc
n_hdlc
ppp_generic
pppox
pppoe
------------
the ppp options and pppoe options file (dsl-provider) are used as "one big
file" so be carefull if you uncomment an option in the pppoe file, and leave
it in the ppp file than it still is set.
my /etc/ppp/options file
asyncmap 0
crtscts
hide-password
local
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
silent
persist
now for each pppoe port you want to use ( or in other words for each remote
machine you want to connect) ,you have to create a server file with the
remote and local ip and an entry in the interfaces file.
Assume we want to let two machines connect to pppoe on eth0 with a local
address of 10.0.0.1 for the server and
10.0.0.21 and 10.0.0.32 for the remote machines. let the login name be eric
(how original ;) ) and the password be "bering"
The localhost name is firewall.
the name of the access concentrator is bering_AC
create /etc/ppp/peers/dsl-server1
# this is the configuration for pppoe-server 1 on ppp0
plugin /usr/lib/pppd/pppoe.so
pppoe_server
pppoe_ac_name bering_AC
10.0.0.1:10.0.0.21
require-pap
name firewall
mtu 1492
------------------
create /etc/ppp/peers/dsl-server2
# this is the configuration for dsl-server 2 on ppp1
plugin /usr/lib/pppd/pppoe.so
pppoe_server
pppoe_ac_name bering_AC
10.0.0.1:10.0.0.32
require-pap
name firewall
mtu 1492
-----------------
edit /etc/interfaces
auto ppp0 # if setup automatically
iface ppp0 inet ppp
pre-up ip link set eth0 up
provider dsl-server1 eth0
auto ppp1
iface ppp1 inet ppp
pre-up ip link set eth1 up
provider dsl-server2 eth0
-----------------------
edit /etc/ppp/pap-secrets
-----------------
eric firewall bering *
-----------------
The clients are setup as usual
I tested this on a local network.
I had still some problems, but mostly this was with the clients.
I now could identify a problem that was described by users not able to
connect after a disconnect.
If a (rp-pppoe debian ) client takes the line down with poff dsl-provider no
lcp terminate is send, so the server ppp0 is still in use and sending lcp
echo requests. and it will take the number of lcp-echo-failure multiplied
by the echo intervall time to free the port.
If the client does a pon during this time and has a shorter "failure
recognition" it will stop connecting.
A bering client that is "cut off " by a ifdown ppp0 on the server will
reconnect a soon as an ifup ppp0 on the server is done
I hope to get feedback,
If the positive result is confirmed , I will add this to the pppoe chapter
in the user guide
Regards
Eric Wolzak
member of the bering Crew
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
