<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Dec 30, 2013 at 7:57 PM, Neil Schulz <span dir="ltr"><<a href="mailto:neil.schulz@neteasy.us" target="_blank">neil.schulz@neteasy.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm not very knowledgeable in VLANs. Sorry for the lack of knowledge in advance.<br>
<br>
Is it possible to create a VLAN for WAN traffic, to separate it from the internal network? I'd imagine so. It was a automated and simple process when use XenServer. I'm trying to switch from Xen to oVirt and when trying to recreate this, I'm unable to ping out from the VM.<br>
<br>
This leads me to believe the VLAN was created incorrectly. I created ifcfg-br1 on the host and through the engine, created the logical network with VLAN tagging 20. Does the interface, ifcfg-br1, require a public IP, any IP address, no ip address? (Sorry, never created a VLAN for WAN traffic as it was automated in XenServer)<br>
</blockquote><div><br></div><div>Assigning an IP-address to a VM network in oVirt is _not_ mandatory,<br>it is only needed for "management" networks (ovirtmgmnt, display, storage)<br>where the _hosts_ need connectivity to resources on that network.<br>
<br>Is this a tagged or an untagged vlan? (an untagged vlan means only one vlan<br>per physical interface andneeds no extra configuration on the OS side)<br>Which other (physical) interfaces are in your "br1" interface?<br>
Are the (tagged) vlans assigned to this interface?<br><br></div><div>A vlan interface on linux looks like this: "eth0.20" where eth0 is the<br>"physical" interface on which tagged vlans are configured and 20 is the<br>
number of one of those interfaces.<br><br></div><div>In the case of an oVirt VM network the physical interface is bridged (and sometimes bonded)<br></div><div>so the interface configuration looks like this: "br1.20".<br>
</div><div><br></div><div>The "normal" route for configuring a new network in ovirt is to configure it in the "networks" tab<br>(as a VM network) and then assigin this network to physical- or bonded interfaces on all the<br>
hosts in your cluster.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
>From there I have the VM installed and configured with a public IP address, however, only get Destination Host Unreachable, meaning it has no route out.<br>
<br>
I am banging my head on the desk trying to figure this out. Can anyone give me any assistance?<br>
<br>
Thank you,<br>
Neil<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/users</a><br>
</blockquote></div><br></div></div>