New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UE Can't connect #12

Closed
pcminitech opened this Issue Jan 19, 2018 · 68 comments

Comments

Projects
None yet
2 participants
@pcminitech

pcminitech commented Jan 19, 2018

MME Log
[01/18 20:31:41.915] WARN: [NAS] EMM status(95) : UE[311980000016984] --> EMM (emm_handler.c:429)
[01/18 20:32:06.867] WARN: [NAS] EMM status(95) : UE[311980000016984] --> EMM (emm_handler.c:429)
[01/18 20:32:16.256] WARN: Not implmented (radioNetwork cause : 21) (s1ap_handler.c:427)
[01/18 20:32:31.873] WARN: [NAS] EMM status(95) : UE[311980000016984] --> EMM (emm_handler.c:429)
[01/18 20:32:41.555] WARN: Not implmented (radioNetwork cause : 21) (s1ap_handler.c:427)
[01/18 20:32:56.862] WARN: [NAS] EMM status(95) : UE[311980000016984] --> EMM (emm_handler.c:429)
[01/18 20:33:06.153] WARN: Not implmented (radioNetwork cause : 21) (s1ap_handler.c:427)
[01/18 20:33:21.870] WARN: [NAS] EMM status(95) : UE[311980000016984] --> EMM (emm_handler.c:429)
[01/18 20:33:31.152] WARN: Not implmented (radioNetwork cause : 21) (s1ap_handler.c:427)
[01/18 20:33:45.338] WARN: Not implemented(choice:3, proc:9) (s1ap_sm.c:176)
[01/18 20:33:56.251] WARN: Not implmented (radioNetwork cause : 21) (s1ap_handler.c:427)
[01/18 20:34:07.825] WARN: Unknown message(type:65) (emm_sm.c:505)
[01/18 20:34:31.284] WARN: Unknown message(type:65) (emm_sm.c:505)
[01/18 20:34:57.084] WARN: Unknown message(type:65) (emm_sm.c:505)

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 19, 2018

Hi, pcminitech

Thanks for your effort to test NextEPC.

From your log, UE sends EMM STATUS with protocol error with " Semantically Incorrect messgae(95)". After NextEPC is received this message, it did not handle correctly the exception state to recover EMM state. Let me try to fix this bug.

BTW, Could you give me a pcap(wireshark) file for this situation? It will be very helpful for us to fix this protocol error.

Thanks again!

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

Packet Capture of the Enb the Enb IP is 192.168.1.80 and EPC is 192.168.1.81

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 19, 2018

Unfortunately, this pcap is not enough for me. ^^;
It only includes the "Initial UE Message + Attach Request + PDN conectivity request".
I presume that after EMM_STATUS, you have executed wireshark to capture packets.

I need a pcap that contains the EMM_STATUS that was created before.
This allows me to know the root cause of the EMM_STATUS and make modifications to the EPC.

Could you replay this situations with capturing packet?

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

[01/18 20:31:41.915] WARN: [NAS] EMM status(95) : UE[311980000016984] --> EMM (emm_handler.c:429)

I have a hard time reproducing this error the one I get now is [01/18 20:34:57.084] WARN: Unknown message(type:65) (emm_sm.c:505)

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 19, 2018

Yeah! I agree that it is not easy to generate such a situation.

I'll improve the NextEPC If an EMM_STATUS is encountered, the EMM state will be restored to INITIAL state. And then, the next ATTACH_REQUEST will be worked properly between EPC and eNodeB/UE.

This update will be released v0.3.2 soon.

I'm very appreciated about your time.

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

I could reinstall the epc to reproduce the error

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

Should it work after the 0.3.2 or did I do a bad config

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

Enb Connecting to EPC
Packet_Capture_Enb.zip

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 19, 2018

I think that your configuration has no problem.

Source-level code updates are needed to handle EMM_STATUS error.

But, I'm not sure about v0.3.2 schedule.
Are you familiar with compile installation based on the manual?

Probably, not much time is necessary to add EMM_STATUS error. It will be check-in github master branch soon. Let me inform you if I update the source code regarding this issue.

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

I was able to reproduce the Error in the packet capture.

@pcminitech

This comment has been minimized.

pcminitech commented Jan 19, 2018

did that help

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 20, 2018

Wow! Great! This pcap will be very helpful to me.

At this point, I didn't find out the basic reason about EMM_STATUS even though you gave me the pcap file. But, I can find out that your EMM_STATUS will be handled properly from this last packet capture.

