<html><head></head><body><div class="ydpc63b7815yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">is that a sub-interface then?</div><div><br></div>
</div><div id="yahoo_quoted_0712355588" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, April 20, 2022, 10:04:51 AM MST, Keith Smith via PLUG-discuss <plug-discuss@lists.phxlinux.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">WOW Thanks!! If we were running a box of VPS's and the box had two NICs <br clear="none">would the second NIC be redundant just in case the 1st NIC fails.... How <br clear="none">do multiple NICs on the same box work?<br clear="none"><br clear="none">OK so the software layer on the O/S talks to the NIC but is not actually <br clear="none">assigned to any particular NIC?<br clear="none"><br clear="none">Thanks for all the replies, this is very educational.<br clear="none"><br clear="none"><br clear="none"><div class="yqt1642272741" id="yqtfd83504"><br clear="none">On 2022-04-20 09:19, Kevin Fries wrote:<br clear="none">> Always remember, the network interface from the OS side and the<br clear="none">> network interface from the hardware side are two completely different<br clear="none">> concepts. Other than the fact that they are generally matched one to<br clear="none">> one, they really have nothing to do with one another.<br clear="none">> <br clear="none">> A hardware interface (i.e. on a NIC) is physical, and you have as many<br clear="none">> as you have. No way to manufacture more without installing more<br clear="none">> hardware.<br clear="none">> <br clear="none">> A OS network interface is a software construct. ETH0 (using the old<br clear="none">> vernacular) generally maps to the first hardware interface, and<br clear="none">> provides a hook for software to use… most notably the network stack.<br clear="none">> While it is not done out of the box, there is no restriction to say<br clear="none">> that two of these constructs can not map to the same back end<br clear="none">> construct. So yes, you can have ETH0.1 (again, using the old<br clear="none">> vernacular)<br clear="none">> <br clear="none">> VMWare and other similar virtual machine managers can take advantage of <br clear="none">> this.<br clear="none">> <br clear="none">> The second point you need to get straight in your head is that a fixed<br clear="none">> IP address is never a construct of the box, but of the Domain Naming<br clear="none">> Service (DNS) on the network. It is NAMED that assigns the IP<br clear="none">> address. For an interface (software in this case as the hardware’s<br clear="none">> address is actually the MAC ADDRESS) to have an address, it asks the<br clear="none">> DHCP server for it. If the DHCP has been told, always assign this<br clear="none">> address to this requester, the address is a fixed, reserved, or<br clear="none">> dedicated IP depending on who is speaking to you. They all mean the<br clear="none">> Same thing.<br clear="none">> <br clear="none">> So, yes, the number of NICs on a box does not limit the number of<br clear="none">> network interfaces the OS provides, and yes, each of those interfaces<br clear="none">> can have a dynamic or dedicated IP address.<br clear="none">> <br clear="none">> HTH<br clear="none">> Kevin<br clear="none">> <br clear="none">> Sent from my iPad<br clear="none">> <br clear="none">>> On Apr 20, 2022, at 9:51 AM, Keith Smith via PLUG-discuss <br clear="none">>> <<a shape="rect" ymailto="mailto:plug-discuss@lists.phxlinux.org" href="mailto:plug-discuss@lists.phxlinux.org">plug-discuss@lists.phxlinux.org</a>> wrote:<br clear="none">>> <br clear="none">>> <br clear="none">>> Hi,<br clear="none">>> I'm wondering how VPS servers are configured. I have a VPS with a <br clear="none">>> dedicated IP. I assume I share a box that has a number of virtual <br clear="none">>> machines and I assume each VPS has a dedicated IP.<br clear="none">>> <br clear="none">>> This is a hardware question. I assume the box has at least 2 network <br clear="none">>> cards. So lets say the server has 20 VPS on it and each has a <br clear="none">>> dedicated IP. Does the box need a NIC for each IP or does the box have <br clear="none">>> NIC cards that can service/route multiple IPs?<br clear="none">>> <br clear="none">>> I have a Dell consumer grade mini tower computer with a single NIC <br clear="none">>> which is built into the motherboard. I assume that NIC can only <br clear="none">>> service one IP address, is that correct or can I install <br clear="none">>> virtualization software on this computer and use the NIC for multiple <br clear="none">>> IP's?<br clear="none">>> <br clear="none">>> Did I just open a can of worms?<br clear="none">>> <br clear="none">>> Thanks in advance for your wisdom.<br clear="none">>> ---------------------------------------------------<br clear="none">>> PLUG-discuss mailing list - <a shape="rect" ymailto="mailto:PLUG-discuss@lists.phxlinux.org" href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br clear="none">>> To subscribe, unsubscribe, or to change your mail settings:<br clear="none">>> <a shape="rect" href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br clear="none">---------------------------------------------------<br clear="none">PLUG-discuss mailing list - <a shape="rect" ymailto="mailto:PLUG-discuss@lists.phxlinux.org" href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br clear="none">To subscribe, unsubscribe, or to change your mail settings:<br clear="none"><a shape="rect" href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a></div></div></div>
</div>
</div></body></html>