configuring a second eth card


We run a web server application internally in my company.

We have one interface configured with an ip address of and a default gateway of

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface    *        U        40 0          0 eth0       *            U        40 0          0 lo
default         UG       40 0          0 eth0

however this IP address is restricted to only certain other LAN's in the company. We would like to add another card and IP address but connected to another LAN which all the company can access. I assume we would then create a new apache virtual server for this ip address.

The second ip address is and the gateway router is

I tried just adding the new ip address and bringing up the interface but then nothing was reachable. I assume this is because the routing must be changed but I'm really not sure what or how. Also what else must be considered etc.

Can anyone help?

Thanks in advance.
Who is Participating?
jeremynd01Connect With a Mentor Commented:
Wow... real-deal Cisco stuff.... That's nicer than I've ever played with, but maybe I can help a bit with 'los dos network cards'.  I've put two cards in boxes many times, and never had to change the kernel routing table to allow them to talk to their LAN peers.

It sounds like your original card (eth0) works fine (i.e. can ping stuff and get replies) when eth1 is deactivated (#ifconfig eth1 down).   Now when you bring up eth1, try supplying the -I <interface> to ping:

#ping -I eth0 <hosttoping>

and see if it works.  Hopefully it does, because then the existance of eht1 isn't messing up your connection.  Likewise, you should be able to ping something on eth1 when it is active.

If this doesn't work, then do and #ifconfig after eth1 isu up and see if there's a conflict, or paste it into ex-ex so we can ponder at it!!
When you say "nothing was reachable," do you mean that you could not contact the server from other computers on the new network card, or that you couldn't contact other computers from the server?  Also, are your routers really hardware devices, or are you just talking about entries in a dhcp server?

Perhaps a little more setup detail would help.  It could be that you're just not supplying the right commands when you try to ping other devices, your firewall could be in the way, etc...
cbndAuthor Commented:
Hi jeremynd01,

Thanks for your reply.

When I brought up the second interface I lost all connectivity to everything outside the local LAN. All my exisiting connections were terminated and I could no longer ping anything outside. I just got host-unreachable.

There are no DHCP servers or firewalls in this network. It's internally secure from the outside world. The routers are all hardware Cisco's as are the switches.

I cannot rely on my default gateway as it's on the 192.168.28 LAN and this does not connect to all the company. If packets were to some in from the 192.168.6 LAN then I would have to put some routing in place to make sure packets went back through the second interace on the 192.168.6 LAN. There might be something else I need to do but I'm lost there.
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1 
Post your closing recommendations!  No comment means you don't care.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.