From owner-freebsd-net@FreeBSD.ORG Sat Nov 13 16:00:09 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 349EC16A4CE for ; Sat, 13 Nov 2004 16:00:09 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9447843D58 for ; Sat, 13 Nov 2004 16:00:08 +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 A8FBE1FF92F; Sat, 13 Nov 2004 17:00:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id ABD5A1FF90C; Sat, 13 Nov 2004 17:00:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id C277A15602; Sat, 13 Nov 2004 15:59:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id B771C15389; Sat, 13 Nov 2004 15:59:34 +0000 (UTC) Date: Sat, 13 Nov 2004 15:59:34 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Josh Coombs In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-net@freebsd.org Subject: Re: Netgraph node with inet and ethernet hooks? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2004 16:00:09 -0000 On Sat, 13 Nov 2004, Josh Coombs wrote: > I'm trying to find a way to get PPPoE half-bridging functionality > working with FreeBSD, similar to what Cisco routers and many older ISDN > routers can/could do. Basically, I'm trying to get the ip/subnet > assigned to the ppp link usable on an ethernet interface. I am going to assume the FreeBSD should be the NAS and not the CPE. > So, on the radius side, you have (format is off, I know...) > > user dsluser, prefix=P > fixed-address = 10.0.0.1 > fixed-netmask = 255.255.255.0 what I though that Cisco, etc. are actually doing is: user dsluser, prefix=P fixed-address = 10.0.0.0 fixed-netmask = 255.255.255.0 to take the first IP out of the subnet and assign it to the remote end: Cisco: int Lo1 192.168.199.17 int Vt1 ip unnumbered Loopback1 so the link would look like: NAS: CPE: Cisco <- 192.168.199.17 PtP 10.0.0.1 -> DSL router ^ ^ \-------------/ IPCP handshake And further the cisco adds a route like route add 10.0.0.0/24 10.0.0.1 But I still call that a HACK. Use a transfer IP for the customer (static or out of a pool) for IPCP PtP link and route the /24 to this IP then. user dsluser, prefix=P Framed-IP-Address = "172.16.36.1", Framed-IP-Netmask = "255.255.255.255", Framed-Route = "10.0.0.0/24 172.16.36.1" you need one single extra IP for that but it's a lot "cleaner" and should always work w/o problems. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT