From owner-freebsd-current@FreeBSD.ORG Sun Aug 1 14:07:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5E5216A4CE; Sun, 1 Aug 2004 14:07:47 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2888C43D46; Sun, 1 Aug 2004 14:07:47 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 4B2931FFDD4; Sun, 1 Aug 2004 16:07:45 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 435CD1FF91D; Sun, 1 Aug 2004 16:07:43 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 7FA7615384; Sun, 1 Aug 2004 14:07:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 747E715329; Sun, 1 Aug 2004 14:07:36 +0000 (UTC) Date: Sun, 1 Aug 2004 14:07:36 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Maxim Maximov In-Reply-To: <410CF1A8.3050605@mcsi.pp.ru> Message-ID: References: <20040730091525.U484@pukruppa.net> <20040731213854.GB38076@cell.sick.ru> <410CB1E4.2030103@mcsi.pp.ru> <20040801093316.GA40608@cell.sick.ru> <410CBBA9.1080302@mcsi.pp.ru> <20040801095558.GA40732@cell.sick.ru> <410CF1A8.3050605@mcsi.pp.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: Gleb Smirnoff cc: freebsd-current@freebsd.org Subject: Re: PPP(was: oE) problems with latest -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2004 14:07:47 -0000 On Sun, 1 Aug 2004, Maxim Maximov wrote: > > this is a PPP only problem. I haven't read all the logs from all your > > mails but if someone could send me a trace file (written with tcpdump > > -w) it would make it a lot easier to check what's going wrong in LCP > > negotiation. > > 'tcpdump -w' output attached. > > > > > Just to make sure. This is NOT a PPPoE problem. PPPoE seems to work > > pretty fine, else you wouldn't be able to start PPP LCP negotiation. > > > > Why rp-pppoe works then? PPP is still the same. of course; the problem had not been visible from the ppp logs. It looked like everything goes fine apart that the peer doesn't ACK your CONREQ and thus you go into another negotiation loop. The problem actually is that the peer will never see your CONFREQ because it goes like this: .. 3c 13 Ethertype (NONSTANDARD, 3Com) 11 00 38 dd 00 1a PPPoE c0 21 PPP LCP but it should go like this: 88 64 Ethertype PPPoE 11 00 3e dd 00 15 PPPoE c0 21 PPP LCP unles you set pppoe 3Com or changed the sysctl (I think there still is one). So it seems that either ether.c (command.c, physical.c) change or the ng_pppoe still have problems selecting the correct type and default to standard. I am checking the sources to find the place if glebius isn't faster ;-) Could you please mail to output of sysctl net.graph.nonstandard_pppoe -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT