<?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 Hello Richard here is the in Routing and SD-WAN</title>
    <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921185#M268722</link>
    <description>&lt;P&gt;Hello Richard here is the thing..&lt;/P&gt;
&lt;P&gt;The customer wants me to set up a VPN connection from 10.107.54.35 255.255.255.255 to their internal ip addresses for example 10.67.0.11 255.255.255.0 and etc.&lt;/P&gt;
&lt;P&gt;However i also have to configure a network for my internal network for example 10.107.0.0 255.255.255.0 with DHCP on the router. Therefore i need the physical interface for that network. Since the Fa0/1 is connected to a switch. That is why i wanted to create 2 sub interfaces...Im surprised i am getting confused by such a simple configuration...but i just cant figure it out...&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks again for your reply&lt;/P&gt;</description>
    <pubDate>Mon, 14 Mar 2016 17:04:25 GMT</pubDate>
    <dc:creator>dogiiibih</dc:creator>
    <dc:date>2016-03-14T17:04:25Z</dc:date>
    <item>
      <title>VPN tunnel through tunnel interface</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921181#M268718</link>
      <description>&lt;P&gt;Hello everyone...&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Im trying to establish a connection to a remote peer through VPN...the tunnel interface is up 1st IKE exchange is good and the &amp;nbsp;tunnel is in QM_IDLE &amp;nbsp;ACTIVE state. However i am not able to ping anything from the tunnel interface not even the directly connected interfaces.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The Tunnel interface is up / down probably because of the tunnel source or?&lt;/P&gt;
