you can use coaxial cable if you are using it for testing or education. so you don't "pollute" the legit GSM communications.

You can and I've recommended it but it's not that trivial either the path loss in coax signals as well as some other factors might not work with all SDR's and RF equipment and it takes a bit more legwork to set up.

Dumb question ... with coax, do you need an SDR board anymore? I assume not since you can do everything in CPU? Or is there some specialized acceleration you get with Silicon. Complete newb here.

The Coax is just a media for the radio wave to propagate through for all intents and purposes for this experiment it's no different than vacuum it's just a piece of cable you still need a transmitter and receiver to actually generate and receive the radio signal as well as a DAC of some sort to connect it to the PC :)

Basically if you do it via direct coax you basically connect a coax cable to the micro bnc port on your SDR (to which the regular antenna coax cable would connect) and the other end has to be connected to the BNC connector on the device that is talking to you radio, some phones have BNC connectors for testing (older phones used to have it to connect to the car phone fixture for better signal) but for some you'll have to solder a connector manually to the phone board or have some setup to connect to whatever custom connector the phone uses to connect to the antenna.

I know that the iPhone 6/s plus for example has a micro bnc connector for the Wifi antennas but I can't recall what they use for the GSM one but it's either going to be bnc or some custom connector if they are using some fractal antenna printed on flex cables or one that is embedded into the case which is quite common these days.

EDIT: Correction the connectors on the LimeSDR and on most phones are U.FL not BNC, I just have a habit of calling all Coax/RF connectors BNC so if this incorrect in some other post apologies :P

ARGGGG EDIT #2: Apparently the iphone (as well as some other phones) use some "custom" connectors that mechanically look like U.FL but are smaller, so FML and good luck finding a cable to connect to it.

That's a really good idea, btw

I hope they will rewrite awscli with it. Today it's quite painful to run it on coreos (python/pip ran in a container)

Why is it painful?

Because if not run in a container, you should put things that upgrade Requests in a venv at least otherwise you may end up breaking apt.

But shouldn't you always use a virtualenv anyways?

Project-wise? - Most definitely! Globally? - Not common practice, but also preferred to avoid collisions.

You might consider taking a look at Twitter's pex. Python supports importing and running code from zip files. pex aids in bundling python code and its dependencies into an executable zip file.

Unfortunately that's simply not the same. Python libraries many times still require header files to be present, which means on a host you want to install PyOpenSSL you must also install libssl-dev, which means you also much install python-dev... etc etc. Don't get me started on using gevent.

A container is the only sane way to package a python service, but that's not _nearly_ as convenient as a statically compiled binary.

Legacy CentOS too

Strange they dont mention AES-CCM at all. I'm using it a lot in IoT applications (dtls). It's not frequent in the "web" world?

~20fps on my nexus 9 (chrome)

more details: http://www.javaworld.com/article/2692491/mobile-java/arms-mb...

a bigchunk of the announced new parts are not going to be opensourced (like the server and some part of the IP stack)

yes it's kinda broken when you know all the existing alternatives: contiki OS, RIOT OS, openwsn, and for LWM2M eclipse wakaama and (shameless plug:) Leshan in place of the mbed server.

you can export the project to use gcc, it's packing you a zip with make files and linker scripts example: https://github.com/jvermillard/Wakaama-mbed

+1 This one is really good, showcasing code, graphics and formula for each lesson. So even if you don't understand totally the mathematical notation you can still read the code. I managed to learn DSP without an EE degree mainly with this book.

For HTTP/TCP it's not helping much but it could be very interesting for the IoT protocols like CoAP (RFC7252) which is UDP based.

Anyway I suppose the main target of this project is to help developers of packet switching and load balancing software.

If it's easy enough to use, it might be interesting for other too. To give an example: my own project is a message processing system as a service, intended for (among others) the massive amounts of data that come from IoT gateways or devices. While we're not quite there yet, we do intend to be able to handle loads that would require this kind of performance. In some applications, millions of messages per second aren't out of the ordinary.

If this kind of library can help us do that, that could save us a lot of time and effort. Time we could use to work on the next bottleneck :)

It is pretty easy to use, as it is largely scripted in Lua, and the code is small and easy to follow. It does depend what you want to do with the data once you receive it though.

Most likely, split it up and feed it to a distributed internal system that can handle the data with slower processing than the single machine can.

That sounds like a pretty easy application then, just rewrite some addresses and put back out on the wire again (hardware should do checksum offload). Probably a bit more to it but definitely worth giving Snabb a go for that.

Quite a bit more to it, but it does sound like it could be a fit. We'll give it a try when we get to the point where our regular intake methods aren't enough :)