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

    2.1-RELEASE shutdown hangs with USB 3g dongle

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    2 Posts 2 Posters 1.4k 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.
    • T
      tullo
      last edited by

      Hello everyone,

      this is my first post so please be patient with me. First I would like to thank all the developers for the super job performed with pfSense, it is a GREAT firewall!!!!

      I am using pfSense at home, with a WAN connection through a USB 3g dongle.

      After upgrading from rel 2.0.3 to 2.1 I have noticed that the shutdown process hangs and I am forced to perform a hardware shutdown through the power button.

      After searching out in the web I have found a similar issue on FreeBSD 8.3 ( see here: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/167685)

      To overcome the problem I have inserted, as suggested in the post, a line on /boot/loader.conf of my pfSense installation:
      hw.usb.no_shutdown_wait="1"

      This prevents the init process to hang on waiting for usb shutdown process completion and the computer shuts down smoothly.

      I wanted, first of all, to share this with all the others that might have encountered the same issue and secondly I would like to ask developers whether in their opinion this kernel setup may be considered safe (e.g. correct disconnection of 3g wan link, no other issues introduced etc.).

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

        It looks like that is actually a sysctl rather than a loader tunable, as such you should be able to add it to the table in System: Advanced: System Tunables: This will mean it gets added to the config file and will survive a firmware update.

        Steve

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