From owner-freebsd-hackers Mon Dec 3 15:54: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.anu.edu.au (mail.anu.edu.au [150.203.2.7]) by hub.freebsd.org (Postfix) with ESMTP id E291E37B420; Mon, 3 Dec 2001 15:53:54 -0800 (PST) Received: from nucl03.anu.edu.au (nucl03.anu.edu.au [150.203.19.120]) by mail.anu.edu.au (8.9.3/8.9.3) with ESMTP id KAA22605; Tue, 4 Dec 2001 10:53:47 +1100 (EST) Received: (from gjl103@localhost) by nucl03.anu.edu.au (8.11.6/8.11.6) id fB3NrGf25767; Tue, 4 Dec 2001 10:53:16 +1100 (EST) (envelope-from gjl103) Date: Tue, 4 Dec 2001 10:53:16 +1100 From: Greg Lane To: freebsd-hackers@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Jul 30 changes to ppp break my Telstra ADSL PPPoE connection Message-ID: <20011204105316.A25712@nucl03.anu.edu.au> Mail-Followup-To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG G'day all, I have a problem with PPPoE over Telstra ADSL (Australia). A full description of the problem can be found in freebsd-questions (see 20011201011107.A9404@nucl03.anu.edu.au dated Nov 30) with the subject: ADSL PPPoE (Telstra Aust.) began to hang between 4.3- and 4.4-RELEASE The short of it is that at some point during my cvsup history certain types of traffic would hang, specifically most web traffic and certain types of ssh (e.g. ls -l of a long directory). This was reminiscent of the MTU/MRU problems at the beginning of the year. I backdated to 4.3-RELEASE which worked and I forgot about it until recently when I decided to change my gateway machine. I have now chased it up in earnest by going back through various dated "cvsup's" and making the world. On July 30th there were some changes to src/usr.sbin/ppp that break ppp and cause this problem. Strangely enough the changes were related to MRU's :-> !! I can reliably make my DSL connection work on three different machines using four different network cards (ed, de, vr, rl) with source dated Jul 30 12:01am, and reliably break it with anything after Jul 31 12:01am. The changes made to ppp on that day were to: src/usr.sbin/ppp/command.c src/usr.sbin/ppp/lpc.c src/usr.sbin/ppp/nat_cmd.c src/usr.sbin/ppp/nat_cmd.h src/usr.sbin/ppp/ppp.8 The most likely problem is lpc.c because 1) it looks the most complicated(!!) and 2) it is supposed to: MFC: Handle peer REQ/NAKs of >1500 byte MRUs when we have no preference The other diffs were small and were to implement two issues: MFC: If the peer REJects our MRU REQ, stop REQing it -- *EVEN* if we're doing PPPoE and the default MRU is therefore too big. MFC: Actually add the ``nat proto'' command I'm afraid my lack of knowledge stops me going on from here. My ppp.conf is below and I start ppp with "ppp -ddial -nat -quiet bigpond" Can anyone see the problem and suggest further detective work I can perform or even better, a fix or workaround? Cheers, Greg P.S. I have cross-posted to questions since the thread started there and hackers since I believe I have narrowed down the problem and it is technical. I hope this is OK. Please confine your reply to whatever list you feel is appropriate, I am subscribed to both. --------------------------------------------------- default: #Only enable logging for troubleshooting #set log CBCP CCP Chat Connect Command IPCP tun Phase Warning Debug LCP sync set device PPPoE:rl0:bigpond set speed sync set mru 1454 set mtu 1454 set ctsrts off enable lqr add default HISADDR set timeout 0 set redial 7 0 set socket /var/run/pppsocket **** ***** #Network Address Translation (NAT) nat enable yes nat log yes #nat same_ports yes nat unregistered_only yes #enable dns # this disabled since the box now runs its own dns bigpond: set authname ******* set authkey ******* ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message