From owner-freebsd-questions Thu Nov 15 6: 7: 7 2001 Delivered-To: freebsd-questions@freebsd.org Received: from atkielski.com (atkielski.com [161.58.232.69]) by hub.freebsd.org (Postfix) with ESMTP id C6D5B37B41A for ; Thu, 15 Nov 2001 06:06:59 -0800 (PST) Received: from contactdish (ASt-Lambert-101-2-1-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.11.6) id fAFE6wW72677; Thu, 15 Nov 2001 15:06:58 +0100 (CET) Message-ID: <009d01c16dde$ca66b320$0a00000a@atkielski.com> From: "Anthony Atkielski" To: , References: <003001c16db5$6c953330$0a00000a@atkielski.com> <3.0.5.32.20011115075925.00fbf8a8@mail.sage-american.com> Subject: Re: DSL PPPoE with 2 NICs Date: Thu, 15 Nov 2001 15:06:52 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, if you get it to work, please explain the procedure to me, as I'd still be interested in knowing how it is done, even though I chose to go the easy route (no pun intended) this time. ----- Original Message ----- From: To: "Andrew C. Hornback" ; "Anthony Atkielski" ; Sent: Thursday, November 15, 2001 14:59 Subject: RE: DSL PPPoE with 2 NICs > Many thanks for all that responded to this request for suggestions. I am > more certain about some of the muddy areas now. As I said, the ISDN works > already on the Win2K gateway, so if I just need something to work, I can > always fall back on that.... > > I've noted over the past months on this list that several have set up the > DSL and my preference is to utilize the power for this function that comes > rather natural with FreeBSD...realizing there are some rough spots to > configure. The router approach might be easier, but it is essential I learn > the BSD approach for the long haul. > > I already know that the DSL line is good and works (somewhat) with the > Win2K, so that is not a problem. However, Win2K is not handling the packets > right apparently (can't reply to emails or FTP upload on the stations > behind the gateway... gateway Win2K works okay 100%). Even so, I'd rather > migrate this function to FreeBSD for the long haul where I can add the > firewall after getting the connection working. > > Again, as usual everyone has been most helpful & I appreciate it. Just > cvsupped a fresh 4.4-STABLE, 2nd NIC in hand, live DSL modem, have my head > under the "hood" and ready to dive in....!! > > At 04:24 AM 11.15.2001 -0500, Andrew C. Hornback wrote: > >Note: Reply text moved to bottom to preserve context. > > > >> -----Original Message----- > >> From: owner-freebsd-questions@FreeBSD.ORG > >> [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Anthony > >> Atkielski > >> Sent: Thursday, November 15, 2001 4:11 AM > >> To: freebsd-questions@FreeBSD.ORG; jacks@sage-american.com > >> Subject: Re: DSL PPPoE with 2 NICs > >> > >> > We have a small LAN about to be set up on a DSL connection which is > >> > activated. The LAN is currently sharing an ISDN Internet connection (not > >> > used for incoming remotes). The gateway machine (192.168.0.1) is running > >> > Win2K. There are several Win2K stations on the LAN and a couple > >> of FreeBSDs > >> > running 4.4, on manually assigned. The DSL is an external modem > >> via PPPoE. > >> > The LAN is connected via Hub. Each box has a RealTek 8139 on device rl0. > >> > > >> > We want to install the DSL in one of the FreeBSD boxes > >> (192.168.0.202) to > >> > use with the > >> > DSL (and change to the gateway in place of the Win2K). here's how the > >> > ifconfig -a > >> > looks now: > >> > > >> > ********************************************************************* > >> > rl0: flags=8843 mtu 1500 > >> > inet6 fe80::240:33ff:fe57:92dd%rl0 prefixlen 64 scopeid 0x1 > >> > inet 192.168.0.202 netmask 0xffffff00 broadcast 192.168.0.255 > >> > ether 00:40:33:57:92:dd > >> > media: Ethernet autoselect (100baseTX ) > >> > status: active > >> > lp0: flags=8810 mtu 1500 > >> > ppp0: flags=8010 mtu 1500 > >> > sl0: flags=c010 mtu 552 > >> > faith0: flags=8000 mtu 1500 > >> > lo0: flags=8049 mtu 16384 > >> > inet6 ::1 prefixlen 128 > >> > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > >> > inet 127.0.0.1 netmask 0xff000000 > >> > ********************************************************************* > >> > > >> > A second NIC card (D-Link DFE-530TX+) will be added for the DSL > >> modem and > >> > it loads as > >> > device r11 (without modem connected yet). > >> > > >> > The "tun" devices are made and ready.... and 4.4 loads netgraph > >> support I > >> > believe without need to build into the kernel. > >> > > >> > QUESTION: > >> > Does anyone listening have a similar setup as planned > >> above...DSL PPP over > >> > PPPoE with two NICs (1 for the modem and 1 for the LAN) and if so, may I > >> > see your ppp.conf file... and what else should I worry about? > >> > > >> > I have read all of the many papers/guides (including Renaud Waldura's > >> > paper). Any added tips would be VERY welcome as I really want to use BSD > >> > rather than Win2K..... many t > >> > >> Instead of a second NIC, add a DSL router (a router that is > >> designed to have a > >> DSL modem on one side and your LAN on the other) to your LAN and > >> use it as your > >> gateway. Only about $100, and the money you spend on it will > >> cost much less > >> than the time you'd spend configuring one of your machines to act > >> as a gateway. > >> More secure, too (there are far fewer potential holes in a simple > >> router than in > >> a full OS running as a gateway). I tinkered with FreeBSD for a > >> while trying to > >> set it up as a gateway, and finally got tired of it and just > >> bought the router, > >> which works fine out of the box, with virtually no setup. > > > > $100 for a router that may or may not ever have security updates or $20 for > >a NIC in a machine that you've already got and are ready to configure and > >use as a gateway. > > > > Jack, while I personally haven't put together a configuration like you're > >talking about, I'm pretty sure that it's not that hard to do. After all, > >having a FreeBSD machine do dial on demand PPP as a network gateway to a > >dial-up ISP seems like it would be harder than what you're talking about, > >but it's actually a simple thing to do. Having a machine send network > >packets between real interfaces sounds a lot easier. > > > > While you're setting it up, I'd recommend against running any sort of > >firewall or filtering software. You can add those in once you've gotten the > >link established and running properly. > > > > And while I'm at it, not to harp on things here, but Anthony, you've > >previously admitted that you're new at FreeBSD. Your dissatisfaction at not > >being able to configure your system to fit your application may have > >something to do with your relative inexperience with the system itself. > > > >--- Andy > > > > > > > > Best regards, > Jack L. Stone, > Server Admin > > Sage-American > http://www.sage-american.com > jacks@sage-american.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message