Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Aircard 313U showing up as a "USB Mass Storage Device"

I know this may not go anywhere, but I just finished transitioning to XG from UTM 9 and tried once more to get a Sierra Wireless 313U Aircard working. Now, with UTM 9 it did recognize it but I could not get it to work and eventually put it aside.

So, after seeing this entry in the USB compatibility list, I thought I would give it another try:

 

Sierra Wireless AC313U AT&T US LTE CAT3 1199:0fff 0f3d:68aa Possible

 

So after plugging it into the system, I then see the following in the admin screen:

 

Ok, not sure why that happened, but I do know there is a small amount of space on the Aircard that holds clients for people to install in order to use it, so I think XG is only seeing that mass storage device and not the modem itself which appears as a separate USB device

Now the odd thing, I have seen a community post of someone getting the Aircard 340U working but then the compatibility list shows it as follows:

Sierra Wireless AC340U AT&T US LTE CAT3 1199:0fff 1199:9051 Not compatible

So, I'm at a loss of what to do. At the moment, I can get a 340U for pretty cheap so I am inclined to go that direction and chuck the 313U out the window. If anyone has any steps that can get this to work, I would love to try them out.

 

Thank you in advance!

 

 



This thread was automatically locked due to age.
Parents
  • An update to this issue.

     

    I have access to a Sophos XG125 and I figured I would see if it could see either of the modems on a piece of actual Sophos hardware vs the Dell R210 I am running XG on at the moment.

     

    When I plugged in the 313U AirCard, it immediately recognized it and I was able to connect to T-Mobile's network without issue and even pinged a remote host (in this case Google) working without a hitch. I also tried the 340U AirCard and following some of the directions in the post I found got the same result as the 313U.

     

    So the question I have (and I would sure love to hear from the Sophos engineers) is why their hardware can detect both the 313U & 340U AirCards and why on non-Sophos hardware (in this case a Dell R210 server) do we get the above-mentioned problem of it only seeing the small USB drive on it with clients?

    Is there a way to have it point to the right place or am I pretty much SOL as far as using XG on the server I have and would need to go to Sophos hardware to get it to work?

     

    Any help would be greatly appreciated!

Reply
  • An update to this issue.

     

    I have access to a Sophos XG125 and I figured I would see if it could see either of the modems on a piece of actual Sophos hardware vs the Dell R210 I am running XG on at the moment.

     

    When I plugged in the 313U AirCard, it immediately recognized it and I was able to connect to T-Mobile's network without issue and even pinged a remote host (in this case Google) working without a hitch. I also tried the 340U AirCard and following some of the directions in the post I found got the same result as the 313U.

     

    So the question I have (and I would sure love to hear from the Sophos engineers) is why their hardware can detect both the 313U & 340U AirCards and why on non-Sophos hardware (in this case a Dell R210 server) do we get the above-mentioned problem of it only seeing the small USB drive on it with clients?

    Is there a way to have it point to the right place or am I pretty much SOL as far as using XG on the server I have and would need to go to Sophos hardware to get it to work?

     

    Any help would be greatly appreciated!

Children
No Data