&lt;P&gt;Check the configuration please and thank you for any information....&amp;nbsp;&lt;/P&gt;
&lt;P&gt;!&lt;BR /&gt;hostname&amp;nbsp;TEST&lt;BR /&gt;!&lt;BR /&gt;boot-start-marker&lt;BR /&gt;boot system flash c1841-advsecurityk9-mz.124-25.bin&lt;BR /&gt;boot-end-marker&lt;BR /&gt;!&lt;BR /&gt;enable secret 5 $1$0HF/$DoHwwKDdu3Z3fReN6YgK./&lt;BR /&gt;!&lt;BR /&gt;no aaa new-model&lt;BR /&gt;memory-size iomem 15&lt;BR /&gt;ip cef&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;ip auth-proxy max-nodata-conns 3&lt;BR /&gt;ip admission max-nodata-conns 3&lt;BR /&gt;no ip dhcp use vrf connected&lt;BR /&gt;!&lt;BR /&gt;ip dhcp pool LAN&lt;BR /&gt; import all&lt;BR /&gt; network 10.107.0.0 255.255.255.0&lt;BR /&gt; default-router 10.107.0.1&lt;BR /&gt; dns-server ...............................&lt;BR /&gt; lease 7&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;crypto isakmp policy 1&lt;BR /&gt; encr aes 256&lt;BR /&gt; authentication pre-share&lt;BR /&gt; group 5&lt;BR /&gt;!&lt;BR /&gt;crypto isakmp policy 2&lt;BR /&gt; encr 3des&lt;BR /&gt; authentication pre-share&lt;BR /&gt; group 2&lt;BR /&gt; lifetime 28800&lt;BR /&gt;!&lt;BR /&gt;crypto isakmp policy 3&lt;BR /&gt; encr 3des&lt;BR /&gt; authentication pre-share&lt;BR /&gt; group 2&lt;BR /&gt; lifetime 28800&lt;BR /&gt;!&lt;BR /&gt;crypto isakmp policy 4&lt;BR /&gt; encr 3des&lt;BR /&gt; authentication pre-share&lt;BR /&gt; group 2&lt;BR /&gt; lifetime 3600&lt;BR /&gt;!&lt;BR /&gt;crypto isakmp policy 5&lt;BR /&gt; encr 3des&lt;BR /&gt; authentication pre-share&lt;BR /&gt; group 2&lt;BR /&gt;crypto isakmp key TEST&amp;nbsp;address a.c.b.d&amp;nbsp;no-xauth&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;crypto ipsec transform-set OTTO esp-3des esp-sha-hmac&lt;BR /&gt;!&lt;BR /&gt;crypto ipsec profile OTTO&lt;BR /&gt; set transform-set OTTO&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;crypto map OTTO_1 1 ipsec-isakmp&lt;BR /&gt; description Tunnel to CUSTOMER&lt;BR /&gt; set peer&amp;nbsp;a.c.b.d&lt;BR /&gt; set transform-set OTTO&lt;BR /&gt; match address 100&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;interface Tunnel0&lt;BR /&gt; ip address 10.107.54.35 255.255.255.254&lt;BR /&gt; tunnel source &lt;SPAN&gt;a.b.c.d&lt;/SPAN&gt;&lt;BR /&gt; tunnel destination a.c.b.d&lt;BR /&gt; tunnel mode ipsec ipv4&lt;BR /&gt; tunnel protection ipsec profile OTTO&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/0&lt;BR /&gt; description === WAN ===&lt;BR /&gt; ip address&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;a.b.c.d a.b.c.d (global ip adress)&lt;/SPAN&gt;&lt;BR /&gt; ip nat outside&lt;BR /&gt; ip virtual-reassembly&lt;BR /&gt; duplex auto&lt;BR /&gt; speed auto&lt;BR /&gt; crypto map OTTO_1&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1&lt;BR /&gt; description === LAN ===&lt;BR /&gt; ip address 10.107.0.1 255.255.255.0&lt;BR /&gt; ip nat inside&lt;BR /&gt; ip virtual-reassembly&lt;BR /&gt; rate-limit input 20480000 1024000 1024000 conform-action transmit exceed-action drop&lt;BR /&gt; rate-limit output 20480000 1024000 1024000 conform-action transmit exceed-action drop&lt;BR /&gt; duplex auto&lt;BR /&gt; speed auto&lt;BR /&gt;!&lt;BR /&gt;ip forward-protocol nd&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 &lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;a.b.c.d (global ip adress)&lt;/SPAN&gt;&lt;BR /&gt;!&lt;BR /&gt;no ip http server&lt;BR /&gt;no ip http secure-server&lt;BR /&gt;ip nat inside source route-map OTTO-RMAP_1 interface FastEthernet0/0 overload&lt;BR /&gt;!&lt;BR /&gt;ip access-list extended OTTO-VPN&lt;BR /&gt; remark CCP_ACL Category=16&lt;BR /&gt; deny ip 10.107.0.0 0.0.0.255 10.79.0.0 0.0.0.255&lt;BR /&gt; deny ip 10.107.0.0 0.0.0.255 10.210.0.0 0.0.0.255&lt;BR /&gt; deny ip 10.107.0.0 0.0.0.255 10.67.0.0 0.0.0.127&lt;BR /&gt; deny ip 10.107.54.34 0.0.0.1 10.79.0.0 0.0.0.255&lt;BR /&gt; deny ip 10.107.54.34 0.0.0.1 10.210.0.0 0.0.0.255&lt;BR /&gt; deny ip 10.107.54.34 0.0.0.1 10.67.0.0 0.0.0.127&lt;BR /&gt; deny ip host 10.107.54.35 10.79.0.0 0.0.0.255&lt;BR /&gt; deny ip host 10.107.54.35 10.210.0.0 0.0.0.255&lt;BR /&gt; deny ip host 10.107.54.35 10.67.0.0 0.0.0.127&lt;BR /&gt; permit ip 10.107.54.34 0.0.0.1 any&lt;BR /&gt; permit ip 10.107.54.35 0.0.0.1&lt;BR /&gt; permit ip 10.107.0.0 0.0.0.255 any&lt;BR /&gt;!&lt;BR /&gt;access-list 1 permit&amp;nbsp;a.b.c.d&lt;BR /&gt;access-list 1 permit a.c.d.b&lt;BR /&gt;access-list 100 permit ip 10.107.0.0 0.0.0.255 10.79.41.0 0.0.0.255&lt;BR /&gt;access-list 100 permit ip 10.107.0.0 0.0.0.255 10.210.0.0 0.0.0.255&lt;BR /&gt;access-list 100 permit ip 10.107.0.0 0.0.0.255 10.67.212.0 0.0.0.127&lt;BR /&gt;access-list 100 permit ip 10.107.54.34 0.0.0.0 10.79.41.0 0.0.0.255&lt;BR /&gt;access-list 100 permit ip 10.107.54.34 0.0.0.0 10.210.0.0 0.0.0.255&lt;BR /&gt;access-list 100 permit ip 10.107.54.34 0.0.0.0 10.67.212.0 0.0.0.127&lt;BR /&gt;access-list 100 permit ip 10.107.54.35 0.0.0.0 10.79.41.0 0.0.0.255&lt;BR /&gt;access-list 100 permit ip 10.107.54.35 0.0.0.0 10.210.0.0 0.0.0.255&lt;BR /&gt;access-list 100 permit ip 10.107.54.35 0.0.0.0 10.67.212.0 0.0.0.127&lt;BR /&gt;snmp-server community stopwashdoo RO 1&lt;BR /&gt;route-map OTTO-RMAP_1 permit 1&lt;BR /&gt; match ip address OTTO-VPN&lt;BR /&gt; match interface FastEthernet0/0&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2019 11:33:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921181#M268718</guid>
      <dc:creator>dogiiibih</dc:creator>
      <dc:date>2019-03-05T11:33:24Z</dc:date>
    </item>
    <item>
      <title>My first comment is that you</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921182#M268719</link>
      <description>&lt;P&gt;My first comment is that you are combining two VPN technologies. You have configured a crypto map and have assigned the crypto map to the outbound physical interface which is correct when using traditional IPsec tunnel. You have also configured the tunnel using the IPsec protection profile which means that you are using VTI which is a newer IPsec technology. Either approach is valid and would work. I have never seen them combined in a single configuration and wonder if this is part of your problem. I suggest that you choose one technology to use and then remove the configuration of the other technology.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;My second comment is that the tunnel interface is almost certainly up/down because the encryption negotiation was not successful. The tunnel with protection profile works differently from a normal GRE tunnel. A GRE tunnel will be up/up as long as the router has a valid route in the routing table to the tunnel destination (it does not matter whether the destination is actually reachable, only that the router has a valid route to the destination). A tunnel using VTI will be up/up only after the encryption negotiation is successful and if the negotiation fails then the tunnel will be up/down.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;So decide which technology you want to use, clean up the config to eliminate the other technology, test again, and let us know the results. If it still does not work then we will be in better position to troubleshoot and determine what is the problem.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2016 14:07:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921182#M268719</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2016-03-14T14:07:25Z</dc:date>
    </item>
    <item>
      <title>Hello Richard thanks for</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921183#M268720</link>
      <description>&lt;P&gt;Hello Richard thanks for responding...&lt;/P&gt;
