From owner-freebsd-questions Fri Aug 4 2:53:27 2000 Delivered-To: freebsd-questions@freebsd.org Received: from hotmail.com (law2-oe3.hotmail.com [216.32.180.107]) by hub.freebsd.org (Postfix) with ESMTP id E37F337B5C5 for ; Fri, 4 Aug 2000 02:53:21 -0700 (PDT) (envelope-from joka83@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 4 Aug 2000 02:53:21 -0700 X-Originating-IP: [4.33.224.66] Reply-To: "Samuel Lin" From: "Samuel Lin" To: References: <809430619.20000802115646@snet.net> Subject: Re: PPPoE issues; SOLUTION Date: Fri, 4 Aug 2000 02:52:28 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Message-ID: X-OriginalArrivalTime: 04 Aug 2000 09:53:21.0481 (UTC) FILETIME=[D2CA2390:01BFFDF9] Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG as a reply to myself, and to help out the one individual who actually did reply to my post ~ it turns out that FreeBSD v4.1-RELEASE works with my PPPoE connection perfectly ..it would seem that 3.4 contains a programming bug = for the more technically inclined, the PPPoE implementation in FreeBSD 3.4 does not seem to properly recognize the PADR packet sent by the access concentrator from the server end of the discovery stage; client-side PPPoE does transmit the initial PADI packet, and the remote server does send a proper PADR reply packet ~ but 3.4 PPPoE does not recognize it as such, and ignores the reply, thereby bringing PPPoE initialization to a grinding halt .i would suggest to mhf to upgrade to version 4.1-RELEASE; if that does not work, i am available at this email ~ i know what you are going through and i would be more than happy to help ----- Original Message ----- From: "mhf" To: "Samuel Lin" Cc: Sent: Wednesday, August 02, 2000 08:56 Subject: Re: PPPoE issues: not connecting to remote peer on Earthlink ADSL connection > Yes Yes!! Someone please help this fella, and in the process help me > too. I have posted a few questions along the same lines, but have > only received one response. There's gotta be a few gurus out there > who can help us get through the PPPoE part of the FreeBSD learning > curve. > > I am currently using FreeBSD 4.0 My ADSL service provider is > Southern New England Telephone (SNET)-- now a subsidiary of SBC just > like PacBell. > > I am writing from work, so I cannot produce my ppp.conf and rc.conf > for this post; however, I would be very greatly to begin dialogue with > anyone who can help Sam and I get ADSL working. > > I was thinking of buying the Linksys ADSL PPPoE Router that everyone > is raving about, but I don't think that will help until I get FreeBSD > to make my Kingston KNE 110 TX ethernet card pass packets back and > forth. > > Thank you for your time. I hope to hear from some successful ADSL > users. > > > -- > Best regards, > mhf mailto:michael.flug@snet.net > > > Wednesday, August 02, 2000, 7:19:49 AM, you wrote: > > SL> I am running a FreeBSD 3.4-Release #3 test system on which I am attempting > SL> to configure PPPoE, to no successful avail. I have followed the procedures > SL> from the handbook (http://www2.freebsd.org/handbook/pppoe.html), from > SL> simpatico (http://www.sympaticousers.org/faq/freebsd_howto.htm), and from > SL> node.to (http://www2.freebsd.org/handbook/pppoe.html), each in its own > SL> distinct and relative measure; nevertheless, none have worked. If anything, > SL> the latter two return a "/kernel: no such service" (??) error on a dial > SL> attempt > SL> while the first at least loads up the PPP process and attempts to dial > SL> (without any readily apparent error, barring the detail of PPPoE not > SL> actually connecting!). > > >>From what I can understand, PPPoE seems to wait for a carrier detect, and > SL> upon not detecting one, it disconnects. I have attempted setting widely > SL> varying values for "cd" from "off" to "5" to the noted "60" ~ none work. I > SL> have even gone so far as to "borrow" a ppp.conf from a friend (on PacBell > SL> ADSL), replace the requisite information (authname & authkey), and still not > SL> succeed in connecting. The hardware (NIC & ADSL modem) is in perfect shape > SL> ~ both work from this NT server without any errors. I am not sure if it is > SL> worth noting that dialup PPP works just fine ~ however, the particular > SL> FreeBSD workstation is (or, rather, should be) connected to an Earthlink > SL> ADSL account via a Fujitsu ADSL modem ~ I am not sure if the problem is one > SL> dealing especially with Earthlink or the specific modem (as such, any > SL> feedback from any Earthlink xDSL/FreeBSD users would be quite useful). I > SL> would very much appreciate *any* help at all, as this is becoming > SL> mind-numbingly frustrating. I have appended some technical information > SL> below in the hopes that it will elucidate the situation better than any > SL> rambling summary I can give. > SL> _________________________________________________ > SL> Of the primary directions from handbook, I have compiled "options NETGRAPH" > SL> into the kernel; either "options NETGRAPH_PPPOE" or "options NETGRAPH_SOCKET > SL> " return the aforementioned error of "/kernel: no such service" on a dial > SL> attempt ~ as such, I have given up on the latter two and compiled only the > SL> first. > > SL> The /etc/ppp/ppp.conf file is configured as follows: > SL> default: > SL> set log Connect Physical async cbcp hdlc id0 ipcp lcp lqm sync tcp/ip timer > SL> Debug Phase Chat LCP IPCP CCP tun command > SL> set speed 115200 > SL> set timeout 120 > SL> set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > SL> add default HISADDR > SL> enable dns > > SL> adsl: > SL> set device PPPoE:xl0 > SL> set authname username #authname & authkey values modified for privacy > SL> set authkey password > SL> set speed sync > SL> set cd 60 # a last ditch effort; neither set cd 5 nor set cd off produced > SL> satisfactory results > > SL> An excerpt from /var/log/ppp.log of parts which I thought to be relevant > SL> (though that doesnt mean much, even in my opinion); due to the fact that I > SL> was (and am) getting quite frustrated, ppp was to log virtually all aspects > SL> of itself, but for the sake of email, I have attempted to trim it down (ever > SL> so slightly): > SL> ppp[263]: tun0: Phase: bundle: Establish > SL> ppp[263]: tun0: Phase: deflink: closed -> opening > SL> ppp[263]: tun0: Debug: List of netgraph node ``xl0:'' (id 1) hooks: > SL> ppp[263]: tun0: Debug: Creating PPPoE netgraph node [1]:orphans -> ethernet > SL> ppp[263]: tun0: Debug: Connecting netgraph socket .:tun0 -> xl0:orphans:tun0 > SL> ppp[263]: tun0: Debug: Sending PPPOE_CONNECT to .:tun0 > SL> ppp[263]: tun0: Warning: deflink: Reducing MRU to 1492 > SL> ppp[263]: tun0: Timer: timer_Start: Inserting physical throughput > SL> timer[0x80b1048] > SL> ppp[263]: tun0: Phase: deflink: Connected! > SL> ppp[263]: tun0: Phase: deflink: opening -> dial > SL> ppp[263]: tun0: Chat: deflink: Dial attempt 1 of 1 > SL> ppp[263]: tun0: Phase: deflink: dial -> carrier > SL> <> > SL> ppp[263]: tun0: Debug: Waiting for carrier > SL> ppp[263]: tun0: Timer: prompt /dev/tty: fdset(r) 0 > SL> ppp[263]: tun0: Timer: Select returns -1 > SL> ppp[263]: tun0: Timer: ---- Begin of Timer Service List--- > SL> ppp[263]: tun0: Timer: physical throughput > SL> timer[0x80b1048]: freq = 1.00s, next = 0.00s, state = running > SL> ppp[263]: tun0: Timer: ---- End of Timer Service List --- > SL> ppp[263]: tun0: Timer: timer_Start: Inserting physical throughput > SL> timer[0x80b1048] > SL> <> > SL> ppp[263]: tun0: Phase: deflink: Disconnected! > SL> ppp[263]: tun0: Phase: deflink: carrier -> hangup > SL> ppp[263]: tun0: Debug: deflink: Close > SL> ppp[263]: tun0: Phase: deflink: Connect time: 11 secs: 0 octets in, 0 octets > SL> out > SL> ppp[263]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Mon 2000 > SL> ppp[263]: tun0: Phase: deflink: hangup -> closed > > > SL> To Unsubscribe: send mail to majordomo@FreeBSD.org > SL> with "unsubscribe freebsd-questions" in the body of the message > > > > > -- > Best regards, > mhf mailto:michael.flug@snet.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message