On Fri, 25 Jun 1999, Beacham Tim P wrote:
> This could be setup with one ethernet card using virtual IP addressing on
> eth0, I think this is covered in the how-to. It works great but I would
> still use a second card if this will be the gateway for a larger network.
> The prices are so minimal now - they are almost disposable.
AHHH, never ever ever. let me stress this more NEVER.
1) You double traffic onto your lan, if your on dsl you will be the only
one effected so then its upto you, however if your on a cable modem
you are apt to wake up in the middle of the night with the burly biker
down the street pounding on your door cause your interfering with his
daily sex addiction
2) The provider will most likely cut your access upon discovering a settup
like this (read your service contract)
3) Very insecure, very very. It makes spoof attacks all that much easier.
4) Cause if your one of the four people on my @home junction, and i find
you ..
Now that out of the way, masq setup is pretty painless afew extra lines to
your firewall and your off and running. The cable modem I have allows 8
ip's. most ten port hubs two are used in/for uplink or crossover mode,
however My isp only allows three ip's per household so i put my cablemodem
into a 5port hub useing the uplink port (so i didn't have to hunt down a
sales person and have them gawk at me when i asked for a crossover cable)
useing a standard cat5. from the 5port hub it branches to a windows pc
in the living room for family use, and branches to my linuxrouters
eth0, eth1 on the router is a 100mbs card hooked into a 10port hub,
so i can stick another 9 pc's behind the linux machine before i require
anymore hardware. not to mention 2pci and 3isa slots left for further
expansion, more than enough to handle corprate traffic levels, on a bubble
gum budget..
> Beach
>
> > -----Original Message-----
> > From: Patrick Putteman [SMTP:[EMAIL PROTECTED]]
> >
> > I think the main point you are missing is that in case of DSL or Cable
> > Modems, you need 2 network cards. One connected to the DSL or Cable Modem,
> > and thus to the internet, and to provide the connection to the lan.
> >
> > Patrick
> >
> > ----- Original Message -----
> > From: W. Sanford May <[EMAIL PROTECTED]>
> > To: Expert Linux Mandrake <[EMAIL PROTECTED]>
> > Sent: Friday, June 25, 1999 9:57 PM
> > Subject: [expert] IPMasq Confusion
> >
> >
> > > I'm planning to set up ipmasq to share my static DSL connection with Win
> > and
> > > Macintosh machines on our private tcp/ip network. I've read the
> > mini-how-to
> > > for ipmasq and I've become a bit confused about the theory behind
> > > configuring ipmasq. Notably, the how-two seems to indicate that you set
> > up
> > > the Linux box with a private IP address that will also be used at the
> > > gateway address for the other machines. The how-to mentions
> > 192.168.1.1.
> > > This is fine, but where do I setup the Linux box/local network gateway
> > > machine with the static IP provided by the DSL service provider? I also
> > > assume I should use the assigned default gateway from the ISP as the
> > default
> > > gateway on the Linux/local network gateway. Correct?
> > >
> > > It seems to me that if the Linux gateway machine is not configured with
> > the
> > > static IP from the ISP, the other machines on the network can point to
> > it
> > as
> > > the gateway, but traffic will not be properly routed to and from the
> > > Internet. Is there someway to configure with the private IP address for
> > the
> > > internal gateway and then use the static ISP-supplied IP address for
> > > purposed of routing data to the Internet?
> > >
> > > Excuse me if I'm missing something obvious or not thinking all that
> > sharply,
> > > but any assistance would be appreciated.
> > >
> > > thanks...
> > >
> > > sanford
> > >
>
