netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 212749] New: ping over geneve over ipv6 would fail
Date: Thu, 22 Apr 2021 08:43:31 -0700	[thread overview]
Message-ID: <20210422084331.432a4a24@hermes.local> (raw)



Begin forwarded message:

Date: Thu, 22 Apr 2021 09:42:25 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 212749] New: ping over geneve over ipv6 would fail


https://bugzilla.kernel.org/show_bug.cgi?id=212749

            Bug ID: 212749
           Summary: ping over geneve over ipv6 would fail
           Product: Networking
           Version: 2.5
    Kernel Version: 5.12.0-rc7
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: jishi@redhat.com
        Regression: No

ping over geneve over ipv6 would fail on 5.10.0-rc7 after commit 
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
            Commit: 88a5af943985 - Merge tag 'net-5.12-rc8' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net

reproducer:

ip netns add client                                                             
ip netns add server                                                             
ip link add veth0_c type veth peer name veth0_s                                 
ip link set veth0_c netns client                                                
ip link set veth0_s netns server                                                
ip netns exec client ip link set lo up                                          
ip netns exec client ip link set veth0_c up                                     
ip netns exec server ip link set lo up                                          
ip netns exec server ip link set veth0_s up                                     
ip netns exec client ip addr add 2000::1/64 dev veth0_c                         
ip netns exec client ip addr add 10.10.0.1/24 dev veth0_c                       
ip netns exec server ip addr add 2000::2/64 dev veth0_s                         
ip netns exec server ip addr add 10.10.0.2/24 dev veth0_s                       
ip netns exec client ping 10.10.0.2 -c 2                                        
ip netns exec client ping6 2000::2 -c 2                                         
ip netns exec client ip link add geneve1 type geneve vni 1234 remote 2000::2
ttl 64                   
ip netns exec server ip link add geneve1 type geneve vni 1234 remote 2000::1
ttl 64                   
ip netns exec client ip link set geneve1 up                                     
ip netns exec client ip addr add 1.1.1.1/24 dev geneve1                         
ip netns exec server ip link set geneve1 up                                     
ip netns exec server ip addr add 1.1.1.2/24 dev geneve1
ip netns exec client ping 1.1.1.2 -c 3

actual result:
+ ip netns exec client ping 1.1.1.2 -c 3                                        
PING 1.1.1.2 (1.1.1.2) 56(84) bytes of data.                                    
From 1.1.1.1 icmp_seq=1 Destination Host Unreachable                            
From 1.1.1.1 icmp_seq=2 Destination Host Unreachable                            
From 1.1.1.1 icmp_seq=3 Destination Host Unreachable                            

--- 1.1.1.2 ping statistics ---                                                 
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2072ms

expected result:
ping should pass

BTW, ping over geneve over ipv4 would pass

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-04-22 15:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210422084331.432a4a24@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).