GoPro HERO3+ Wifi connection troubles with Cyanogenmod

Today I decided to pull out my old Hero3, after updating it to the latest firmware I was surprised to find that the GoPro app would not connect successfully. What I found was that for whatever reason, the DHCP request from my mobile device (OPO in my case) was not received and or accepted by the camera, and no IP address was found. After some probing around I discovered that these cameras default to the 10.5.5/24 network.

So the solution was simple, in my wireless settings for the AP on the mobile device I manually configured the IP address to live on the 10.5.5/24 network by assigning it the IP address The gateway and DNS are also assigned to however I don’t believe this makes any difference on these devices.


Importing .sdtid files with stoken

So this morning I was kindly reminded again by my corporate IT overlords that my RSA soft token was going to be expiring in 9 days. Having had this token in place for a year now I had forgotten how to update it.

After a few minutes I recalled that the trick was as simple as

stoken import --file <my>.sdtid

Well that’s simple, except for the fact that in my case, this failed. After a quick bit of googling around I found that version 0.2 (which ships with my release of ubuntu) incorrectly identifies where the tokens are within the sdtid files resulting in an annoying error:

error: no valid token in file '<my>.sdtid': General failure

UGH! Well the solution is simple here. After a quick upgrade to 0.90 I’ve had no problems importing since.

Infiniband Tips and Tricks

Below are some commands I’ve found useful when dealing with infiniband and related issues.

Determine port state on all ports available within the fabric

The command ibnetdiscover command will show you the state of each port in the the fabric. It’s a good idea when running this command (on any node) to redirect the output into a file (especially if you have a large number of ports)

Determine indivudual port information

The ibportstate command can provide additional port information once you have the LID (available from ibnetdiscover)


ibportstate -L <lid> query

Determine current node description

smpquery nodedesc 1

Enable / Disable a port

ibportstate -L <lid> -P <port> enable
ibportstate -L <lid> -P <port> disable

Windows 7 dropping connections to SMB services regularly

One thing that’s been constantly bugging me, as well as my wife is the fact that in general, Samba (SMB) connectivity from our Windows 7 machines is spotty at best. In general we can connect, and transfer data to and from our ZFS file server. However at seemingly random times the transfers fail, or the shares become unavailable. This is extremely frustrating especially when doing something like streaming music.

After some digging around I found the SessTimeout variable which is described as:

Determines the duration of the secondary delay used in calculating a time-out value for outstanding operations. If the redirector does not receive a response to an outstanding operation before the resulting time-out expires, it considers the operation to have failed. The value of the SessTimeout entry can be thought of as a margin for error. If there is an unexpected delay, the redirector permits the operation this extra time to complete.

Sounds promising…. So I popped up regedit on the windows workstations and added the DWORD entry SessTimeout in:


To a value of 300. After that no more timeout issues! Whoohoo! Finally!

Juniper NCSVC and Linux 3.19

So interestingly I noticed that as soon as I upgraded to the 3.19 kernel (RC5 in my case) I was no longer able to connect to any internal machines on my corporate VPN.

Interestingly my private OpenVPN services still all functioned correctly.

In the 3.19 kernel there have been many changes to the network infrastructure so likely something there broke my VPN. It could also be a problem with the way exported routes from my corporate VPN. I’m not sure but I do know it doesn’t work right.


Well it’s been a busy few weeks. I still haven’t run down which commit broke this, however given the amount of comments from all of you, it seems to be a problem for many more people than myself.

One thing I did suspect was a possible mishandling of certain packets generated by vpnc as multi-cast, unfortunately this didn’t pan out, so further investigation is still required.


It seems from 4.5 forward (including 4.6 which I’m running now) This is broken yet again.

EeePC wireless performance

After updating my 1005PE with an Intel 6300 network card and additional antennas I wanted to see how fast a real world copy could be through wireless.

So I hopped on my internal file server and a large file

Intel 6300 speed test

9.88 MB/s or about 80 MBps through an SSL web host. Not bad…

The next few tests I’ll try will be lower level trials sourcing data from a memory disk.

Tune your wifi channel if you’re apartment living!

One thing I’ve noticed living here in this apartment is the shear number of wireless networks that propagate throughout my space. Personally I could care less what or where this signal comes from or goes to, however it does present a bit of a problem for reliability.

This is due to the fact that so many people tend to utilize the same channel (sub frequency) for their wireless networks that things get messy fast. I’ve seen everything from slow and unreliable wireless (feet away from the access point) to access point failure due to it having to negotiate so many other active access points sharing the same channel.

There is a solution and it’s quiet simple. In Linux using iwlist tool you can quickly pull a list of active networks around you, from there you can find (if you’re lucky) an unused channel, or at the very least the least used channel. Once you’ve discovered this change your router configuration, reboot if necessary and enjoy your much more stable and reliable connection.

$ iwlist wlan1 scanning | egrep 'ESSID|Channel' 
                    Frequency:2.412 GHz (Channel 1)
                    ESSID:"FBI Surveillance Van #13"
                    Frequency:2.412 GHz (Channel 1)
                    Frequency:2.412 GHz (Channel 1)
                    ESSID:"erics wire"
                    Frequency:2.412 GHz (Channel 1)
                    Frequency:2.412 GHz (Channel 1)
                    Frequency:2.412 GHz (Channel 1)
                    Frequency:2.412 GHz (Channel 1)
                    Frequency:2.427 GHz (Channel 4)
                    Frequency:2.432 GHz (Channel 5)
                    Frequency:2.437 GHz (Channel 6)
                    Frequency:2.437 GHz (Channel 6)
                    Frequency:2.437 GHz (Channel 6)
                    Frequency:2.437 GHz (Channel 6)
                    Frequency:2.462 GHz (Channel 11)
                    Frequency:2.462 GHz (Channel 11)
                    Frequency:2.462 GHz (Channel 11)
                    Frequency:2.462 GHz (Channel 11)
                    Frequency:2.462 GHz (Channel 11)
                    Frequency:2.462 GHz (Channel 11)

As you can see, channel 4 was available so I snatched it up (even though it’s overlapping), channels 1,  6 and 11 being extremely busy as they’re the the only non-overlapping channels available, so they’re set by default on most consumer access points.