I've updated sources code related EMM STATUS issue yesterday. I'm not sure whether you can use it or not. Because, v0.3.2 is not released at this time, so you need to build the source code.

Let me give you simple guide for you.

  • Stop the previous package deamon

    • systemctl stop nextepc-mmed
    • systemctl stop nextepc-sgwd
    • systemctl stop nextepc-pgwd
    • systemctl stop nextepc-hssd
    • systemctl stop nextepc-pcrfd
  • Build the Package

    • sudo apt-get -y install autotools-dev pkg-config git flex bison libsctp-dev libgnutls28-dev libgcrypt-dev libssl-dev libmongoc-dev libbson-dev mongodb libyaml-dev
    • git clone https://github.com/acetcom/nextepc
    • autoreconf -iv;./configure --prefix=/home/acetcom/git/nextepc/install;make -j 2;make install
  • Test the package

    • ./test/testepc
  • Run the nextepc

    • Edit ./install/etc/nextepc.conf(mme.gummei.mme_gid, mme_code, mme.tai.tac)
    • ./nextepc-epcd
@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

autoreconf -iv;./configure --prefix=/home/acetcom/git/nextepc/install;make -j 2;make install
autoreconf: 'configure.ac' or 'configure.in' is required
-bash: ./configure: No such file or directory
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
I get this error on Ubuntu 16.04

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 20, 2018

Oops. I've missed one guide. Sorry!

You need to change a directory with 'cd nextepc'. Let me re-write it exactly.

[XXX] $ git clone https://github.com/acetcom/nextepc
[XXX/nextepc] $ cd nextepc
[XXX/nextepc] $ autoreconf -iv
[XXX/nextepc] $ ./configure --prefix=./install
[XXX/nextepc] $ make -j 2
[XXX/nextepc] $ make install

You may see the configuration file in the follwing directory.
[XXX/nextepc] $ cd install
[XXX/nextepc/install] $ vi nextepc.conf
You need to changes TAI info.

And then
[XXX/nextepc/install] $ cd ..
[XXX/nextepc] $ ./nextepc-epcd

Sorry to bother you!

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

root@SpeedFI-EPC:/home/daltongilmore# git clone https://github.com/acetcom/nextepc
fatal: destination path 'nextepc' already exists and is not an empty directory.
root@SpeedFI-EPC:/home/daltongilmore#
should I remove the old nextepc folder

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 20, 2018

Anything is possible.

rm -rf nextepc

OR

cd nextepc

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