&lt;P&gt;Since i dont have another physical interface i could create 2 sub interfaces right?&lt;/P&gt;
&lt;P&gt;The vpn tunnel needs to be only established with 1 ip address and that is 10.107.54.35 255.255.255.255. Since the other end the peer has no more ip addresses open.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2016 14:32:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921183#M268720</guid>
      <dc:creator>dogiiibih</dc:creator>
      <dc:date>2016-03-14T14:32:19Z</dc:date>
    </item>
    <item>
      <title>I do not understand your</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921184#M268721</link>
      <description>&lt;P&gt;I do not understand your response. Why would you want 2 sub interfaces? In what way would that help you with your encryption processing?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;It appears that your router is an 1841 and I believe that the 1841 does support configuration of vlan subinterfaces if that is what you are asking about.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I do not understand what you are saying about the peer device and its limited IP addresses. If the peer is very limited for IP addresses then that might be a reason to choose to implement your VPN using the crypto map, since using the crypto map does not require that any IP address of their address space is configured on your router while the tunnel VTI does require an IP address.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2016 16:21:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921184#M268721</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2016-03-14T16:21:16Z</dc:date>
    </item>
    <item>
      <title>Hello Richard here is the</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921185#M268722</link>
      <description>&lt;P&gt;Hello Richard here is the thing..&lt;/P&gt;
&lt;P&gt;The customer wants me to set up a VPN connection from 10.107.54.35 255.255.255.255 to their internal ip addresses for example 10.67.0.11 255.255.255.0 and etc.&lt;/P&gt;
&lt;P&gt;However i also have to configure a network for my internal network for example 10.107.0.0 255.255.255.0 with DHCP on the router. Therefore i need the physical interface for that network. Since the Fa0/1 is connected to a switch. That is why i wanted to create 2 sub interfaces...Im surprised i am getting confused by such a simple configuration...but i just cant figure it out...&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks again for your reply&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2016 17:04:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921185#M268722</guid>
      <dc:creator>dogiiibih</dc:creator>
      <dc:date>2016-03-14T17:04:25Z</dc:date>
    </item>
    <item>
      <title>I just noticed i had the</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921186#M268723</link>
      <description>&lt;P&gt;I just noticed i had the wrong subnets on the extended ACL but its still not working...&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2016 19:04:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921186#M268723</guid>
      <dc:creator>dogiiibih</dc:creator>
      <dc:date>2016-03-14T19:04:00Z</dc:date>
    </item>
    <item>
      <title>It is not clear whether you</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921187#M268724</link>
      <description>&lt;P&gt;It is not clear whether you have taken any of my advice and changed anything. So we do not know what you have got at this point or why that might not be working. Perhaps you can start with a clear explanation of what you are attempting to achieve and then the current configuration of the router. Perhaps that would allow us to give you good advice.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2016 19:55:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921187#M268724</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2016-03-14T19:55:37Z</dc:date>
    </item>
    <item>
      <title>I solved the problem it was</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921188#M268725</link>
      <description>&lt;P&gt;I solved the problem it was just a subnet mismatch...damn &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;But thanks a lot for your help Richard I appreciate it.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2016 11:35:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921188#M268725</guid>
      <dc:creator>dogiiibih</dc:creator>
      <dc:date>2016-03-15T11:35:17Z</dc:date>
    </item>
    <item>
      <title>You are quite welcome. I am</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921189#M268726</link>
      <description>&lt;P&gt;You are quite welcome. I am glad that my suggestions were helpful and more glad that you were able to solve your own issue. It is nice when I can help someone solve an issue but it is even better when they find their own solution. So congratulations. And thanks for the ratings.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2016 15:23:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/vpn-tunnel-through-tunnel-interface/m-p/2921189#M268726</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2016-03-15T15:23:07Z</dc:date>
    </item>
  </channel>
</rss>

