On 04/18/2016 08:01 PM, liyulei wrote:
And I used the command "tcpdump -i eno1.5 " to capture the datagrams through the vlan interface, there were only repeated outputs: ARP who has 192.68.81.254 Tell 192.168.81.3
Could you tell me the reason for that?
My guess would be that the switch isn't configured to give you access to VLAN 5 with tagged packets. In that case, there's no need for you to configure eno1.5
Specifically what are you trying to accomplish by configuring a tagged VLAN interface?
Thank you again.
I am deploying Liberty Neutron, according the official document, there are two NIC at least, but my physical machine has only one. Someone suggested me I could create a vlan interface, then everything would be ok. Until now, though I created the vlan interface, it can't attach to the Internet.
Could other methods created virtual interface instead of vlan interface?
Thanks
Li yulei
-----邮件原件----- 发件人: centos-bounces@centos.org [mailto:centos-bounces@centos.org] 代表 Gordon Messmer 发送时间: 2016年4月19日 11:18 收件人: CentOS mailing list 主题: Re: [CentOS] 答复: How to configure VLAN in CentOS7
On 04/18/2016 08:01 PM, liyulei wrote:
And I used the command "tcpdump -i eno1.5 " to capture the datagrams through the vlan interface, there were only repeated outputs: ARP who has 192.68.81.254 Tell 192.168.81.3
Could you tell me the reason for that?
My guess would be that the switch isn't configured to give you access to VLAN 5 with tagged packets. In that case, there's no need for you to configure eno1.5
Specifically what are you trying to accomplish by configuring a tagged VLAN interface? _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 04/18/2016 11:19 PM, liyulei wrote:
I am deploying Liberty Neutron, according the official document, there are two NIC at least, but my physical machine has only one. Someone suggested me I could create a vlan interface, then everything would be ok. Until now, though I created the vlan interface, it can't attach to the Internet.
Could other methods created virtual interface instead of vlan interface?
I can't give you an authoritative answer, but... You might be able to deploy the openstack components that you need using VLANs, but you have to understand how 802.1q tagging works.
Since you don't have access to the switch, when you create a tagged VLAN, you will only be able to communicate on that interface with other systems where you have created an identically tagged interface, and only if your switch supports jumbo packets and doesn't try to manage the tagged packets.
I'm guessing that you don't have access to your router since you don't have access to your switch. In that case, you should revert ifcfg-eno1 to its original state. You can't put the subnet to which your default gateway is attached on a tagged interface. With that file in its original state, you can create a new, tagged interface with a different subnet and no GATEWAY specified. Then, create an interface with the same tag number on a different computer, and assign another address in the same (new) subnet. Test communication between those two addresses. Specifically, test streaming data to make sure that full-sized packets work correctly.
-
Gordon Messmer -
liyulei