root@SpeedFI-EPC:/home/daltongilmore/nextepc/nextepc# autoreconf -iv
autoreconf: Entering directory .' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal -I m4 aclocal: warning: couldn't open directory 'm4': No such file or directory configure.ac:16: warning: LT_AC_PROG_SED is m4_require'd but not m4_defun'd acinclude.m4:27: CORE_CONFIG_NICE is expanded from... configure.ac:16: the top level autoreconf: configure.ac: tracing configure.ac:16: warning: LT_AC_PROG_SED is m4_require'd but not m4_defun'd acinclude.m4:27: CORE_CONFIG_NICE is expanded from... configure.ac:16: the top level autoreconf: configure.ac: adding subdirectory lib/freeDiameter-1.2.1 to autoreconf autoreconf: Entering directory lib/freeDiameter-1.2.1'
aclocal: warning: couldn't open directory 'm4': No such file or directory
autoreconf: configure.ac: creating directory build-aux
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
configure.ac:70: installing 'build-aux/ar-lib'
configure.ac:66: installing 'build-aux/compile'
configure.ac:22: installing 'build-aux/config.guess'
configure.ac:22: installing 'build-aux/config.sub'
configure.ac:18: installing 'build-aux/install-sh'
configure.ac:18: installing 'build-aux/missing'
extensions/dbg_msg_dumps/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
extensions/dbg_msg_dumps/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
extensions/dbg_msg_dumps/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
extensions/dbg_msg_dumps/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
extensions/dbg_msg_dumps/Makefile.am:3: its definition is in aclocal's search path.
extensions/dbg_msg_dumps/Makefile.am: installing 'build-aux/depcomp'
extensions/dict_dcca/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
extensions/dict_dcca/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
extensions/dict_dcca/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
extensions/dict_dcca/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
extensions/dict_dcca/Makefile.am:3: its definition is in aclocal's search path.
extensions/dict_dcca_3gpp/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
extensions/dict_dcca_3gpp/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
extensions/dict_dcca_3gpp/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
extensions/dict_dcca_3gpp/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
extensions/dict_dcca_3gpp/Makefile.am:3: its definition is in aclocal's search path.
extensions/dict_mip6i/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
extensions/dict_mip6i/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
extensions/dict_mip6i/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
extensions/dict_mip6i/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
extensions/dict_mip6i/Makefile.am:3: its definition is in aclocal's search path.
extensions/dict_nas_mipv6/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
extensions/dict_nas_mipv6/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
extensions/dict_nas_mipv6/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
extensions/dict_nas_mipv6/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
extensions/dict_nas_mipv6/Makefile.am:3: its definition is in aclocal's search path.
extensions/dict_nasreq/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
extensions/dict_nasreq/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
extensions/dict_nasreq/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
extensions/dict_nasreq/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
extensions/dict_nasreq/Makefile.am:3: its definition is in aclocal's search path.
extensions/dict_rfc5777/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
extensions/dict_rfc5777/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
extensions/dict_rfc5777/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
extensions/dict_rfc5777/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
extensions/dict_rfc5777/Makefile.am:3: its definition is in aclocal's search path.
extensions/dict_s6a/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
extensions/dict_s6a/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
extensions/dict_s6a/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
extensions/dict_s6a/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
extensions/dict_s6a/Makefile.am:3: its definition is in aclocal's search path.
libfdcore/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
libfdcore/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
libfdcore/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
libfdcore/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
libfdcore/Makefile.am:3: its definition is in aclocal's search path.
configure.ac: installing 'build-aux/ylwrap'
libfdproto/Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
libfdproto/Makefile.am:3: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
libfdproto/Makefile.am:3: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
libfdproto/Makefile.am:3: If 'LT_INIT' is in 'configure.ac', make sure
libfdproto/Makefile.am:3: its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 20, 2018

My guide may be wrong. Autoconf/Libtool is not working.
Let me changes as below.

[XXX/nextepc] $ sudo apt-get install autoconf libtool gcc
[XXX/nextepc] $ autoreconf -iv

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

./configure --prefix=./install
didn't work I just ran the
./configure

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

./configure --prefix=./install
configure: error: expected an absolute directory name for --prefix: ./install

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 20, 2018

Absolute path is needed

./configure --prefix=/home/pcminitech/nextepc/install

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

/etc/nextepc/mme.conf
where is that file now

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 20, 2018

In the build environment, configuration file is not located at /etc/nextepc.

if you are using ./configure --prefix=/home/daltongilmore/nextepc/install, the file is located /home/daltongilmore/nextepc/install/nextepc directory.

And also, mme/sgw/pgw.conf is package configuraton.
You should use the nextepc.conf in build environment.

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

Enb connects quick now

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

That file is not there and I can't find the log files anymore

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

daltongilmore@SpeedFI-EPC:~/nextepc/install$ ls
bin etc lib var

@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

daltongilmore@SpeedFI-EPC:/nextepc$ ls
acinclude.m4 config.log install main.o nextepc-mmed stamp-h1
aclocal.m4 config.nice lib Makefile nextepc-pcrfd support
autom4te.cache config.status libtool Makefile.am nextepc-pgwd test
build-aux configure LICENSE Makefile.in nextepc-sgwd webui
config.h configure.ac m4 nextepc-epcd README.md
config.in debian main.c nextepc-hssd src
daltongilmore@SpeedFI-EPC:
/nextepc$

1 similar comment
@pcminitech

This comment has been minimized.

pcminitech commented Jan 20, 2018

daltongilmore@SpeedFI-EPC:/nextepc$ ls
acinclude.m4 config.log install main.o nextepc-mmed stamp-h1
aclocal.m4 config.nice lib Makefile nextepc-pcrfd support
autom4te.cache config.status libtool Makefile.am nextepc-pgwd test
build-aux configure LICENSE Makefile.in nextepc-sgwd webui
config.h configure.ac m4 nextepc-epcd README.md
config.in debian main.c nextepc-hssd src
daltongilmore@SpeedFI-EPC:
/nextepc$

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 22, 2018

Could you give me your pcap file and nextepc.conf?
Let me check if there is a problem in nextepc.

And also, if you can update latest source code, give me a nextepc.log files, it will be helpful to solve the problem.

