Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Hello,
Any idea?
Suppose you have a NIC on a server and you want to set five public IP addresses on it, then you should be able to communicate with these other IP addresses and use them.
When you don't specify a source binding, then the system is going to use the default route interface. I believe if you use -S IP to be the source of your ping OR -I interface, then it will use the alternate interface. So ping -s 10.0.5.20 google.com will use the alternate ip as well -I interface.
When you don't specify a source binding, then the system is going to use the default route interface. I believe if you use -S IP to be the source of your ping OR -I interface, then it will use the alternate interface. So ping -s 10.0.5.20 google.com will use the alternate ip as well -I interface.
Hello,
Thank you so much for your reply.
I have done this before and I created this thread because of it:
Yeah, so you just use the -I or -S with your source ip address. When people test (and have multiple ips) they often forget to set the source and it gives them the wrong results. This is often when pinging from a router where there might be lots of paths out or routing instances.
Most tools where the source makes a difference have a way to bind the source.
The switch/router the ethernet cable will connect to from your server must also support it plus creating Switch Virtual Interfaces (SVI) to route the different subnets.
Yeah, so you just use the -I or -S with your source ip address. When people test (and have multiple ips) they often forget to set the source and it gives them the wrong results. This is often when pinging from a router where there might be lots of paths out or routing instances.
Most tools where the source makes a difference have a way to bind the source.
Hello,
Thank you for your reply.
You mean multipath routing?
That would be one case, you have if you 2 paths out, you need to bind to the appropriate source to route to the right interface. In your case (simple added ip) I would not consider that to be multipath because your are using the same interface for both paths, hardly redundant. Multi Path refers to connecting to 2 separate networks and interfaces to provide redundancy.
That would be one case, you have if you 2 paths out, you need to bind to the appropriate source to route to the right interface. In your case (simple added ip) I would not consider that to be multipath because your are using the same interface for both paths, hardly redundant. Multi Path refers to connecting to 2 separate networks and interfaces to provide redundancy.
Hello,
Thanks again.
You said:
Quote:
In your case (simple added ip)...
What do you mean?
Same interface? Can you tell me more?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.