TP-Link M7350 v4 4g "modem" "router".

  • Hi guys.

    I picked up a TP-Link m7350 v4 today because of my internet provider is such a a**hole that they have not succeeded to send a technician to my house to connect the adsl line into my house.

    I noticed right away when i plugged it into my iMac with usb that it came up as a ethernet device.

    I tried getting it to show up as an ethernet device on the pfsense to run it as a wan while my provider gets his head out of his ass but the pfsense won't show me the interface.

    I have done some research and found out that the ethernet "module" via usb is a RNDIS service.

    Is it possible to get it up and running in pfsense or is it just impossible?

    Really need help with this one.

    Hope you have a great weekend all!

    Best wishes!

  • Netgate Administrator

    You might be able to.

    You can extract the rndis kernel module (if_urndis.ko) from the equivalent FreeBSD version and load it into pfSense. There are a number of threads covering that.

    Check the usbconfig output for the device though to see if it exposes a urndis device.


  • Thanks for the reply stephenw10

    I saw some of the urndis threads but i didn't find any that explained enough how to get the kernel module over to pfsense, read also something about a system panic and something like that if the kernel was used, is that an issue?

    Could you help me/point me in the right direction if it is not a system panic issue to use it.

    Best regards! :)

  • Netgate Administrator

    So first get the kernel from the appropriate FreeBSD ISO, so 11.1 64bit if you're testing against pfSense 2.4.X.

    Copy the file to /boot/modules using SCP (WinSCP in Windows for example).

    Then add the following line to /boot/loader.conf.local:


    I would not expect a kernel panic. The biggest issue is from disconnecting the modem whilst it's in use. pfSense does not like to have interfaces removed like that.


  • Just wanted to share that I successfully connected my M7350 v3 box via USB to my pfSense 2.4.3.
    After following the above steps, the interface showed up as ue0 and I could continue adding a new Interface in pfSense.
    No kernel panic indeed 👏 .