Angel Tsankov wrote:pppd call pppoe dryrun eth0This seems to produce some more info. Here it is (the peer file for this PPPoE connection is called megalan53):Plugin rp-pppoe.so loaded. RP-PPPoE plugin version 3.3 compiled against pppd 2.4.3 pppd options in effect: holdoff 15 # (from /etc/ppp/peers/megalan53) persist # (from /etc/ppp/peers/megalan53) dryrun # (from command line) plugin rp-pppoe.so # (from /etc/ppp/peers/megalan53) noauth # (from /etc/ppp/peers/megalan53) user sven # (from /etc/ppp/peers/megalan53) eth0 # (from command line) rp_pppoe_service megalan53 # (from /etc/ppp/peers/megalan53) eth0 # (from command line) rp_pppoe_service megalan53 # (from /etc/ppp/peers/megalan53) mru 1492 # (from /etc/ppp/peers/megalan53) mtu 1492 # (from /etc/ppp/peers/megalan53) lcp-echo-failure 3 # (from /etc/ppp/peers/megalan53) lcp-echo-interval 30 # (from /etc/ppp/peers/megalan53) defaultroute # (from /etc/ppp/peers/megalan53) usepeerdns # (from /etc/ppp/peers/megalan53) If you need further assistance in tackling this issue just let me know.Still doesn't help. Could you please, after connecting, issue this command: ip link list and paste the entire output. But if that doesn't show the problem, I give up.
Hmm, eth0 has mtu=1500, I guess this might be the problem: 1: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0c:29:41:f1:c1 brd ff:ff:ff:ff:ff:ff2: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop link/ether 3e:82:66:ca:40:4f brd ff:ff:ff:ff:ff:ff
4: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1492 qdisc pfifo_fast qlen 3link/ppp
I have also attached the /etc/ppp/options and /etc/ppp/peers/megalan53 files.
etc-ppp.tar.gz
Description: Binary data
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
