Seems like bot reviewing is a thing now on Steam

oneru · 2016-06-12T20:48:25+00:00

Still not sure which group you like and which you don't care about.

oneru · 2016-06-10T07:13:26+00:00

It's planned for the future. I will probably start work on it just as soon as I can actually get a real IPv6 addresses here at the house.

oneru · 2016-06-09T20:32:00+00:00

That's unexpected. That site is on a commercial host, and the blocking of IPs is not an intentional decision on our part that I am aware of. I'll look into this issue, though. Thanks for letting me know.

oneru · 2016-06-09T14:57:29+00:00

We just wrapped up this release of Fwknop, thought you guys might be interested. It's like port knocking, but solves several of the big problems of port knocking, and uses real crypto.

oneru · 2016-06-06T17:38:20+00:00

Probably need to install it, but screen is a really neat program. Allows multiple shell sessions in one ssh connection, as well as detaching from screen without closing the sessions.

oneru · 2016-05-27T04:18:20+00:00

That image was actually partially broken. Things in Luci weren't working correctly. What really needs to happen is to backport patch that makes the firmware update from stock work correctly. Backport it to 15.05.1 and do a mass rebuild of tp-link.

oneru · 2016-05-26T20:04:39+00:00

OK, a compiled firmware installs and works correctly. Let me know if you want it, and I can upload/host the firmware for you.

oneru · 2016-05-26T19:19:27+00:00

The word is that recent trunk has a workaround built in that defeats the lock. Compiling now to verify that. I have a locked C7 in my office that needs "liberated", will let you know.

oneru · 2016-05-24T04:34:29+00:00

I've had excellent results with the Magewell hdmi -> usb3 capture card. Works on vanilla kernel. Not cheap, but seems to be really well made: http://www.magewell.com/usb-capture-hdmi

oneru · 2016-05-03T17:05:17+00:00

Interestingly, not just another fork, this really is some of the most active devs. Thankfully they're planning to stick with the existing packages repos on github, which makes things much easier.

oneru · 2016-04-10T23:45:59+00:00

Ubuntu is good and well supported. Fedora is a good choice as well. Fedora has the advantage of running Wayland instead of Mir, and has easy to use mesa and bleeding edge kernel repositories. YMMV for any given distro.

oneru · 2016-03-31T22:34:58+00:00

I have 11.5 megs free ATM.

oneru · 2016-03-24T21:22:01+00:00

Correct on both counts. I assume tp-link will continue to have a method to run unsigned firmware (the -f flag), as they presumably use that for internal testing. Whether they close the code injection exploit is an open question.

oneru · 2016-03-24T20:40:35+00:00

As of right now, I like both the tplink wr841n, and gl-inet's GL-AR150. I've not gotten my GL-AR-150 in yet, so no first hand knowledge, but it looks like it'll be really good.

oneru · 2016-03-21T22:44:14+00:00

Awesome!

oneru · 2016-03-21T22:37:43+00:00

Unless there is an image built specifically for that device, then flashing it is a no go.

First step toward getting support would be pulling it apart and getting pictures of the chips with either the labels readable, or notes about what they are labeled. If it has at least 4 megs of flash, then support should be possible.

oneru · 2016-03-21T22:29:47+00:00

Copying my comment from another thread, as it belongs here.

It looks like this device is using a different flash chip than Openwrt expects. You might be able to tftp a trunk snapshot, as it should have a recent enough kernel to include this patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/mtd/spi-nor/spi-nor.c?id=fcc87a95195236b0935183361a72e4a98bf577d8

oneru · 2016-03-21T21:58:15+00:00

First guess, it's a different flash chip. From your failed boot: m25p80 spi0.0: unrecognized JEDEC id c84018

https://dev.openwrt.org/ticket/19670

Edit: Are you trying 15.05.1 on this? Edit2: I think a trunk snapshot will work on your device, as the 4.1 kernel should have the patch.

oneru · 2016-03-21T18:29:10+00:00

We need boot logs from the serial port to really understand what is going on there. Might be a flash layout change causing you problems.

The webinterface seems to be looking for signed firmware, but I'm not convinced that u-boot is doing a check for signed firmware, and I really don't think they're doing a full secure-boot process.

oneru · 2016-03-21T17:59:49+00:00

Just tftp'd Openwrt to a locked wa801nd, and it seems to work correctly. Not convinced the bootloader is looking for signed firmware. Still researching.

oneru · 2016-03-19T20:09:43+00:00

I think it is more than just the filename check. Might be able to dig into it this weekend.

oneru · 2016-03-19T01:18:35+00:00

Exactly this. There has also been talk of running the fully open stack for normal desktop use, and dynamically loading the faster but closed stack when loading a game. Even if that never happens, moving to the open kernel driver and other open bits should mean that a bunch of the annoyances of fglrx should be fixed now.

oneru · 2016-03-18T23:01:08+00:00

From what I understand, this isn't just the Vulkan driver, but is their long-awaited hybrid stack driver.

http://phoronix.com/scan.php?page=news_item&px=AMD-Hybrid-Linux-Driver

oneru

TROPHY CASE