<?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 Re: vgva layer2 vpn - gre tunnel between AP and VGVA behind NAT in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/vgva-layer2-vpn-gre-tunnel-between-ap-and-vgva-behind-nat/m-p/88924#M8326</link>
    <description>Hi Andrea, thanks for your patience here. I ran this past one of our engineers and in general they'd like it if we could open a case for this, they have a lot of follow up questions and it's just easier if we can keep all of the information in a case. In general, we do support NATing GRE traffic. We NAT GRE traffic for layer 3 roaming by default.</description>
    <pubDate>Tue, 25 Jan 2022 16:43:39 GMT</pubDate>
    <dc:creator>SamPirok</dc:creator>
    <dc:date>2022-01-25T16:43:39Z</dc:date>
    <item>
      <title>vgva layer2 vpn - gre tunnel between AP and VGVA behind NAT</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/vgva-layer2-vpn-gre-tunnel-between-ap-and-vgva-behind-nat/m-p/88923#M8325</link>
      <description>Hello,&lt;BR /&gt;I've a problem setting up a guest ssid with traffic tunneled to a VGVA via GRE encapsulation.&lt;BR /&gt;&lt;BR /&gt;Here the network diagram (rif: &lt;A href="https://cloud.kapostcontent.net/pub/10a358c3-2aff-41e5-baf1-b8275e775765/vgva-layer-2-vpn-configuration-guide" target="_blank" rel="noopener" title="vgva-layer-2-vpn-configuration-guide"&gt;vgva-layer-2-vpn-configuration-guide&lt;/A&gt; ) I'm testing, only difference is I'm using GRE encapsulation instead of IPSec:&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;
&lt;DIV class="media" style="overflow: hidden"&gt;
&lt;DIV class="media" style="overflow: hidden"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="w71BzfQQyOmzWOON4Agw_netdiagramextreme.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/4972i2BE95406E67DB3F2/image-size/large?v=v2&amp;amp;px=999" role="button" title="w71BzfQQyOmzWOON4Agw_netdiagramextreme.png" alt="w71BzfQQyOmzWOON4Agw_netdiagramextreme.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;GRE tunnel between AP and VPN Gateway goes UP but AP clients doesn't work. I can see client traffic encapsulated in GRE arriving to VGVA but&amp;nbsp;&lt;BR /&gt;I can't see any client's traffic de-ecapsulated and coming out of the VGVA.&lt;BR /&gt;&lt;BR /&gt;Any suggestion ? Is it possible that NATing GRE encapsulation is not supported ?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 20 Jan 2022 12:41:39 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/vgva-layer2-vpn-gre-tunnel-between-ap-and-vgva-behind-nat/m-p/88923#M8325</guid>
      <dc:creator>AndreaT</dc:creator>
      <dc:date>2022-01-20T12:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: vgva layer2 vpn - gre tunnel between AP and VGVA behind NAT</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/vgva-layer2-vpn-gre-tunnel-between-ap-and-vgva-behind-nat/m-p/88924#M8326</link>
      <description>Hi Andrea, thanks for your patience here. I ran this past one of our engineers and in general they'd like it if we could open a case for this, they have a lot of follow up questions and it's just easier if we can keep all of the information in a case. In general, we do support NATing GRE traffic. We NAT GRE traffic for layer 3 roaming by default.</description>
      <pubDate>Tue, 25 Jan 2022 16:43:39 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/vgva-layer2-vpn-gre-tunnel-between-ap-and-vgva-behind-nat/m-p/88924#M8326</guid>
      <dc:creator>SamPirok</dc:creator>
      <dc:date>2022-01-25T16:43:39Z</dc:date>
    </item>
  </channel>
</rss>

