<?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: U200-A L2TP in Security e-Series</title>
    <link>https://community.hpe.com/t5/security-e-series/u200-a-l2tp/m-p/5704939#M163</link>
    <description>&lt;P&gt;i use the inode client, that you can obtaining downloading the Inome management center and creating a customized setup&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=110&amp;amp;prodSeriesId=4177945&amp;amp;prodTypeId=12883&amp;amp;objectID=c02602433" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=110&amp;amp;prodSeriesId=4177945&amp;amp;prodTypeId=12883&amp;amp;objectID=c02602433&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the config i used was this&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=120&amp;amp;prodSeriesId=5061731&amp;amp;prodTypeId=18964&amp;amp;objectID=c03093836" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=120&amp;amp;prodSeriesId=5061731&amp;amp;prodTypeId=18964&amp;amp;objectID=c03093836&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;even without the certificate setup...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had this strange problem though: having a complex ( many private subnet ) i setup a route in the firewall for all the private network versus the private WAN router, and this break the L2TP in a strange way&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;after connecting IPSEC the l2tp engine send l2tp packet TO THE IP OF THE CLIENT BEFORE THE NAT!!! ( and you will find the packed using wireshark in the TRUST INTERFACE.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;disabling this route ( so that all the packet go to the UNTRUST ) the firewall fixed the packet and the L2TP go up...&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ended trying tho force the routing of LT2P packet to the untrusted , reenabling the private network routing and it seem working ( but i'havent feedback from the support ).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have a private network that overlap the private network of the client, the L2TP connection, without this trick do not go up!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 28 Jun 2012 13:15:19 GMT</pubDate>
    <dc:creator>Manfri</dc:creator>
    <dc:date>2012-06-28T13:15:19Z</dc:date>
    <item>
      <title>U200-A L2TP</title>
      <link>https://community.hpe.com/t5/security-e-series/u200-a-l2tp/m-p/5646869#M158</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently working with a U200-A and trying to get L2TP running. I'm not getting an active connection. In the security policy I see the L2TP connection entering the U200 on the untrust zone to local zone. The policies allow the L2TP and I see the session the session table but not getting active.&lt;/P&gt;&lt;P&gt;I configured this according to the documentation. Configured a local user for user access but this didn't help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm using software version 5.20 feature 5128P01. this because also SSL-VPN is needed for this customer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm using Windows 7 but it seems that only IPSec is possible ith this. I also used Vista, XP and iPad but all the same results.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone worked with L2TP before? If so, can you share how to configure and how to configure Windows?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards André&lt;/P&gt;</description>
      <pubDate>Fri, 04 May 2012 14:09:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/security-e-series/u200-a-l2tp/m-p/5646869#M158</guid>
      <dc:creator>Breuk230</dc:creator>
      <dc:date>2012-05-04T14:09:50Z</dc:date>
    </item>
    <item>
      <title>Re: U200-A L2TP</title>
      <link>https://community.hpe.com/t5/security-e-series/u200-a-l2tp/m-p/5704939#M163</link>
      <description>&lt;P&gt;i use the inode client, that you can obtaining downloading the Inome management center and creating a customized setup&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=110&amp;amp;prodSeriesId=4177945&amp;amp;prodTypeId=12883&amp;amp;objectID=c02602433" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=110&amp;amp;prodSeriesId=4177945&amp;amp;prodTypeId=12883&amp;amp;objectID=c02602433&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the config i used was this&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=120&amp;amp;prodSeriesId=5061731&amp;amp;prodTypeId=18964&amp;amp;objectID=c03093836" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=120&amp;amp;prodSeriesId=5061731&amp;amp;prodTypeId=18964&amp;amp;objectID=c03093836&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;even without the certificate setup...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had this strange problem though: having a complex ( many private subnet ) i setup a route in the firewall for all the private network versus the private WAN router, and this break the L2TP in a strange way&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;after connecting IPSEC the l2tp engine send l2tp packet TO THE IP OF THE CLIENT BEFORE THE NAT!!! ( and you will find the packed using wireshark in the TRUST INTERFACE.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;disabling this route ( so that all the packet go to the UNTRUST ) the firewall fixed the packet and the L2TP go up...&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ended trying tho force the routing of LT2P packet to the untrusted , reenabling the private network routing and it seem working ( but i'havent feedback from the support ).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have a private network that overlap the private network of the client, the L2TP connection, without this trick do not go up!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jun 2012 13:15:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/security-e-series/u200-a-l2tp/m-p/5704939#M163</guid>
      <dc:creator>Manfri</dc:creator>
      <dc:date>2012-06-28T13:15:19Z</dc:date>
    </item>
  </channel>
</rss>

