<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic VLAN traffic to WAN (Hop between Core to Router) in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-traffic-to-wan-hop-between-core-to-router/m-p/4473860#M19369</link>
    <description>HI All, Please help...&lt;BR /&gt;&lt;BR /&gt;3x VLAN&lt;BR /&gt;VID 1 &lt;BR /&gt;VID 2 Data (Router resides on this VLAN)&lt;BR /&gt;VID 3 VoIP&lt;BR /&gt;&lt;BR /&gt;All uplinks have VLANs 2&amp;amp;3 tagged on all edge switches.&lt;BR /&gt;All edge switches has Default gateway as IP of the default VLAN on core.&lt;BR /&gt;&lt;BR /&gt;Core has default route to WAN router.&lt;BR /&gt;WAN router has new static routes supportin VLAN traffic on VID 2 &amp;amp; 3.&lt;BR /&gt;&lt;BR /&gt;I can ping outside IP address (Not DNS) on VLAN 3 when i do a tracert on VID 3 the hop between Core switch to Router times out but the hops cont and reach thier destination.&lt;BR /&gt;&lt;BR /&gt;I am having DNS problems on VID 3 even when using off site DNS servers which i believe is the result of this hop problem.&lt;BR /&gt;&lt;BR /&gt;Any ideas?&lt;BR /&gt;&lt;BR /&gt;Many thanks,&lt;BR /&gt;Kc.&lt;BR /&gt;</description>
    <pubDate>Wed, 05 Aug 2009 12:52:12 GMT</pubDate>
    <dc:creator>KCollinson</dc:creator>
    <dc:date>2009-08-05T12:52:12Z</dc:date>
    <item>
      <title>VLAN traffic to WAN (Hop between Core to Router)</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-traffic-to-wan-hop-between-core-to-router/m-p/4473860#M19369</link>
      <description>HI All, Please help...&lt;BR /&gt;&lt;BR /&gt;3x VLAN&lt;BR /&gt;VID 1 &lt;BR /&gt;VID 2 Data (Router resides on this VLAN)&lt;BR /&gt;VID 3 VoIP&lt;BR /&gt;&lt;BR /&gt;All uplinks have VLANs 2&amp;amp;3 tagged on all edge switches.&lt;BR /&gt;All edge switches has Default gateway as IP of the default VLAN on core.&lt;BR /&gt;&lt;BR /&gt;Core has default route to WAN router.&lt;BR /&gt;WAN router has new static routes supportin VLAN traffic on VID 2 &amp;amp; 3.&lt;BR /&gt;&lt;BR /&gt;I can ping outside IP address (Not DNS) on VLAN 3 when i do a tracert on VID 3 the hop between Core switch to Router times out but the hops cont and reach thier destination.&lt;BR /&gt;&lt;BR /&gt;I am having DNS problems on VID 3 even when using off site DNS servers which i believe is the result of this hop problem.&lt;BR /&gt;&lt;BR /&gt;Any ideas?&lt;BR /&gt;&lt;BR /&gt;Many thanks,&lt;BR /&gt;Kc.&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Aug 2009 12:52:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-traffic-to-wan-hop-between-core-to-router/m-p/4473860#M19369</guid>
      <dc:creator>KCollinson</dc:creator>
      <dc:date>2009-08-05T12:52:12Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN traffic to WAN (Hop between Core to Router)</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-traffic-to-wan-hop-between-core-to-router/m-p/4473861#M19370</link>
      <description>&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;the hop between Core switch to Router times out but the hops cont and reach thier destination&lt;BR /&gt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;how did you check ?&lt;BR /&gt;do you get response back? if so they also "hop back".&lt;BR /&gt;there may be a filter in it's path (firewall or just ACL on the router or the coreswitch) that doesn't allow this device answering this ICMP traceroute packets, but do allow them to be forwarded to the next hop and pass the response.</description>
      <pubDate>Thu, 06 Aug 2009 05:27:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-traffic-to-wan-hop-between-core-to-router/m-p/4473861#M19370</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2009-08-06T05:27:52Z</dc:date>
    </item>
  </channel>
</rss>

