<?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: IPv6 duplicate issue in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipv6-duplicate-issue/m-p/287741#M76736</link>
    <description>&lt;P&gt;IPv6 duplicate address and no IPv6 iBGP neighbor issue&amp;nbsp; was software code 8.1.6-h2 bug on PAN 3220. It is fixed once code upgraded into 8.1.9-h4. Even Palo alto doesn't had answer on this IPv6 issue.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Sep 2019 17:31:02 GMT</pubDate>
    <dc:creator>TARATHAPA</dc:creator>
    <dc:date>2019-09-10T17:31:02Z</dc:date>
    <item>
      <title>IPv6 duplicate issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipv6-duplicate-issue/m-p/284633#M76329</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;is there anyone had an issue of duplicate IPv6? i coundn't able to ping next hop ipv6 ip.&amp;nbsp; i worked with PAN TAC even they don't have answers just suggested to change different ipv6 subnets, tried by changinging different ipv6 subnet couldn't fix the issue.&amp;nbsp; Our network envirnoment has same architucture for ipv4 and ipv6 but ipv4 working perfectly fine only having issue with ipv6. and i can't able change and commit interface ipv6 address anytime during the work hour it affect ipv4 and blips the internet. It seems severe bug of PAN-3220. Please advice if anyone has answer for this issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Background: - want give some overview of this issue. why this issue appered all of sudden?&amp;nbsp; one month back IPv6 was working and office moved to new location. haven't changed anything in configuration including same LAN and WAN subnets. we are using company owned SWIP block ip address for untrust interface.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;output of untrust interface ethernet1/4&lt;BR /&gt;Name: ethernet1/4, ID: 67&lt;BR /&gt;Link status:&lt;BR /&gt;Runtime link speed/duplex/state: 1000/full/up&lt;BR /&gt;Configured link speed/duplex/state: auto/auto/auto&lt;BR /&gt;MAC address:&lt;BR /&gt;Port MAC address b4:0c:25:e0:40:43&lt;BR /&gt;Operation mode: layer3&lt;BR /&gt;Untagged sub-interface support: no&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;Name: ethernet1/4, ID: 67&lt;BR /&gt;Operation mode: layer3&lt;BR /&gt;Virtual router Primary-VR&lt;BR /&gt;Interface MTU 1500&lt;BR /&gt;Interface IP address: XX.XX.XX.4/24&lt;BR /&gt;Interface IPv6 address: fe80::b60c:25ff:fee0:4043/64 duplicate&lt;BR /&gt;2XXX:XXXX:XXXX:250::4/64&lt;BR /&gt;DAD: enabled&lt;BR /&gt;NDP Monitoring: disabled&lt;BR /&gt;Router Advertisement: enabled&lt;BR /&gt;DNS Support: disabled&lt;BR /&gt;Interface management profile: Ping-Only&lt;BR /&gt;ping: yes telnet: no ssh: no http: no https: no&lt;BR /&gt;snmp: no response-pages: no userid-service: no&lt;BR /&gt;Service configured: IKE BGP&lt;BR /&gt;Zone: UnTrust, virtual system: vsys1&lt;BR /&gt;Adjust TCP MSS: no&lt;BR /&gt;Policing: no&lt;BR /&gt;--------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;--------------------------------------------------------------------------------&lt;BR /&gt;Physical port counters read from MAC:&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;rx-broadcast 626812&lt;BR /&gt;rx-bytes 96224949715&lt;BR /&gt;rx-multicast 28714&lt;BR /&gt;rx-unicast 108679181&lt;BR /&gt;tx-broadcast 972&lt;BR /&gt;tx-bytes 79643981793&lt;BR /&gt;tx-multicast 19&lt;BR /&gt;tx-unicast 92566997&lt;BR /&gt;----------------------------------------&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PAFW(active)&amp;gt; ping inet6 yes source xxxx:xxxx:xxxx:250::4 host xxxx:xxxx:xxxx:250::2&lt;BR /&gt;PING xxxx:xxxx:xxxx:250::2(xxxx:xxxx:xxxx:250::2) from xxxx:xxxx:xxxx:250::4 : 56 data bytes&lt;BR /&gt;^C&lt;BR /&gt;--- xxxx:xxxx:xxxx:250::2 ping statistics ---&lt;BR /&gt;83 packets transmitted, 0 received, 100% packet loss, time 82002ms&lt;/P&gt;&lt;P&gt;PAFW(active)&amp;gt; ping source xx.xx.xx.4 host xx.xx.xx.2&lt;BR /&gt;PING xx.xx.xx.2 (xx.xx.xx.2) from xx.xx.xx.4 : 56(84) bytes of data.&lt;BR /&gt;64 bytes from xx.xx.xx.2: icmp_seq=1 ttl=255 time=0.323 ms&lt;BR /&gt;64 bytes from xx.xx.xx.2: icmp_seq=2 ttl=255 time=0.293 ms&lt;BR /&gt;64 bytes from xx.xx.xx.2: icmp_seq=3 ttl=255 time=0.288 ms&lt;BR /&gt;64 bytes from xx.xx.xx.2: icmp_seq=4 ttl=255 time=0.309 ms&lt;BR /&gt;^C&lt;/P&gt;</description>
      <pubDate>Thu, 22 Aug 2019 16:48:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipv6-duplicate-issue/m-p/284633#M76329</guid>
      <dc:creator>TARATHAPA</dc:creator>
      <dc:date>2019-08-22T16:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: IPv6 duplicate issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipv6-duplicate-issue/m-p/287741#M76736</link>
      <description>&lt;P&gt;IPv6 duplicate address and no IPv6 iBGP neighbor issue&amp;nbsp; was software code 8.1.6-h2 bug on PAN 3220. It is fixed once code upgraded into 8.1.9-h4. Even Palo alto doesn't had answer on this IPv6 issue.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 17:31:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipv6-duplicate-issue/m-p/287741#M76736</guid>
      <dc:creator>TARATHAPA</dc:creator>
      <dc:date>2019-09-10T17:31:02Z</dc:date>
    </item>
  </channel>
</rss>

