Uploaded image for project: 'vpp'
  1. vpp
  2. VPP-1930

Crash when configured nat with gre interface

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • nat
    • None

      version : vpp master
      vpp configuration:
       G0 ip 192.168.102.151
       create gre tunnel src 192.168.102.151 dst 192.168.100.174
       set interface stat gre0 up
       set interface ip addr gre0 8.8.8.1/30
       set interface nat44 out gre0 output-feature
      linux configuration:
       ip: 192.168.100.174
       ip tunnel add mode gre remote 192.168.102.151 local 192.168.100.174 
       ifconfig gre0 8.8.8.2/30 up

      after configuration, ping 8.8.8.1 then crash

      DBGvpp# 2: /root/work/vpp-master/src/vnet/config.h:130 (vnet_get_config_data) assertion ` < vec_len (cm->config_string_heap)' fails

       

      Program received signal SIGABRT, Aborted.

      [Switching to Thread 0x7fff3bfff700 (LWP 45893)]

      0x00007ffff5478387 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55

      55        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);

      Missing separate debuginfos, use: debuginfo-install krb5-libs-1.15.1-37.el7_7.2.x86_64 libcom_err-1.42.9-16.el7.x86_64 mbedtls-2.7.16-2.el7.x86_64 pkcs11-helper-1.11-3.el7.x86_64

      it's bt info

      (gdb) bt

      #0  0x00007ffff5478387 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55

      #1  0x00007ffff5479a78 in __GI_abort () at abort.c:90

      #2  0x000000000040858e in os_panic () at /root/work/vpp-master/src/vpp/vnet/main.c:371

      #3  0x00007ffff6219aa6 in debugger () at /root/work/vpp-master/src/vppinfra/error.c:84

      #4  0x00007ffff6219e91 in _clib_error (how_to_die=2, function_name=0x0, line_number=0, 

          fmt=0x7fffaff78e80 "%s:%d (%s) assertion `%s' fails") at /root/work/vpp-master/src/vppinfra/error.c:143

      #5  0x00007fffafdffd32 in vnet_get_config_data (cm=0x7fffb44f03e0, config_index=0x1002492e94, 

          next_index=0x1002492ed8, n_data_bytes=0) at /root/work/vpp-master/src/vnet/config.h:130

      #6  0x00007fffafe00007 in vnet_feature_next_with_data (next0=0x1002492ed8, b0=0x1002492e80, n_data_bytes=0)

          at /root/work/vpp-master/src/vnet/feature/feature.h:316

      #7  0x00007fffafe00031 in vnet_feature_next (next0=0x1002492ed8, b0=0x1002492e80)

          at /root/work/vpp-master/src/vnet/feature/feature.h:324

      #8  0x00007fffafe076eb in nat44_ed_in2out_fast_path_node_fn_inline (vm=0x7fffb4b667c0, node=0x7fffb530c540, 

          frame=0x7fffb531c7c0, is_output_feature=1) at /root/work/vpp-master/src/plugins/nat/in2out_ed.c:967

      #9  0x00007fffafe095af in nat44_ed_in2out_output_node_fn_hsw (vm=0x7fffb4b667c0, node=0x7fffb530c540, 

          frame=0x7fffb531c7c0) at /root/work/vpp-master/src/plugins/nat/in2out_ed.c:1515

      #10 0x00007ffff7edfc3f in dispatch_node (vm=0x7fffb4b667c0, node=0x7fffb530c540, type=VLIB_NODE_TYPE_INTERNAL, 

          dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x7fffb531c7c0, last_time_stamp=1085510887320845)

          at /root/work/vpp-master/src/vlib/main.c:1194

      #11 0x00007ffff7ee0349 in dispatch_pending_node (vm=0x7fffb4b667c0, pending_frame_index=0, 

          last_time_stamp=1085510887320845) at /root/work/vpp-master/src/vlib/main.c:1353

      #12 0x00007ffff7ee2395 in vlib_main_or_worker_loop (vm=0x7fffb4b667c0, is_main=0)

          at /root/work/vpp-master/src/vlib/main.c:1848

      #13 0x00007ffff7ee2e17 in vlib_worker_loop (vm=0x7fffb4b667c0) at /root/work/vpp-master/src/vlib/main.c:1982

      #14 0x00007ffff7f23b55 in vlib_worker_thread_fn (arg=0x7fffb6a77e80)

          at /root/work/vpp-master/src/vlib/threads.c:1814

      #15 0x00007ffff6238870 in clib_calljmp () at /root/work/vpp-master/src/vppinfra/longjmp.S:123

      #16 0x00007fff3bffebb0 in ?? ()

      #17 0x00007ffff7f1da47 in vlib_worker_thread_bootstrap_fn (arg=0x7fffb6a77e80)

          at /root/work/vpp-master/src/vlib/threads.c:585

      Backtrace stopped: previous frame inner to this frame (corrupt stack?)

            fivarga89 Filip Varga
            fivarga89 Filip Varga
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: