It is very simple to set up. Below is my config info
     
     Paranoid.snurgle.org <- main linux box hooked up via ADSL
        \-192.168.1.1 <- Internal IP
         \- 209.226.67.216 Assigned ip via DHCP
     
     ETH0 = Attached to cable modem
     ETH1 = Attached to internal network
     
     All I did was, use yast to run the dhclient on eth0 9Altho the client 
     they give out it crap, I had to compile my own, 1.3.16 I belever the 
     version I use is), I then bring up ETH1, assign it's ip, and ipchains 
     to setup ip masq, and viola it works. I can go into more details if 
     you want. But it was quite simple.


______________________________ Reply Separator
_________________________________
Subject: Re: [SuSE Linux] YAST masquerade setting
Author:  "Bob Easton" [SMTP:[EMAIL PROTECTED]] at BCEEXCH
Date:    3/31/99 10:56 AM


On 1 Apr 99, at 16:26, Lenz Grimmer wrote:
     
>
> Hi,
>
> On Thu, 1 Apr 1999, Paul Hostetler wrote: 
>
> > On Thu, 1 Apr 1999, Lenz Grimmer wrote:
> > > Have a look at the package "firewall". It will add the required
variables 
> > > to /etc/rc.config to set up firewalling/masquerading.
> >
> > Will it permit DHCP on one NIC and a static IP (192.168.0.x) on
> > another? I get a DHCP address from Road Runner.  I don't recall seeing 
> > an answer to this question.
>
> No, this does not work with the current DHCP client configuration - sorry!

>
     
LenZ,
     
What is the status of this development?  [Not nagging here but I 
*think* this works on RedHat, but I could be wrong.] I too wish 
to use a SuSE box as my gateway between RoadRunner and my local 
network. Is there *any* configuration that will work?  I thought 
I read something about having two dissimilar NICs (and drivers) 
made things work.  I'm about to buy a VA Research system and may 
have to resort to RedHat (e-gads) if there is no way around 
this!  The RR system requires DHCP - but how about if I run DHCP 
on my local network as well?  Will SuSE run a DHCP client on one 
NIC and a DHCP server on another? That is to say, is the problem 
mainly with having a *static IP* on one NIC while running DHCP 
on the other?  Can we expect a fix for this soon?
     
Thanks in advance,
Bob
     
--
To get out of this list, please send email to [EMAIL PROTECTED] with 
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the 
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html

Reply via email to