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.
It is my understanding that a server can be accessed by multiple IP addresses if it is configured to respond to them and if the network topology knows to refer requests for those IPs to that particular server. I'm not talking about which IP addresses have requested files from apache.
I'd like to know how to find out which IP addresses my server is configured to occupy and serve requests for. Sorry I'm not explaining this better. I'd very much like to know the proper jargon. I think beadyallen has the right idea. The output is pretty verbose though. It looks something like this for a machine I have access to:
Although the last two aren't likely to work since they're configured on the same subnet as the first one, but on a separate ethernet interface. Unless you're running the ip2 stack, it's not going to be about to route return traffic out eth2 properly, so you'll end up with "triangular routing"... i.e. packets come in eth2, but the replies go out eth1 which results in the connection hanging since the replies are coming from the "wrong" IP.
Edit: Actually it looks like they all are being routed properly, so either the system is using the ip2 stack, or there's a firewall in front that is rewriting the source IPs to match the original request.
Although the last two aren't likely to work since they're configured on the same subnet as the first one, but on a separate ethernet interface. Unless you're running the ip2 stack, it's not going to be about to route return traffic out eth2 properly, so you'll end up with "triangular routing"... i.e. packets come in eth2, but the replies go out eth1 which results in the connection hanging since the replies are coming from the "wrong" IP.
Edit: Actually it looks like they all are being routed properly, so either the system is using the ip2 stack, or there's a firewall in front that is rewriting the source IPs to match the original request.
It's a combination of extended APIs and userland tools to implement more complex routing than what is possible using the standard tools (ifconfig/route/arp).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.