From owner-freebsd-net Mon Feb 7 13: 7:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-12.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.140]) by builder.freebsd.org (Postfix) with ESMTP id 66082408E for ; Mon, 7 Feb 2000 13:07:21 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA04724; Mon, 7 Feb 2000 21:05:06 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA03261; Mon, 7 Feb 2000 21:05:12 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002072105.VAA03261@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dermot McNally Cc: Brian Somers , freebsd-net@freebsd.org, Julian Elischer Subject: Re: PPPoE connection almost working In-Reply-To: Message from Dermot McNally of "Mon, 07 Feb 2000 00:16:12 +0100." <4.2.0.58.20000207000333.00b04c70@tim> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Feb 2000 21:05:12 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > At 00:53 06.02.2000 +0000, Brian Somers wrote: > > > > > dsl: > > > set device PPPoE:ed0 > > > set mru 1492 > > > set mtu 1942 > > > >Spot the deliberate mistake... hence the warning in the log :*] > > Yup, I spotted that too afterwards. Fixing it cured the warning, as you'd > expect, but had otherwise no effect. > > > > 23:14:41.096562 0:0:e8:4f:be:4b Broadcast 8863 32: PPPoE PADI v1, type 1, > > > sess 0 len 12 [Service-Name] [Host-Uniq 004888c0] > > > 23:14:41.141794 0:d0:c0:f9:b6:23 0:0:e8:4f:be:4b 8863 67: PPPoE PADO v1, > > > type 1, sess 0 len 47 [Service-Name] [Host-Uniq 004888c0] [AC-Name > > > MUNC12-nrp2] [AC-Cookie 372992470f60c417cd68e17dcde89eb4] > > > >This is the sort of thing I get when testing locally - the -current > >tcpdump looks a bit different as it's been upgraded and the tcpdump > >people added pppoe support (they mustn't have liked the look of my > >output :-): > > Some people are just fussy - your output beats what was there before. > > > >So as you can see, the local side *should* be sending a PADR. > > That's what I would have thought. One difference between us is that the > PADO in your case specifies a service name, whereas mine doesn't (nor does > my PADI, because I don't know what name to use...). > > >I don't really know why the PPPoE node isn't responding to the PADO. > >it looks good from here. > > > >Are there any odd looking kernel messages on your console or in > >/var/log/messages ? > > [checks] Nope. > > Right, I think I'll do the following: > > * Assume that MAC Address affinity isn't the problem - if it was, I > probably wouldn't get a PADO, right? I would think so. > * Update the box to current. I wanted to do it anyway, and it'll bring my > configuration a little closer to yours. I believe netgraph is just about the same in both. > * If I really have to, I'll try packet-sniffing a working connection from > Windows. This will be a pain, because the "modem" Telekom supplies is > intended to connect direct to a NIC, so to connect it correctly to a hub > requires a crossed over cable that I don't currently have. Still, if we > don't get anywhere by other means, I'll try this route. It will at least > tell me if the official software specifies a service name in its PADI. You could also try bringing up your own pppoed. It's pretty straight forward - just add a few variables to /etc/rc.conf and take a look at the pppoe profile in /usr/share/examples/ppp/ppp.conf.sample. > Thanks for the ideas (not to mention the software), > Dermot I've cc'd a better email address for Julian - perhaps he's got some suggestions :*] -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message