Update Latest Source Code

  • [/home/daltongilmore/nextepc]$ git pull
  • [/home/daltongilmore/nextepc]$ make -j 2
  • [/home/daltongilmore/nextepc]$ cd lib
  • [/home/daltongilmore/nextepc/lib]$ make install
  • [/home/daltongilmore/nextepc/lib]$ cd ..
  • [/home/daltongilmore/nextepc]$ ./nextepc-epcd

And then, give me a nextepc.log file

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

Enb with connect to MME and with not activate cell

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

nextepc.zip
Nextepc.conf

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

It will active cell until I change the mme.conf to my setting for the sim that brakes it

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 23, 2018

From your logfile,

File Logging : '/home/daltongilmore/nextepc/install/var/log/nextepc/nextepc.log'
MongoDB URI : 'mongodb://localhost/nextepc'
Configuration : '/home/daltongilmore/nextepc/install/etc/nextepc/nextepc.conf'

If you send me "nextepc.conf" from getting '/home/daltongilmore/nextepc/install/etc/nextepc/nextepc.conf', there is some problem.

Please, check LINE 134 in nextepc.conf
tac: 12345 ==> tac:1

Good luck!

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 23, 2018

Ah! Sorry! You need to change GUMMEI's PLMN_ID and TAI's PLMN_ID/TAC.

Let me attach the modified nextepc.conf
nextepc.zip

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

Should I change the mme.conf or leave it now

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

daltongilmore@SpeedFI-EPC:~/nextepc$ ./nextepc-epcd
NextEPC daemon v0.3.2 - Jan 20 2018 23:35:07

