[Users] Create VLAN for WAN traffic

[Bob Doolittle]

And yes, it needs an ip address on a separate network, and your LAN needs
to know how to reach the VLAN's network.

-Bob
On Dec 30, 2013 2:28 PM, "Bob Doolittle" <bob at doolittle.us.com> wrote:

> In a situation like this a common issue is that the host you are pinging
> does not have a route back to your VLAN so can't send the response. Can you
> monitor traffic at the destination and see if it's receiving your pings?
> Can you ping from the other direction?
>
> In my general networking experience creating a VLAN is simple. Teaching
> your LAN about your VLAN is harder, and requires external configuration of
> routes.
>
> -Bob
> On Dec 30, 2013 1:57 PM, "Neil Schulz" <neil.schulz at neteasy.us> wrote:
>
>> I'm not very knowledgeable in VLANs. Sorry for the lack of knowledge in
>> advance.
>>
>> 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.
>>
>> 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)
>>
>> 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.
>>
>> I am banging my head on the desk trying to figure this out. Can anyone
>> give me any assistance?
>>
>> Thank you,
>> Neil
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20131230/8d6f06fb/attachment-0001.html>