Posted by fli in Tech, tags: FreeBSD, hsdpa, hso
New release of hso(4), FreeBSD driver for Option iCON branded 3G/HSDPA devices.
Changes to hso(4)
- Support for the new TTY layer, driver now works with 7.0 upto todays 8.0-CURRENT.
- Device IDs for Option GlobeTrotter HSUPA and Option GMT382 added.
- Minor performance and stability issues have been addressed.
Changes to hsoctl(1)
- hsoctl now forks into background upon a successful connection, the old behvaior can be obtained with -n flag. Disconnection is possible by executing hsoctl -d hso0. While running in background, important information is logged to syslog. Complete daemonization is also possible with the -b flag.
- Use of AT+CGREG in addition to AT+CREG to detect network registration (for service plans where voice calls are disabled).
- resolv.conf handling have been improved, only nameserver entries are changed, other content is left intact. A bug that sometimes caused garbled data to be prepended to resolv.conf have also been addressed. The resolv.conf path can be altered with the -r flag, disable resolv.conf with -r /dev/null.
- hsoctl does now gracefully terminate upon unexpected device removal.
- Default route installation have been improved.
The code can be obtained from the hso page, the update should hit the ports tree soon (comms/hso-kmod).
Speed test from a rural location. Values are in bits/s, so that’s almost 300 kB/s downstream and around 40 kB/s upstream. Hopefully downstream is slightly better from a more urban location.

hso(4) speedtest
This entry was posted on Thursday, October 23rd, 2008 at 12:40 pm and is filed under Tech. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.
A possible addition to hsoctl would be a fifo to inject commands to the device, or to at least drop the output of commands like AT+CSQ to.
Lots of people would like to send a command to the device to read device information from it.
Would you object to this driver being committed into FreeBSD as a full driver? From a quick glance the driver is BSD licensed, right?
I would need to test it before committing and that would take still some time, but it would definitely be big win for the FreeBSD project.