Second ip for hosts interface
-
@olivierlambert No,
I want to add second ip address to existing interface.
Example how can i add 10.1.2.100/24 to eth3.
-
I would better create a new network, but I let @fohdeesha answer here
-
@SNSNSN Hi, this isn't possible, at least not without a lot of manual workarounds. It's not recommended anyhow, why do you need to assign another subnet to an adapter already in a different subnet? These should typically be isolated either physically via different connections, or via VLANs.
-
Normally speaking you wouldn't have multiple subnets/IPs on a single virtual NIC, the best route to go is to add another NIC and assign IPs on that end.
What is your goal here?
-
@planedrop said in Second ip for hosts interface:
Normally speaking you wouldn't have multiple subnets/IPs on a single virtual NIC, the best route to go is to add another NIC and assign IPs on that end.
What is your goal here?
I have storages on 2 different ip blocks. 1 for NFS 1 for ISCSI...
-
@SNSNSN Generally you'd want to create another virtual NIC for the VM to connect to the other subnet, it's very uncommon for a single NIC to be used for multiple subnets other than in a VLAN scenario (and then it's usually just for switches, hypervisors, and routers).
You'd want to add another NIC/interface to this VM and then assign that to the other subnet/VLAN.
-
@planedrop If there is no solution to add 2 ip on single PIF, vlan will be solution. I just wonder is it possible or not...
-
@SNSNSN IIRC most operating systems don't support this anyway, unless you are using VLANs, multiple IPs on a single interface isn't the norm and I'm pretty sure the best way to do what you want here is add another interface on the other subnet.
-
@planedrop Yea, looks like, thank you.
-
@SNSNSN Indeed, these would typically at least be isolated via vlans at least (one vlan for iscsi traffic, one for iscsi). There's no point in having them in two different subnets if they're in the same network and vlan, the traffic isn't isolated at all. You might as well have them in the same subnet if you're doing that, in which case you only need 1 IP on the XCP-ng management NIC.
