APLawrence - Information and Resources for Unix and Linux Systems, Bloggers and the self-employed
RSS Feeds Get APLawrence.com by RSS











(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Home > Unix Articles > Address change kills networking
Printer Friendly Version




A Change of Address




I had shut down my computer and was getting ready to wrap up the day when the phone rang. My wife always groans and tells me to let these last minute calls go to voice mail, but I never pay attention. I didn't recognize the caller id, though I did know it was from a mid-western state. I answered.

The caller had a downed Unix machine. Big crash, dead hardware, but he had a backup machine that he had restored backups to and had changed the IP to match the old server. But networking was not working: he couldn't ping any other machine and other machines couldn't ping that.

"Arp caching", I said. Local networks actually communicate using hardware MAC addresses; machines maintain tables that match IP to MAC. Every machine on the network would have the MAC address of the dead server matched with its IP and would be trying to communicate with that. Simple..

"Well, yeah, but this has been up for five hours."



Ooops. That's not MAC caching. I don't remember how long Windows keeps its arp cache, but it isn't that long. Hmmm..

I had him check routing, netconfig, hosts: everything I could think of. This machine was working before you changed the address? Check, yes. Hmmmmm.

Well, maybe the NIC card has just coincidentally gone dead. Is there another nic card in the machine?

"Actually, there are four NIC cards. I wasn't sure which was good, so I put the same address on all of them".

Ahhh. There it is: the machine is confused as to where to route packets: I'm not sure which card it would choose, but obviously it wasn't the one plugged in! I told him to either delete the other cards or change them to unique IP addresses. I held on the phone while he did that and rebooted; all was well after that.

You can put multiple addresses on one card through ip aliasing, but you can't put the same address on multiple cards quite that easily. IP bonding can do this, but that's not what was being done here. Every card could route LAN packets, but which card would? That was the problem.


If this page was useful to you, please click to help others find it:  
Your +1's can help friends, contacts, and others on the web find the best stuff when they search.


Comments?




More Articles by Anthony Lawrence - Find me on Google+



Click here to add your comments



Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



LOD Communications, Inc.

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!


book graphic unix and linux troubleshooting guide




Buy Kerio from a dealer who knows tech: I sell and support

Kerio Connect Mail server, Control, Workspace and Operator licenses and subscription renewals
pavatar.jpg

This post tagged:

       - Networking
       - SCO_OSR5
       - Troubleshooting
       - Unix




Unix/Linux Consultants

Skills Tests

Guest Post Here