Spurios IP address conflicts.

Blackstar is a linux box, ip .35 (I'll not type the first
three octets in this.)  It has a modem and runs pppd.
Three users each have a pppd account.  They have ip addresses of .38 .44 and .75.

When someone is dialing into the box, another machine on
my net will crash, or have network problems.  If rebooted,
I will typically get a message such as:

A machine with hardware address of 00:00:0C:FB:B2:C0 claims
to be .222 Net interface disabled.

Where .222 is the address of the machine in question.

Ifconfig and arp don't show any sign of 222.  I can't ping
222 when this is going on.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Is there any ethernet card with same MAC address ?

Could one of your dialin clients be incorrectly configured, and be requesting the same IP address as another machine on the LAN?
I have three questions:

1) Does .222 has its root file system on Blackstar??

2) Have any of these machines a gateway??

3) Which deamon are you using as dialin provider, parameters??

Give me a 'netstat -nr' when a ppp account is active
and a 'ps -ax' when blackstar is up 'n running.
Why Diversity in Tech Matters

Kesha Williams, certified professional and software developer, explores the imbalance of diversity in the world of technology -- especially when it comes to hiring women. She showcases ways she's making a difference through the Colors of STEM program.

sherwoodAuthor Commented:
Regarding questions:
>>Is there any ethernet card with same MAC address ?
      No.  Our switching hub lists all the MAC addresses
that it is caching.  This MAC address is not on more than
the one segment.  In addition, MAC addresses are suppose to
be unique.  

>> Could one of your dialin clients be incorrectly configured, and be requesting the same IP address as another machine on the LAN?
      That was my first thought.  1. As far as I can tell
from the config files, Blackstar won't negotiate the IP.
Each dialin account has a unique IP, and that's it.  2. This is  borne out by running ifconfig when the connection occurs.  
Ifconfig shows that the pppd interface is up, and shows the
proper ip at the other end of it.  3.  If the machine at the
other end was actually 222, then a ping would normally elicit
a response.  
        Comment from margin...
>>I have three questions:

>>  1) Does .222 has its root file system on Blackstar??
      No. .222 is a win95 box.  And it won't always be .222
It sometimes will be .220 or .112  I think the Blackstar is
claiming to forward packets for these addresses.  

>>  2) Have any of these machines a gateway??
      The network as a whole has a gateway through .1.
In fact this is the primary reason that people dial in to
Blackstar is to get access to the net.

>>  3) Which deamon are you using as dialin provider, parameters??

>>      Clarify:  On the server or on the client.
      On the server we're running pppd that comes with linux.
There are a large and icky number of config files.  email
me (sherwood@math.ualberta.ca) if you want specifics.

                           Give me a 'netstat -nr' when a ppp account is active
                           and a 'ps -ax' when blackstar is up 'n running.
A 'netstat -n' had help me to pick out this possibility:

All machines in your network has dynamic IP-addresses (included the dial-in machines). All this dynamic IP-addresses are whithin the same sub-network.
The machine which stands for the dynamic IP-adresses are blackstar and at least one other machine.

The pppd on blackstar has the option 'defaultroute' which means that the dial-in machine will be reached through a gateway on the default route.

This means that the rest of the network will be disabled when the default route on blackstar points to the dial-in machine (it had worked if the dial-in machine and the rest of the network were on different sub-nets...).
When another machine is trying to 'contact' blackstar, blackstar receives the message but are unable to answer since the answer will be sent to the dial-in machine.

The strange message will appear after reboot of another machine if it get an new IP-adress after reboot and has any nfs-history on blackstar before the reboot(and before the dial-in machine appeared).

Possibly solution:
Give the dial-in machines another sub-net IP.

I get the feeling that this is not a possibility.

Mail me if I'm right
Are the other three dial up machines on a separate network ie by this I mean are they on a LAN or have network cards inside them??
It's pretty brute-force, but given your small number of systems, couldn't you just subnet?  At least give it a try.  Put the dialup systems' IP addresses on one subnet, and the ethernet systems' addresses on the other.  Even if it doesn't address the root problem, it ought to isolate it such that things work again.

sherwoodAuthor Commented:
Why would subneting work?  
This still wouldn't stop the rogue machine from claiming a
false IP.

Doing so would be difficult.  To subnet, I'd have to change the
netmask on all my machines (some 180 of them)  On top of that,
a mask that would include all three of hte other machines,
but not require that I re-assign a third of my net to new ip's
would be impossible.  Changing the home machines is not polically
pracatical until I can 'prove' which machine is mis-behaving.
You said you'd established that the rogue machine is not claiming a false IP.

Now where are these 180 other machines?  You didn't mention them in the text of the question.  Blackstar is acting as a router, here, so the dialup systems have to be on a subnet that Blackstar can claim to be routing to.  The other option would be to set up IP Masquerading.  

If you're not ready to try these and you want more help, at least give us a better idea what your network looks like.  Are these 180 systems behind a netmask?  What's the upstream router's address (last octet, at least)?  Will the upstream router trust Blackstar to announce routing for another network (like the private 10.0.0 net)?  Is this all behind a firewall?


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.