<?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 Bug in CSV Interface import with unnumbered interfaces in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/bug-in-csv-interface-import-with-unnumbered-interfaces/m-p/276053#M1794</link>
    <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Running Expedition 1.1.28.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recently begun importing tunnels via CSV import. I have discovered that interfaces with type (media) "tunnel" are ignored if they are not assigned an address at all. Tunnel interfaces often don't need addresses asigned, especially if they are used with static routing and next-hop is the interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Performing an experiment with an ortdinary ethernet interface shows the same thing, without an address ethernet interfaces are not imported either. This is more understandable, as this could be en error in the CSV file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Request: Please allow importing interfaces without IP addresses, at least for those media types where it makes sense.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;/Per&lt;/P&gt;</description>
    <pubDate>Thu, 11 Jul 2019 07:55:56 GMT</pubDate>
    <dc:creator>Per_Westerlund</dc:creator>
    <dc:date>2019-07-11T07:55:56Z</dc:date>
    <item>
      <title>Bug in CSV Interface import with unnumbered interfaces</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/bug-in-csv-interface-import-with-unnumbered-interfaces/m-p/276053#M1794</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Running Expedition 1.1.28.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recently begun importing tunnels via CSV import. I have discovered that interfaces with type (media) "tunnel" are ignored if they are not assigned an address at all. Tunnel interfaces often don't need addresses asigned, especially if they are used with static routing and next-hop is the interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Performing an experiment with an ortdinary ethernet interface shows the same thing, without an address ethernet interfaces are not imported either. This is more understandable, as this could be en error in the CSV file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Request: Please allow importing interfaces without IP addresses, at least for those media types where it makes sense.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;/Per&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2019 07:55:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/bug-in-csv-interface-import-with-unnumbered-interfaces/m-p/276053#M1794</guid>
      <dc:creator>Per_Westerlund</dc:creator>
      <dc:date>2019-07-11T07:55:56Z</dc:date>
    </item>
    <item>
      <title>Re: Bug in CSV Interface import with unnumbered interfaces</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/bug-in-csv-interface-import-with-unnumbered-interfaces/m-p/276066#M1796</link>
      <description>&lt;P&gt;Workaround: Set a dummy address, then it will be accepted. The address can be removed later.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;/Per&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2019 08:22:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/bug-in-csv-interface-import-with-unnumbered-interfaces/m-p/276066#M1796</guid>
      <dc:creator>Per_Westerlund</dc:creator>
      <dc:date>2019-07-11T08:22:49Z</dc:date>
    </item>
  </channel>
</rss>

