![]() ![]() Paquetes RX:53176 errores:0 perdidos:0 overruns:0 frame:0 Paquetes RX:4458717 errores:0 perdidos:1674 overruns:0 frame:0 I agree with you regarding to interface aliasing is very old, but it seems to be well configured as you can see in my /etc/network/interfaces file but ifconfig don't show the interface ifconfigĭirec. ![]() We are an ISP so we don't have that problem :-D. It's only because I didn't want to show the IP address of the server :-D I have put "net1-IP" and "net1-GW" instead of the IP address that I have in the /etc/network/interfaces files. Just put the actual addresses in there for the "address" and "gateway" fields, not symbolic names. Gateway net1-GWShouldn't the address lines in /etc/network/interfaces have IP address entries? Even if net1-IP is in /etc/hosts, I'm not sure that the network startup scripts will do any name resolution. Did your ISP really give you a /26? Pretty generous if so. ![]() The netmask you're using (255.255.255.192) is for a /26, or 62 usable addresses. Many ISPs will give their commercial customers a /29 or even a /28, though that's less common in these days of IP address shortages. Of course you need an ISP that will give you an IP subnet, not just a single address to make this work. Since HTTPS doesn't take too well to name-based virtual hosts, it's easier to assign a second IP address to the NIC and bind the HTTPS server to that address. I've used interface aliasing when I wanted to have a separate HTTP and HTTPS servers on the same box. Shouldn't the address lines in /etc/network/interfaces have IP address entries? Even if net1-IP is in /etc/hosts, I'm not sure that the network startup scripts will do any name resolution. Just specify different ports for the different services with NAT. I'll be using LAN IP's in this example, so replace them with the ones you'll be using. The instructions provided apply to RedHat, Fedora, and CentOS. One of the major benefits is that you don't need a physical adapter for each IP but instead can create many virtual ones tied to a single physical card. By using multiple IP's you can run a service under a specific IP while having another service under a different one (for example, have HTTP on one and SMTP on another), or create a private LAN using a local IP and have the alias hold your Internet IP (such as NAT). This tutorial demonstrates how to bind multiple IP addresses to a single NIC. If you wanna do this because of this example. Ethernet, Fast-Ethernet, Gigabit-Ethernet, Fiber and so on.Īlso why o why would you do such a thing? You cannot have more then one IPv4 or IPv6 address or mac address for that matter on one interface. Paquetes TX:28563 errores:0 perdidos:0 overruns:0 carrier:0īytes RX:2559324 (2.5 MB) TX bytes:2559324 (2.5 MB)Įth0:1 Link encap:Ethernet direcciónHW d0:27:88:75:c2:90īut, "netstat -putan" shows me several service listening in the second IP. Paquetes RX:28563 errores:0 perdidos:0 overruns:0 frame:0 Paquetes RX:2371126 errores:0 perdidos:925 overruns:0 frame:0 Pre-up iptables-restore < /etc/lesīut if I execute "ifconfig" i can only view the eth0 and lo interfaces:Įth0 Link encap:Ethernet direcciónHW d0:27:88:75:c2:90ĭirec. ![]() # dns-* options are implemented by the resolvconf package, if installed I have Ubuntu Server 11.10 64bits and I have configured "/etc/network/interfaces" as follows: I need to configure multiple IP address in only one ethernet interface card (eth0). ![]()
0 Comments
Leave a Reply. |