Driver bug for AX88179 on pfSense 2.2



  • I bought a couple Trendnet USB3 Adapter (AX88179) to use in two news installation with Intel NUC (NUC5i3RYK), since I needed two Gbit interfaces in each gateway. FreeBSD 10.1 supports this chipset, so do pfSense 2.2.

    However I'm having a issue that I consider a bug.
    The interface using the AX88179 resets every other hour in a softer way but I still lose network access for a few seconds.
    Talking about that on FreeBSD forum, some people say that FreeBSD 10.1-STABLE fix the problem.
    I'm having a hard time to figure out what FreeBSD version the pfSense 2.2 uses. What 10.1-RELEASE-p4 means in terms of FreeBSD version. There's no explanation about that on BSD's Website.

    Yesterday i downloaded the 2.2.1 devel version to test (uses 10.1-RELEASE-p6) and the problem is the same.

    Somebody was any idea if in any point the 10.1-STABLE will be used. It appears to me that they never use the stable versions on pfSense. It's always somethings customized. am I right?  Any ideas how to get this bug to the pfSense Developers?

    FreeBSD Bugzilla fixed: 195811

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195811

    Versions:
    Stable:

    FreeBSD gwaus.XXXXX.org 10.1-RELEASE-p4 FreeBSD 10.1-RELEASE-p4 #0 36d7dec(releng/10.1)-dirty: Thu Jan 22 15:12:35 CST 2015    root@pfsense-22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10  amd64

    Devel:

    FreeBSD gwaus.XXXXX.org 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0 b69ba8f(releng/10.1)-dirty: Thu Mar  5 01:07:05 CST 2015    cmb@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10  amd64

    Loggging:

    Mar  4 15:58:17 gwaus check_reload_status: Linkup starting ue0
    Mar  4 15:58:17 gwaus kernel: ue0: link state changed to DOWN
    Mar  4 15:58:17 gwaus kernel: ue0: link state changed to UP
    Mar  4 15:58:17 gwaus check_reload_status: Linkup starting ue0
    Mar  4 15:58:18 gwaus php-fpm[92691]: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.13.1 )
    Mar  4 15:58:18 gwaus php-fpm[92691]: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.13.1 )
    Mar  4 15:58:18 gwaus check_reload_status: rc.newwanip starting ue0
    Mar  4 15:58:19 gwaus php-fpm[92691]: /rc.newwanip: rc.newwanip: Info: starting on ue0.
    Mar  4 15:58:19 gwaus php-fpm[92691]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.13.1) (interface: LAN[lan]) (real interface: ue0).
    Mar  4 15:58:19 gwaus check_reload_status: Reloading filter
    Mar  4 16:34:40 gwaus check_reload_status: Linkup starting ue0
    Mar  4 16:34:40 gwaus kernel: ue0: link state changed to DOWN
    Mar  4 16:34:40 gwaus kernel: ue0: link state changed to UP
    Mar  4 16:34:40 gwaus check_reload_status: Linkup starting ue0
    Mar  4 16:34:41 gwaus php-fpm[92691]: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.13.1 )
    Mar  4 16:34:41 gwaus php-fpm[92691]: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.13.1 )
    Mar  4 16:34:41 gwaus check_reload_status: rc.newwanip starting ue0
    Mar  4 16:34:42 gwaus php-fpm[92691]: /rc.newwanip: rc.newwanip: Info: starting on ue0.
    Mar  4 16:34:42 gwaus php-fpm[92691]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.13.1) (interface: LAN[lan]) (real interface: ue0).
    Mar  4 16:34:42 gwaus check_reload_status: Reloading filter


  • Netgate Administrator

    @alamaral:

    Somebody was any idea if in any point the 10.1-STABLE will be used. It appears to me that they never use the stable versions on pfSense. It's always somethings customized. am I right?  Any ideas how to get this bug to the pfSense Developers?

    All pfSense versions are built on the release versions of FreeBSD which are the most stable. Some thing do get included from a newer version if an important new feature or bug fix has been added. For example the 2.2.1 release will have the run(4) driver from 10-stable because it included a bug fix.

    The way to get this included is to open a bug at redmine.pfsense.org. Since this is a known bug with an easily available fix there is a good chance of it being included. No promises though, USB NICs are generally frowned upon!  ;)

    Edit: I see you've already done that. https://redmine.pfsense.org/issues/4494

    Steve


  • Netgate Administrator

    Replying to myself…
    Having looked at the source, as I see you and Chris also have, there appears to have been no change to the axge driver in stable since 10.1-rel. Even looking in HEAD the only changes don't seem relevant to this. If it really is able to run under 10.1 stable it's down to some other change, possibly in the USB subsystems.

    Get a FreeBSD 10-stable stable snapshot and boot that. Test your USB NIC there.
    ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/10.1/

    Steve



  • @alamaral:

    However I'm having a issue that I consider a bug.
    The interface using the AX88179 resets every other hour in a softer way but I still lose network access for a few seconds.

    I'm having the same issue with a USB 2.0 adapter and AX88772B chipset. Any chances there will be a bugfix for the AX chipsets or any ideas where to tweak to have a workaround for this issue?



  • Follow Stephen's advice and test it under stable. If the nic works fine under FreeBSD-stable, report this on the open redmine ticket.