Very Computer

Sent via Deja.com http://www.deja.com/
Before you buy.

If it is a misconfigured user machine, properly someone else use
192.168.1.20 and 192.168.1.30 periodically too.

My solution is use 192.168.2 network instead, if it is possible for you.
If you doing MASQ, you probaraly can choose any network as
long as the network is not occuiped by somebody else.

Dan

Quote:> > I have a home network consisting of a cable modem
> > to the internet, a 10 mbit hub, a linux box with 2
> > nics (Redhat 6.0) doing IP masquerading ("Iowa").
> > On a private 192.168.1.0 network, connected to the
> > hub and using "Iowa" as a gateway (with
> > masquerading), I have three clients: Mac OS 8
> > running Open Transport TCP/IP ("Mac"), a dual-boot
> > Win2000 Beta 3/Linux Redhat 6.0 ("Adam"), and a
> > dual-boot Win98/Linux Redhat 6.0 Dell Laptop
> > ("Jax"). Network connectivity inside and to the
> > internet was working great for six weeks.
> > Suddenly... I'm experiencing IP conflicts on both
> > the Mac OS and Windows platforms, but not on the
> > Linux platforms. "Mac" says there's a conflict
> > with it's IP address 192.169.1.20 with another
> > device on the network (with address 00 00 C0...)
> > then it shuts down it's own network interface
> > (Mac). Windows doesn't tell you right off, but
> > networking doesn't work and looking in the event
> > log, you see a similar error: conflict with it's
> > IP address 192.168.1.30 (note different address)
> > with another device on the network (with address
> > 00 00 C0...) (note same device in conflict). I've
> > identified all the objects' MAC addresses on my
> > network and none of them match the one noted by
> > both Mac and Adam as the object with which they
> > are in conflict. Very strange that two different
> > platforms are complaining of a conflict with the
> > same object (same MAC address), but in conflict
> > with different IP addresses (20 and 30). I feel
> > this is a huge clue. :) I've discovered that if I
> > power cycle the cable modem, the conflict will
> > sometimes clear up, but only for a little while. I
> > suspect the cable modem because it's the only
> > object on my network that manipulating seems to
> > effect the conflict. I've replaced both NICs in
> > Iowa, but it didn't help. I rebuilt Iowa from
> > scratch, reinstalling RedHat 6.0 on a different
> > hard drive, clean install, etc. and it didn't
> > help. I've tried a different hub and it didn't
> > help. The modem's MAC address is printed on the
> > bottom of the device and it doesn't match that
> > address noted by Mac and Adam as the one in
> > conflict, but maybe it's labelled wrong or
> > something. Having changed out most everything
> > else, given that the power cycling the modem
> > effects the conflict (albiet not consistently),
> > and given the fact that all this worked great for
> > six weeks then presto, the conflict, I am tempted
> > to conclude that the cable modem is freaking out.
> > Here's the problem with that theory: networking
> > from my Linux clients works perfectly! Even from
> > Adam (dual boot, doesn't work from Windows, works
> > from Linux, proving the NIC works, etc.). I've
> > scoured Usenet, RedHat, IP Masq for Linux site,
> > and I haven't found an answer yet. I post this out
> > of desperation. Any ideas out there?

> > Sent via Deja.com http://www.deja.com/
> > Before you buy.

I wonder how many firewalls a user could slip through assuming
there are some users out there with an internal network of private IPs and
they have their firewall setup to accept packets from systems in the

private IP addresses to be used openly, I would put an ipchain  DENY rule
as the first rule on the input chain for the network interface that is
connected to the cable modem.

Tony