Date: Sat, 13 Nov 1999 23:27:51 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Josh Tiefenbach <josh@zipperup.org> Cc: freebsd-net@FreeBSD.ORG Subject: Re: Problems using ppp(8) and PPPoE Message-ID: <Pine.BSF.4.10.9911132326190.21751-100000@current1.whistle.com> In-Reply-To: <Pine.BSF.4.10.9911122359570.19136-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Any news? On Sat, 13 Nov 1999, Julian Elischer wrote: > > > On Fri, 12 Nov 1999, Julian Elischer wrote: > > > > > > > On Fri, 12 Nov 1999, Josh Tiefenbach wrote: > > > > > > I think I may have an idea. You are sending a Host-Uniq tag in the PADI. I > > > > have this funny feeling that my ISP doesnt like that. I'm in the middle of > > > > running some tests to see what happens when I change pppoe_start() to not > > > > insert that tag in the PADI. > > > > > > > > (Yes. I know that this might break some things, but I want to see if my ISP > > > > actually emits a PADO in response to the modified PADI) > > > > > > Following up to myself, it looks like I was right on both counts. In removing > > > the Host-Uniq tag, I see the following on the wire: > > > > > > cerebus:~# tcpdump -nev -s 256 ether proto 0x8863 or ether proto 0x8864 > > > tcpdump: listening on de0 > > > 23:23:18.010000 0:c0:f0:22:35:e1 ff:ff:ff:ff:ff:ff 8863 24: > > > 1109 0000 0004 0101 0000 > > > 23:23:18.728783 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8863 61: > > > 1107 0000 0029 0101 0000 0102 001d 3133 > > > 3034 3130 3439 3931 3833 3632 2d73 6d73 > > > 322d 746f 726f 6e74 6f36 3301 0100 00 > > This is the same response that the test system gave except the test > system said "montreal02" instead of "toronto63". So it SHOULD work with > the HOST-UNIQUE tag, especially if they are teh same router type. > the SPEC says it "MUST" support and return that tag.. > > Maybe the system was just down at the time you first tested.. > did you try the old ng_pppoe again? The test system in Montreal > was down for hours (in some cases days) at a time. > > if you compile the base netgraph (and the socket type) into the system, > then you can use kldload and kldunload to load and unload the pppoe node > (but remove the 'dependency' line fom the pppoe module's makefile. it > triggers a bug in the module code) > > > > > 23:23:19.005733 0:c0:f0:22:35:e1 ff:ff:ff:ff:ff:ff 8863 24: > > > 1109 0000 0004 0101 0000 > > > 23:23:19.728640 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8863 61: > > > 1107 0000 0029 0101 0000 0102 001d 3133 > > > 3034 3130 3439 3931 3833 3632 2d73 6d73 > > > 322d 746f 726f 6e74 6f36 3301 0100 00 > > > > > > As you can see, I can now elicit a PADO from Sympatico. Unfortunately, it > > > looks like removing the Host-Uniq tag breaks all that code which uses the > > > Host-Uniq identifier to match which flow belongs to which node. > > > > > > Comments? > > Get an ISP that follows the spec? > > > > complain loudly? > > > > since you only have one flow, you could hide the host unique in a global > > and pretend you found it in the PADO packet. .... > > > > If you add it back (and don't touch the windows machine, does it fail > > again?) > > > > > > > > > > josh > > > > > > -- > > > "To succeed in the world, it is not enough to be stupid, you must also be > > > well-mannered" -- Voltaire > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9911132326190.21751-100000>