iotcreators.com web
    • Login
    • Search
    • forum.iotcreators.com
    • docs.iotcreators.com
    • Tags
    • Popular
    • Recent
    • Register

    IPv6 can't receive any packet via m2m.public.nl

    Network & Coverage
    ipv6 netherlands lte-m
    3
    4
    154
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rxtx last edited by

      I’m testing IPv6 connectivity via LTE-M and I’m unable to receive any packet.
      According to tcpdump, only outbound UDP goes through, but no UDP nor TCP packet is ever received.

      2022-02-20T12:52:51.681Z DEBUG modem >> AT+CGDCONT=0,"IPV4V6","m2m.public.nl"
2022-02-20T12:52:51.701Z DEBUG modem << OK
2022-02-20T12:53:01.828Z DEBUG modem >> AT+CFUN=1
2022-02-20T12:53:01.879Z DEBUG modem << OK
2022-02-20T12:53:02.910Z DEBUG modem >> AT+CFUN?
2022-02-20T12:53:02.923Z DEBUG modem << +CFUN: 1
2022-02-20T12:53:02.952Z DEBUG modem << OK
2022-02-20T12:53:02.997Z DEBUG modem >> AT+CGMM
2022-02-20T12:53:03.011Z DEBUG modem << nRF9160-SICA
2022-02-20T12:53:03.013Z DEBUG modem << OK
2022-02-20T12:53:03.020Z DEBUG modem >> AT+CGMR
2022-02-20T12:53:03.034Z DEBUG modem << mfw_nrf9160_1.3.1
2022-02-20T12:53:03.037Z DEBUG modem << OK
2022-02-20T12:53:03.046Z DEBUG modem >> AT+CEMODE?
2022-02-20T12:53:03.061Z DEBUG modem << +CEMODE: 2
2022-02-20T12:53:03.064Z DEBUG modem << OK
2022-02-20T12:53:03.173Z DEBUG modem >> AT+CNEC=24
2022-02-20T12:53:03.184Z DEBUG modem << OK
2022-02-20T12:53:03.282Z DEBUG modem >> AT+CGEREP=1
2022-02-20T12:53:03.297Z DEBUG modem << OK
2022-02-20T12:53:03.329Z DEBUG modem >> AT+CEREG=5
2022-02-20T12:53:03.348Z DEBUG modem << OK
2022-02-20T12:53:03.392Z DEBUG modem >> AT%CESQ=1
2022-02-20T12:53:03.402Z DEBUG modem << OK
2022-02-20T12:53:03.473Z DEBUG modem >> AT%XSIM?
2022-02-20T12:53:03.487Z DEBUG modem << %XSIM: 1
2022-02-20T12:53:03.502Z DEBUG modem << OK
2022-02-20T12:53:03.521Z DEBUG modem >> AT+CPIN?
2022-02-20T12:53:03.530Z DEBUG modem << +CPIN: READY
2022-02-20T12:53:03.538Z DEBUG modem << OK
2022-02-20T12:53:06.209Z DEBUG modem << %CESQ: 52,2,16,2
2022-02-20T12:53:06.222Z DEBUG modem << +CEREG: 2,"0123","0020DA7A",7
2022-02-20T12:53:07.166Z DEBUG modem << +CNEC_EMM: 18
2022-02-20T12:53:07.194Z DEBUG modem << +CGEV: ME PDN ACT 0
2022-02-20T12:53:07.213Z DEBUG modem << +CEREG: 5,"0123","0020DA7A",7,0,18,"11100000","00000110"
2022-02-20T12:53:07.268Z DEBUG modem >> AT+COPS=3,2
2022-02-20T12:53:07.278Z DEBUG modem << OK
2022-02-20T12:53:07.281Z DEBUG modem >> AT+CGACT?
2022-02-20T12:53:07.284Z DEBUG modem << +CGEV: IPV6 0
2022-02-20T12:53:07.289Z DEBUG modem << 
2022-02-20T12:53:07.291Z DEBUG modem << +CGACT: 0,1
2022-02-20T12:53:07.297Z DEBUG modem << 
2022-02-20T12:53:07.299Z DEBUG modem << OK
2022-02-20T12:53:07.304Z DEBUG modem >> AT+COPS?
2022-02-20T12:53:07.312Z DEBUG modem << +COPS: 0,2,"20416",7
2022-02-20T12:53:07.315Z DEBUG modem << OK
2022-02-20T12:53:07.339Z DEBUG modem >> AT+CGDCONT?
2022-02-20T12:53:07.354Z DEBUG modem << +CGDCONT: 0,"IPV4V6","m2m.public.nl","10.207.79.184 2A01:059D:8162:1442:0001:0001:7E46:09EC",0,0
2022-02-20T12:53:07.356Z DEBUG modem << OK
2022-02-20T12:53:07.321Z DEBUG modem >> AT%XCBAND
2022-02-20T12:53:07.331Z DEBUG modem << %XCBAND: 8
2022-02-20T12:53:07.332Z DEBUG modem << OK
2022-02-20T13:00:16.141Z DEBUG modem >> AT#XUDPCLI=2,"2001:678:6d4:5032::1aef:100",5555
2022-02-20T13:00:16.168Z DEBUG modem << #XUDPCLI: 1,"connected"
2022-02-20T13:00:16.170Z DEBUG modem << OK
2022-02-20T13:00:19.595Z DEBUG modem >> AT#XUDPSEND="Hello"
// ***** ***** This Hello is received successfully!
2022-02-20T13:00:19.612Z DEBUG modem << #XUDPSEND: 5
2022-02-20T13:00:19.614Z DEBUG modem << OK
// ***** ***** But no reply from netcat is ever received
2022-02-20T13:00:50.860Z DEBUG modem >> AT#XUDPCLI=0
2022-02-20T13:00:50.869Z DEBUG modem << #XUDPCLI: 0,"disconnected"
2022-02-20T13:00:50.871Z DEBUG modem << OK
2022-02-20T13:01:43.385Z DEBUG modem >> AT#XUDPSVR=2,5555
2022-02-20T13:01:43.417Z DEBUG modem << #XUDPSVR: 1,"started"
2022-02-20T13:01:43.420Z DEBUG modem << OK
// ***** ***** Also no packet ever received in listen mode
2022-02-20T13:03:15.787Z DEBUG modem >> AT#XUDPSVR=0
2022-02-20T13:03:15.804Z DEBUG modem << #XUDPSVR: 0,"stopped"
2022-02-20T13:03:15.805Z DEBUG modem << OK
2022-02-20T13:04:07.637Z DEBUG modem >> AT#XTCPCLI=2,"2001:678:6d4:5032::1aef:100",5555
// ***** ***** No TCP SYN is ever received on the server
2022-02-20T13:04:31.167Z DEBUG modem << #XTCPCLI: -116,"not connected"
2022-02-20T13:04:31.170Z DEBUG modem << ERROR
2022-02-20T13:12:00.903Z DEBUG modem >> AT#XTCPCLI=2,"2a02:2308:10::c:19",80
2022-02-20T13:12:24.934Z DEBUG modem << #XTCPCLI: -116,"not connected"
2022-02-20T13:12:24.939Z DEBUG modem << ERROR

      Tried various ports, double-checked that firewall is open, still no luck.

      Is IPv6 traffic blocked somewhere?

      Uta 1 Reply Last reply Reply Quote 0
      • Uta
        Uta iotcreators.com team @rxtx last edited by

        Hi @rxtx , sorry for letting you wait. I’ll try to find someone who can help me with answering your question about IPv6 and LTE-M. I’ll be back asap.

        1 Reply Last reply Reply Quote 0
        • K
          Kolja Vornholt last edited by

          I will look into that. In the meantime:
          Have you already tested IPv4 ?

          1 Reply Last reply Reply Quote 0
          • K
            Kolja Vornholt last edited by

            I can confirm the issue. I can reproduce it. The problem occurs not due to LTE-M but due to this specific APN (m2m.public.nl). @Uta will take care of this

            1 Reply Last reply Reply Quote 1
            • 1 / 1
            • First post
              Last post