[01/23 08:38:51.459] WARN: pid file /home/daltongilmore/nextepc/install/var/run/nextepc-epcd/pid overwritten -- Unclean shutdown of previous NextEPC run? (init.c:104)
PID[8266] : '/home/daltongilmore/nextepc/install/var/run/nextepc-epcd/pid'
File Logging : '/home/daltongilmore/nextepc/install/var/log/nextepc/nextepc.log'
MongoDB URI : 'mongodb://localhost/nextepc'
Configuration : '/home/daltongilmore/nextepc/install/etc/nextepc/nextepc.conf'
[01/23 08:38:51.462] PCRF try to initialize
[01/23 08:38:51.520] PCRF initialize...done
[01/23 08:38:51.522] PGW try to initialize
[01/23 08:38:51.616] PGW initialize...done
[01/23 08:38:51.616] gtp_server() [127.0.0.1]:2123
[01/23 08:38:51.616] gtp_server() [127.0.0.1]:2152
[01/23 08:38:51.616] ERRR: iotcl error(dev:pgwtun flags = 4096) (unix/tun.c:71)
[01/23 08:38:51.616] ERRR: tun_open(dev:pgwtun) failed (pgw_gtp_path.c:231)
[01/23 08:38:51.616] ERRR: Can't establish PGW path (pgw_sm.c:49)
[01/23 08:38:51.617] SGW try to initialize
[01/23 08:38:51.617] INFO: CONNECTED TO 'pgw.localdomain' (TCP,soc#7): (fd_logger.c:93)
[01/23 08:38:51.618] INFO: CONNECTED TO 'pcrf.localdomain' (TCP,soc#10): (fd_logger.c:93)
[01/23 08:38:51.635] SGW initialize...done
[01/23 08:38:51.635] gtp_server() [127.0.0.2]:2123
[01/23 08:38:51.636] gtp_server() [192.168.1.81]:2152
[01/23 08:38:51.637] HSS try to initialize
[01/23 08:38:51.803] HSS initialize...done
[01/23 08:38:51.804] MME try to initialize
[01/23 08:38:52.313] MME initialize...done

[01/23 08:38:52.313] INFO: NextEPC daemon start (main.c:156)
[01/23 08:38:52.313] gtp_server() [192.168.1.81]:2123
[01/23 08:38:52.313] gtp_client() [127.0.0.2]:2123
[01/23 08:38:52.313] s1ap_server() [192.168.1.81]:36412
[01/23 08:38:52.316] INFO: CONNECTED TO 'mme.localdomain' (TCP,soc#7): (fd_logger.c:93)
[01/23 08:38:52.316] INFO: CONNECTED TO 'hss.localdomain' (TCP,soc#10): (fd_logger.c:93)
[01/23 08:45:01.073] eNB-S1 accepted[192.168.1.80]:36412 in s1_path module
[01/23 08:45:01.073] eNB-S1 accepted[192.168.1.80] in master_sm module
[01/23 08:48:26.521] gtp_client() [192.168.1.81]:2123
[01/23 08:48:26.522] gtp_client() [127.0.0.1]:2123
[01/23 08:48:26.522] gtp_client() [127.0.0.2]:2123
[01/23 08:48:26.522] gtp_client() [192.168.1.81]:2152
[01/23 08:48:26.526] gtp_client() [127.0.0.1]:2152
[01/23 08:48:26.663] WARN: [EMM] EMM STATUS : IMSI[311980000017000] Cause[95] (emm_sm.c:568)
[01/23 08:48:37.183] WARN: [EMM] EMM STATUS : IMSI[311980000017000] Cause[95] (emm_sm.c:568)
[01/23 08:48:47.703] WARN: [EMM] EMM STATUS : IMSI[311980000017000] Cause[95] (emm_sm.c:568)
[01/23 08:48:58.223] WARN: [EMM] EMM STATUS : IMSI[311980000017000] Cause[95] (emm_sm.c:568)
[01/23 08:49:08.743] WARN: [EMM] EMM STATUS : IMSI[311980000017000] Cause[95] (emm_sm.c:568)
[01/23 08:53:11.283] WARN: [EMM] EMM STATUS : IMSI[311980000017000] Cause[95] (emm_sm.c:568)

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 23, 2018

Hi, pcminitech

Note that you don't update mme.conf if you use the BUILD environment(make install). In this case, nextepc-epcd uses nextepc.conf. Of course, if you use the DEBIAN PACKAGE environment(apt-get install nextepc), you should updates mme.conf instead of nextepc.conf

BTW, I presume that EMM_STATUS is a temporal error. So, if UE try to do ATTACH REQUEST again, I expected that UE succeeds to register NextEPC. But, I think there is some protocol error in NextEPC. Basically, I need to find out why your eNodeB raises this EMM STATUS error.

Please, give me some time. Wireshare pcap file is enough to analyze this issue.

Thank you very much for your effort.

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 23, 2018

I have one question. Do you have any other EPC?
If the EPC has no problem about EMM_STATUS, could you give me a pcap file with using another EPC? "From ATTACH_REQUEST to ATTACH_ACCEPT"

Thanks!

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 23, 2018

Ah! IPSEC! OK!. I'll solve the problem without another EPC.

BTW, there is a bug in NextEPC protocol stack. EPS attach result(Spec 24.301, 9.9.3.10) in ATTACH_ACCEPT is not derived from EPS attach type(9.9.3.11) in ATTACH_REQUEST. EPS attach result was filled with combined EPS/IMSI attach(2) regardless of EPS attach type.

I've updated NextEPC source code. But I'm not sure that this changes could solve the problem of EMM_STATUS.

You can update the changes from github. Note that you should update nextepc.conf. Of course, you don't have to update mme.conf

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

Great New the UE now connects!!!

@pcminitech

This comment has been minimized.

pcminitech commented Jan 23, 2018

I now get some other error now,

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 23, 2018

WOW! GREAT! Thanks!

Please, don’t hegitate raise any questions!

Thanks again!

@pcminitech

This comment has been minimized.

pcminitech commented Jan 24, 2018

[01/23 16:48:32.206] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:32.846] ERRR: sock_write(len:66) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:32.846] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:32.846] ERRR: sock_write(len:66) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:32.846] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:34.126] ERRR: sock_write(len:66) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:34.126] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:34.126] ERRR: sock_write(len:66) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:34.126] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:39.266] ERRR: sock_write(len:66) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:39.266] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:39.266] ERRR: sock_write(len:66) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:39.266] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:39.926] ERRR: sock_write(len:58) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:39.926] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:39.926] ERRR: sock_write(len:58) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:39.926] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:40.086] ERRR: sock_write(len:73) failed(9:Bad file descriptor) (unix/socket.c:549)
[01/23 16:48:40.086] ERRR: sock_write() failed (pgw_gtp_path.c:171)
[01/23 16:48:40.086] ERRR: sock_write(len:73) failed(9:Bad file descriptor) (unix/socket.c:549)

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 24, 2018

You may try to do 'ping'. Right?

I think that the problem might be related to set up TUN device.
Did you remove the nextepc package using 'sudo apt-get purge nextepc-core'? If so, you need to setup TUN device.

