Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
having two nics is not interesting. It's what you're actually doing with them them affects things. You need to give us the full picture if you want advice. Only thing that people seem to always want to do is to have two default gateways. I still have no idea what they think that means.
having two nics is not interesting. It's what you're actually doing with them them affects things. You need to give us the full picture if you want advice. Only thing that people seem to always want to do is to have two default gateways. I still have no idea what they think that means.
One is for the public facing and other is internal. For internal, it will communicate with our backup server. It is the network guy's idea . A main concern is to make sure the machine communicates to the backup server on the correct NIC. We use EMC Networker.
Last edited by trackstar2000; 06-19-2013 at 02:24 PM.
The rules of TCP/IP don't change in linux. The issue would be usually a combination of IP address and subnet mask. That should allow IP range choice to correct endpoint within subnet. If it goes outside of subnet then you'd have to add in a gateway address. This may be confusing if both nic's need a gateway. That could be fixed with some settings. Usually internal lan doesn't use a gateway but tell us the exact topology.
Linux versions may put gateway and other settings in different places. It may be automated on some dhcp or may have to have some network manager settings changed.
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
Posts: 3,233
Rep:
Quote:
Originally Posted by trackstar2000
One is for the public facing and other is internal. For internal, it will communicate with our backup server. It is the network guy's idea . A main concern is to make sure the machine communicates to the backup server on the correct NIC. We use EMC Networker.
good idea, I've done something like that myself except it was a web server talking to a back-end database server and file server.
as mentioned, as long as the two nics are assigned to two distinct discrete networks and the backup server is configured to belong to the same network as the internal nic than it should work
something like this:
It turns out the network guy used a cicso asa (used NAT). I only had to use one physical NIC which is 10.XX.XX.XX. When I am logged in, the browser shows my IP address as 134.XX.ZZ.ZZ (Same iP I used for SSH).
We are trying to get backup to run (our backup server is on 134.XX.YY.YY)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.