Hi Denis, If we can choose VLAN and Vlan domain while adding IPv4 address for the object will be good. If the IPv4 space belongs to VLAN(s), when we add IPv4 address for the object and the IPv4 address match the IPv4 space, we would link to identify which VLAN will the IPv4 address belong to. Thanks. -----邮件原件----- 发件人: racktables-users-bounce@xxxxxxxxxxxxx [mailto:racktables-users-bounce@xxxxxxxxxxxxx] 代表 Denis Ovsienko 发送时间: 2014年1月13日 13:35 收件人: racktables-users@xxxxxxxxxxxxx 主题: [racktables-users] Re: duplicate IP address for difference VLAN or domain 13.01.2014, 09:16, "Dika Ye" <dika.ye@xxxxxxxxxxxxx>: > Hi Denis, > > Thanks for your reply. > > It seems that we can map difference VLANs to the same IPv4 address > space in racktables, then when I add the IPv4 address for the object, > it will auto connect to the > IPv4 space which I have mapped to the difference VLANs, but I can't > identify the object IPv4 address belong to which VLAN. Object's IPv4 address belongs to the VLAN(s) to that the IPv4 network belongs. > What's the actually usage for "mapping difference VLANs to the same > IPv4 address space" in racktables? A lot of related reasoning is in the thread that starts with this message: //www.freelists.org/post/racktables-users/Subnets-can-only-belong-to-on e-VLAN -- Denis Ovsienko