Bret,

Sounds like you've almost got it licked.  If PPPoE doesn't work for you
(unlikely), and if you can set your modem up as a router where it acts as
a firewall and logs on for you, you can give your eth0 (or whatever card
points to the router/modem the address of 10.0.0.2 even if the router is
running DHCP (assuming it's set itself up with the default 10.0.0.1).
Then set your kernel routing table up something like:

$ route -n
Kernel IP routing table
Destination  Gateway       Genmask        Flags Metric Ref  Use Iface
192.168.1.0  192.168.1.10  255.255.255.0  UG    0      0      0 eth1
127.0.0.0    0.0.0.0       255.0.0.0      U     0      0      0 lo
0.0.0.0      10.0.0.1      0.0.0.0        UG    1      0      0 eth0

Make sure on the line that has the gateway set to 10.0.0.1 that you have
Metric set to 1.  This should get you up and running.  The bottom line is
the one that gets me to the 'net.  The top access my LAN.

Glen



On Tue, 29 Aug 2000, Bret Hughes wrote:

>Dusty deBoer wrote:
>
>> This probably won't help much (any?) but this machine I am running is
>> hooked up via DSL to Southwestern Bell. I didn't order a static ip
>> address; I get a DHCP address every time I log in with the DSL. Here's
>> what I did to set up - maybe somebody can enlighten me as to what is
>> happening behind the scenes.
>>
>> 1.) I have a NIC in my Win machine. Hook the DSL modem directly up to that
>> NIC, log in using SWBells provided software, and get a user name and
>> password.
>> 2.) Decide that I would like to route through my linux machine, so I
>> install the (Kingston?) NIC that came from SW Bell into my Linux machine,
>> in addition to the NIC (Netgear) that was already there. Now, the Netgear
>> NIC hooks directly up to the Win nic via a crossover cable.
>> 3.) Downloaded PPPoE software from www.roaringpenguin.com/pppoe/, since
>> the Win software said that it was doing ppp over ethernet. Hooked the DSL
>> modem up directly to the new (eth1) NIC on linux, installed and set up the
>> PPPoE stuff from roaring penguin.
>> 4.) Run adsl-start, and Wow! Fast internet connection. Made some routing
>> changes so that Win can get to the net.
>>
>> So that's my story - again, it was really easy. (So if anybody has any
>> idea what happened behind the scenes, I would appreciate comments.)
>>
>> -Dusty deBoer
>
>Thanks for the quick responses all.  Tech support did indeed confirm that SBC
>uses pppoe and I downloaded the roaring penguin rpm, installed it and am at
>least getting responses back from the pppoe server.  Next is how to get the
>userid and password.  Someone in my family managed to misplace the damn
>instructions that came with the kit ( Might have been me but I suspect a
>frensy of cleaning that occurred last week)  This does not happen too much
>with a three year old and a two month old :)
>
>I appreciate your help and the next call is to tech support again.  BTW it
>will be interesting to see if I can do this without the windows step.
>
>Bret
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
>



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to