Date: Sun, 4 Nov 2018 17:10:59 -0700 From: Warner Losh <imp@bsdimp.com> To: Mike Andrews <mandrews@bit0.com> Cc: cederom@tlen.pl, "freebsd-usb@FreeBSD.org" <freebsd-usb@freebsd.org> Subject: Re: umodem0, Cisco USB serial console, and quirks Message-ID: <CANCZdfrkGZQWbYUK-xUbq6wBZmkz5k10p11ADkrn8VHASAhmqA@mail.gmail.com> In-Reply-To: <alpine.BSF.2.21.9999.1811041851500.98957@beast.int.bit0.com> References: <alpine.BSF.2.21.1709191021260.34953@beast.int.bit0.com> <d9dbef0b-c22e-c7ea-34a2-f36e9e768745@selasky.org> <alpine.BSF.2.21.1709191205280.1218@beast.int.bit0.com> <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> <alpine.BSF.2.21.1709262210180.33243@beast.int.bit0.com> <33f3a1f8-69d1-9240-6381-8a851beb97d0@yandex.ru> <18d57cbe-1235-aedf-45e6-e36b495ca1eb@bit0.com> <15cff2a5-021f-49e5-b287-37a14a9321b3@selasky.org> <5d0a544d-517c-2fb9-84e8-d87704474cce@yandex.ru> <5cdb37b5-fca1-99db-cacc-cf72f0cee0df@selasky.org> <51ae0fc4-7e93-30d6-caa3-393afbe278b6@yandex.ru> <bbdda4ab-567f-2658-b83e-5bf0e1176e9a@selasky.org> <CANCZdfqoC8QaDDRP0QoYO0C1WvT_EBmNC8UXAzG-GEbaoK0Xyg@mail.gmail.com> <0dd7b89f-6a82-1d6e-0d0a-4f2b9515bd5d@yandex.ru> <CAFYkXj=PzMx3TKSLPNvcLT3=3mUTFkcpRftFGh9MxB4_o7-RCw@mail.gmail.com> <alpine.BSF.2.21.9999.1811041851500.98957@beast.int.bit0.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 4, 2018 at 5:06 PM Mike Andrews <mandrews@bit0.com> wrote: > On Fri, 2 Nov 2018, CeDeROM wrote: > > > Try to add VID/PID of your device into a usbmodem driver. Use > > configurations to see which one works with your device. Rebuild the > > module/kernel, reboot, try it out untill success. > > > > After your device is recognised by usbmodem and creates several cuaU* > > devices.. still Your device may require uploading a specific firmware > > in order for gsm modem to work. You can find those in Windows driver > > package. > > > > Use MINICOM for cuaU communications that would save you a debug time. > > > > That works for me - added 3 devices like that with no problem. In fact > > they work better on FreeBSD than Windows ;-) > > > > > > Alternartively, replace your modem with something that is known to > > work - for instance QUECTEL EC25 LTE module works far better than my > > previous stock 3G module here.. > > I think we're losing the plot here a bit. > > While this is generally useful advice, this thread was originally about > the USB serial console port of Cisco ASA firewalls. It should just be a > plain ol' USB-to-serial setup. No actual modems of any kind involved, > especially not cellular ones. > > I suspect we shouldn't even be loading umodem at all -- just ucom. But > for some reason, umodem gets loaded when I plug the thing in. With just > an FTDI serial-to-usb adapter in there, umodem doesn't just, just ucom. > No. ucom is a back end for all the bazillion different USB Serial chips that all do something different... The problem is there *IS*NO*STANDARD* here. At least not one in the universally followed sense. So, there's necessarily some code for each new thing that comes along. Without access to a Cisco ASA Firewall, all we can do is speculate about what you might need to do to get it working. It may be as simple as adding something like the VID/PID to the right uXXXXX driver. It may be something more complicated. > These firewalls (and I suspect all of Cisco's newer routers and switches) > have both normal serial and mini-USB-to-serial ports, and you can connect > a simple USB-to-serial converter (PL2303, FTDI, etc) into the normal port > and of course that works fine on FreeBSD. But it would be nice to skip > needing the dongle... > I agree. It would be nice. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrkGZQWbYUK-xUbq6wBZmkz5k10p11ADkrn8VHASAhmqA>