Date: Thu, 15 Nov 2001 16:07:23 -0600 From: jacks@sage-american.com To: "Andrew C. Hornback" <achornback@worldnet.att.net>, "Anthony Atkielski" <anthony@atkielski.com>, <freebsd-questions@FreeBSD.ORG> Subject: RE: DSL PPPoE with 2 NICs Message-ID: <3.0.5.32.20011115160723.00ffe910@mail.sage-american.com> In-Reply-To: <3.0.5.32.20011115075925.00fbf8a8@mail.sage-american.com> References: <005401c16db7$6491bd00$6600000a@ach.domain> <003001c16db5$6c953330$0a00000a@atkielski.com>
next in thread | previous in thread | raw e-mail | index | archive | help
...well, bad day at black rock! I never got a chance yet to test out the PPPoE setup because once I installed the second NIC, turned on the DSL modem and booted up, it messed up the LAN settings and the FreeBSD box lost its connection with the network. It changed the original network NIC device from rl0 to rl1 and the new NIC for the DSL grabbed the NW device's rl0....and it insists on taking that spot. No doubt if I were doing a fresh install, the network would be setup right, using the rl1 instead of the rl0 when it was just a workstation. Sooooo, I went in and changed the rc.conf to point the DSL host to the new rl1, and restarted...NADA. The box still couldn't see the LAN. What config files am I missing on this? I'm sure its simpler than this. I'm blushing at those who do this in 10-15 mins... but, it really is a matter of level of SKILL... it's my first time. Additional tips welcomed... I'd rather not re-install the OS just to make it see the Network through the new NIC. ....thanks! At 07:59 AM 11.15.2001 -0600, jacks@sage-american.com wrote: >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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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 <full-duplex>) >>> > status: active >>> > lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 >>> > ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 >>> > sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552 >>> > faith0: flags=8000<MULTICAST> mtu 1500 >>> > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> 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 > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20011115160723.00ffe910>