Let me guide as below.

  1. Check TUN device

    • [/home/daltongilmore/nextepc]$ ifconfig pgwtun
  2. If there is no TUN device,

    • [/home/daltongilmore/nextepc]$ sudo ip tuntap add name pgwtun mode tun
    • [/home/daltongilmore/nextepc]$ sudo ip addr add 45.45.0.1/16 dev pgwtun
    • [/home/daltongilmore/nextepc]$ sudo ip addr add cafe::1/16 dev pgwtun
    • [/home/daltongilmore/nextepc]$ sudo ip link set pgwtun up
  3. Re-check TUN device

    • [/home/daltongilmore/nextepc]$ ifconfig pgwtun
pgwtun    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:45.45.0.1  P-t-P:45.45.0.1  Mask:255.255.0.0
          inet6 addr: fe80::db53:5995:e15b:5cb4/64 Scope:Link
          inet6 addr: cafe::1/64 Scope:Global
          UP POINTOPOINT NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:56 errors:0 dropped:0 overruns:0 frame:0
          TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:10752 (10.7 KB)  TX bytes:2368 (2.3 KB)
  1. If you can see the TUN device(pgwtun), run NextEPC.
    • [/home/daltongilmore/nextepc]$ ./nextepc-epcd

If it is not working, give me a full nextepc.log file. And also, the result of 'ifconfig pgwtun' is also helpful to solve the issue.

@pcminitech

This comment has been minimized.

pcminitech commented Jan 24, 2018

yes the adapter is gone

@pcminitech

This comment has been minimized.

pcminitech commented Jan 24, 2018

I'm using a LGW gateway that separates the traffic off at the Enb only management traffic go to the EPC

@pcminitech

This comment has been minimized.

pcminitech commented Jan 24, 2018

I would like to try using APN for different networks

@acetcom

This comment has been minimized.

Owner

acetcom commented Jan 24, 2018

In the nextepc.conf, there is some manual about "using APN for different network"

Here is a example.

  o 'test' APN uses 45.46.0.1/16, 'test2' APN uses 45.47.0.1/16.
     All other APNs use 45.45.0.1/16
    $ sudo ip addr add 45.45.0.1/16 dev pgwtun
    $ sudo ip addr add 45.46.0.1/16 dev pgwtun
    $ sudo ip addr add 45.47.0.1/16 dev pgwtun

    ue_pool:
      - addr: 45.45.0.1/16
      - addr: 45.46.0.1/16
        apn: test
      - addr: 45.47.0.1/16
        apn: test2

If you cannot understand it, explain me how you'll setup the network with exact IP address.

@pcminitech pcminitech closed this Jan 27, 2018

@pcminitech

This comment has been minimized.

pcminitech commented Mar 2, 2018

The UE will not reconnect today It worked great for month and half

@pcminitech pcminitech reopened this Mar 2, 2018

@pcminitech

This comment has been minimized.

pcminitech commented Mar 2, 2018

Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: 000c405e 00000500 08000340 1351001a 00353407 41710839 11890000 10864102
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: e0e00023 027cd011 271d8080 21100100 00108106 00000000 83060000 0000000a
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: 00000d00 00100000 43000600 13f18900 01006440 080013f1 894009f1 30008640
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: 0130
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: [03/01 23:58:45.312] ASSERT: !(0). Can't decode S1AP_PDU (mme_sm.c:183)
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: [03/01 23:59:07.933] ASSERT: !(clbuf). No more free clbuf. (unix/pkbuf.c:144)
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: [03/01 23:59:07.933] ASSERT: !(clbuf). Can't allocate clbuf(length:8) (unix/pkbuf.c:2
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: [03/01 23:59:07.933] ASSERT: !(p). pkbuf_alloc failed(headroom:8, size:8) (unix/pkbuf
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: [03/01 23:59:07.933] ERRR: Decoding of IE s1ap_InitialUEMessage failed (s1ap_ies_deco
Mar 01 23:59:07 SpeedFI-EPC nextepc-mmed[2965]: 98 bytes hex:

@acetcom

This comment has been minimized.

Owner

acetcom commented Mar 3, 2018

You may use the OLD nextepc version. Right?
From Issue #18 , there is a significant memory problem under 0.3.3 version.

Would you update your NextEPC version to 0.3.4?
Let me know if I have misunderstanding.

Thanks!

@pcminitech pcminitech closed this Mar 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment