Hello Matthew, I hope that I can help you a bit. 1. the difference between dachstein and bering is that Dachstein uses rp-pppoe and bering uses kernel pppoe. 2. you can setup an pppoe server without getty and so on, just by using the pppoe.lrp and ppp.lrp. I set a test one up . how I did it : http://www.mail-archive.com/[EMAIL PROTECTED]/msg06510.html
Interesting is that you get a connection > > Nov 25 08:53:01 firewall pppd[8591]: pppd 2.4.1 started by LOGIN, uid 0 > Nov 25 08:53:01 firewall pppd[8591]: using channel 25 > Nov 25 08:53:01 firewall pppd[8591]: Using interface ppp1 > Nov 25 08:53:01 firewall pppd[8591]: Connect: ppp1 <--> /dev/ttyS0 ........ Nov 25 08:53:04 firewall pppd[8591]: remote IP address 192.168.5.99 > Nov 25 08:53:04 firewall pppd[8591]: Script /etc/ppp/ip-up started (pid > 4309) > Nov 25 08:53:04 firewall pppd[8591]: Script /etc/ppp/ip-up finished (pid > 4309), status = 0x100 After establishing the connection the "pings" aren't answered by the client.. > Nov 25 08:53:37 firewall pppd[7359]: No response to 3 echo-requests > Nov 25 08:53:37 firewall pppd[7359]: Serial link appears to be disconnected. and the server hangs up again. or better said pppd hangsup.. it seems that the whole pppd gets a signal to go down ov 25 08:53:37 firewall pppd[7359]: Couldn't increase MTU to 1500. > Nov 25 08:53:37 firewall pppd[7359]: Couldn't increase MRU to 1500 > Nov 25 08:53:43 firewall pppd[7359]: Connection terminated. > Nov 25 08:53:43 firewall pppd[7359]: Connect time 561.8 minutes. And so your dialout connection over ppp0 is also taken down. I don't know why this is done. I suppose this should be an option setting. The other problem is why does the dialin client doesn't answer on lcp requests. 1. is this a route problem on the client ? 2 is the client running a firewall and doesn't answer pings ? 3 ? > Now the catch is that when the connection drops out (why it does it, I do > not know why) the external pppoe connection is then also torn down, and it > has to reconnect and get a new address, which it does. I can only assume > that it is something to do with the pppd setup interacting between the two > ppp interfaces. I suppose so too ;) > I include my /etc/network/interfaces, and /etc/ppp/peers/dialin, > /etc/ppp/peers/adslprovider, and /etc/ppp/options and /etc/options.ttyS0 > files in the hope that someone can point out why this interaction is > occurring. I have no options file. > > pppd is called from login.config as: > > /AutoPPP/ - - /usr/sbin/pppd debug file /etc/ppp/options.ttyS0 Try it the way I described in the archived mail pleas give a feedback if this worked. Regards eric Wolzak member of the bering crew # # original configuration files # # # > So as far as I can see the dial in connection should not reference > /etc/ppp/options > > # /etc/network/interfaces -- configuration file for LEAF network > # J. Nilo, April 2002 > # > # Loopback interface. > auto lo > iface lo inet loopback > > auto ppp0 > iface ppp0 inet ppp > pre-up ip link set eth0 up > provider adslprovider eth0 > > iface ppp1 inet ppp > provider dialin > > auto eth1 > iface eth1 inet static > address 192.168.5.254 > masklen 24 > broadcast 192.168.5.255 > > auto eth2 > iface eth2 inet static > address 203.a.b.c > masklen 27 > broadcast 203.a.b.255 > # ---<End of File>--- > > > /etc/ppp/peers/dialin > > debug > ms-dns 192.168.5.254 > asyncmap 0 > auth > crtscts > modem > noccp > -detach > +pap > -chap > +pap > require-pap > refuse-chap > proxyarp > lcp-echo-interval 300 > lcp-echo-failure 4 > noipx > # ---<End of File>--- > > > /etc/ppp/peers/adslprovider > > # Configuration file for PPP, using PPP over Ethernet > # to connect to a DSL provider. > plugin /usr/lib/pppd/pppoe.so > name "[EMAIL PROTECTED]" > pty "pppoe -I eth0 -T 80 -m 1452" > noipdefault > hide-password > lcp-echo-interval 20 > lcp-echo-failure 3 > # Override any connect script that may have been set in /etc/ppp/options. > connect /bin/true > noauth > persist > mtu 1492 > # ---<End of File>--- > > /etc/ppp/options is empty > > /etc/ppp/options.ttyS0 > > debug > -detach > auth > asyncmap 0 > modem > crtscts > lock > noccp > +pap > require-pap > refuse-chap > proxyarp > lcp-echo-interval 300 > lcp-echo-failure 10 > ms-dns 192.168.5.254 > netmask 255.255.255.0 > 192.168.5.254:192.168.5.99 > # ---<End of File>--- > > I appreciate Shorewall plays a part in this, but I have not yet seen one > rejected packet in its logs, and it is setup to allow masq from > 192.168.5.0/24 (which is my internal network) and this works as well as a > non mentioned wlan setup using hostap that is working fine as well. > > Can anyone shed some light on this, otherwise I will have to go back to > Dachstein which worked very easily and was easy to set up. By far the most > difficult this in this setup is pppd however the debian format > /etc/network/interfaces file is an absolute mystery to me never having used > anything like it before. > > With many thanks, > Matthew > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
