Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Bad LTE performance after reboot (Huawei ME909s-120)

    Scheduled Pinned Locked Moved Wireless
    17 Posts 3 Posters 1.8k Views
    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.
    • D
      darkred
      last edited by darkred

      I have now tried all three variants - without success. The modem does not connect this way. Is there perhaps an error in the command?

      /bin/echo "AT^RESET" > '/dev/cuaZ99.1'.
      

      Do shell scpits in /usr/local/etc/rc.d/ directory start later than the commands in shellcmd?
      I will test something like:

      /usr/local/etc/rc.d/modemreset.sh:

      #!/bin/sh
      sleep 60
      /bin/echo "AT^RESET" > /dev/cuaZ99.1
      

      Regards

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        The timing is probably not much different. I would check the system logs for errors during boot that might indicate the interface is unavailable at that point.

        You probably don't need to sleep at that point but after the reset. More like:

        #!/bin/sh
        /bin/echo "AT^RESET" > /dev/cuaZ99.1
        sleep 60
        /etc/rc.linkup opt1 up
        

        Steve

        1 Reply Last reply Reply Quote 0
        • D
          darkred
          last edited by

          Hi Steve
          I tried it (changed the interface).

          #!/bin/sh
          /bin/echo "AT^RESET" > /dev/cuaZ99.1
          sleep 60
          /etc/rc.linkup ppp0 up
          

          Sadly with no success..
          After the reboot the system trys to reconnect in an endless loop...
          57ef4f26-10fc-4b31-9eaa-f38f8dd756cf-image.png

          But then, if I place the following command over cron or putty, it connects successfully...

          /bin/echo "AT^RESET" > '/dev/cuaZ99.1'
          
          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Ok but key in that log is that the port you are trying to use does not actually exist.
            So what does exist at that point? Has it rearranged the ports so that is now cuaU1.0 for example?

            Does it not in fact see the modem at all so no ports are created?
            In which case you might try using usbconfig to retrigger that process after the reset.

            Steve

            1 Reply Last reply Reply Quote 0
            • D
              darkred
              last edited by

              The problem is that I can't connect to the firewall during log output (is remotely connected via VPN). I wait until the next reset is done by cronjob. After that it runs again. But I will try to check this on site.
              Then I would have to check in the shell which cua* devices are visible? What is the best way to do this? And how could I do the reset with usbconfig?

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Yeah check the system log. Look in /dev.

                Use usbconfig -d ugen0.2 reset or whatever the device is.
                See: https://www.freebsd.org/cgi/man.cgi?query=usbconfig

                Steve

                1 Reply Last reply Reply Quote 0
                • D
                  darkred
                  last edited by

                  Hi Steve
                  Sorry, I had a lot to do the last Days. But now I tested wirh usbconfig. Sadly the same effect. If I set the command manually in the running system - it works. But if I use it as part of shellcmd the system does not connect to the modem.... I have no Idea what I can do. Currently I have an cron once a night, which runs "/bin/echo "AT^RESET" > '/dev/cuaZ99.1'". Thats working but is not a very nice solution.
                  Regards

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Well it looks like a timing issue so you should be able to set something that runs at boot, waits for the interfaces to be detected and the modem to cone up and then sends the AT reset. It's just a matter if finding the correct timing and using a command that doesn't prevent other things running while it waits.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • N
                      nblind
                      last edited by

                      Hi Darkred,

                      Does adding a boot delay to /boot/loader.conf help?

                      loader_delay="40"
                      

                      I had to add a delay on my apu4d4. I followed these instructions:
                      https://teklager.se/en/knowledge-base/pfsense-lte-troubleshooting/

                      Br,
                      nblind

                      D 1 Reply Last reply Reply Quote 0
                      • N
                        nblind @darkred
                        last edited by

                        What can be the reason for this, or what can I do about it? I have already set the loader_delay to "40" - but it does not help.

                        I now see that you already did that.
                        I did not read carefully enough, sorry.

                        Br,
                        nblind

                        1 Reply Last reply Reply Quote 0
                        • D
                          darkred @nblind
                          last edited by

                          Hi @nblind
                          Thank you for your support.
                          I have already implemented the delay, that is correct. Unfortunately, my problem still exists. Currently I use a workaround. I reboot the device once a night and start a reset of the modem via cron 10 minutes later. So it works - for whatever reason.....
                          Best Regards

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.