This is great news, the DragonFly project keeps doing really interesting things. The interview linked elsewhere in the thread give a good overview of how the project is doing. Matthew Dillon mentions in the interview that DragonFly will be able to be much more than an experimental operating system.
Wow I had never seen these devices from Onyx before. Thanks for posting this. I too would be really interested to find out how the phone works in the real world.
I am less interested in the 9" ereaders, but would be interested in finding a 11" panel to put in a chromebook.
They're supporting 4 projects so far: OpenSSL, OpenSSH, NTPd, and an Open Crypto Audit Project (OCAP) audit of OpenSSL. The Network Time Protocol project is here: http://ntp.org/
He zoned out of the world around him and distracted himself with either the project he was working on prior, or just a stream of consciousness around his get-out-of-too-many-words tool of counting
Not the chip in the article, but still a Cortex M0+
http://www.nxp.com/products/microcontrollers/cortex_m0_m0/lp...
These are about £0.71 at single unit quantities and are very hobbyist friendly in a DIP package. Not sure what I will do with them, but I feel the need to buy 100.
Note that as far as I know MCUs from that series don't have an ADC, which can be a real PITA.
Personally, I've switched to using MCUs in QFP packages a while ago. You get a lot more pins, peripherals, speed, etc for the physical dimensions and price. If you decide to make a custom PCB for a project you don't end up stuck with a huge DIP package or having to evaluate and port the software to a new MCU in an SMD package.
QFPs are perfectly easy to hand solder with the right tools, which are in fact really basic: either a temperature controlled soldering station or a hot air station and solder paste.
I'm now experimenting with QFN packages, which reduce cost and size compared to QFP. Hand soldering seems to work ok, but I have yet to see the yield for small batch manual assembly.
We've worked with an assembly house that does manual assembly for small-quantity (10-20) batches. Usually they ask for extras due to attrition, but so far we've not lost any.
I usually check the quality of their assembly under a 20x microscope. I've only found 1 board that had a bit of stray solder between 2 pins which was easy to clean. So, yes, manual assembly seems to work, but that may depend on the assembler proficiency.
Yep, I keep trying to find an excuse to use then, largely though I end up wanting more IO than you usually find in the DIP ARM packages. With a controller as tiny as those in the article, it should be possible to turn it into a 14/16 pin DIP-like; I'm assuming that you could throw an XTAL on the adapter board, or that you can reduce the pins further since there's likely more than one ground and vcc. It would certainly be a nice toy to play with for projects since I usually don't need more than 10 i/o and if I do, i can get away with shift registers when I need more.
This is really cool, I find the microsoft documentation particularly terrible.
I always had a chuckle when the first result for a simple C# concept and the result isn't a MSDN site. I also chuckle when the result is a forum post from 2005 that drops me into a link loop.
Thankfully I won't have to write C# for a long while. I can't say I will miss the MVC stack or the legacy burden you get with forms.
Looks like: IPv6 addresses for NS (nameserver) and MX (mail exchange) records, and root and www subdomain. Looks to check DNS responds to queries over IPv6, too. Easy mode to get at least four stars: enable IPv6 with a free Cloudflare account.
If your VPS provider has it, usually you need to set up the given static address (from a /64), there won't usually be any autoconfig. Sometimes you have to turn it on per VPS in some management settings.
1) make sure your services listen on ipv6 and configure them accordingly if they don't.
Watch out for things like virtual hosts and TLS configuration.
2) Add firewall rules to allow inbound traffic over ipv6 if they don't already exist.
If using ufw (default in ubuntu), check that `ufw status` lists entries for ipv6.
# ufw status
Status: active
To Action From
-- ------ ----
OpenSSH ALLOW Anywhere
80/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
OpenSSH (v6) ALLOW Anywhere (v6)
80/tcp ALLOW Anywhere (v6)
443/tcp ALLOW Anywhere (v6)
Allowing inbound https connections over both ipv6 and ipv4 is as easy as typing
ufw allow 443/tcp
If you're managing your firewall rules by hand, do NOT block icmpv6 as it will break connectivity.
3) add a AAAA record pointing to your vps' ipv6 address to any domain name pointing at your vps.
To find that address, use a command like
ip -6 address | grep global
on your vps.
Make sure the TTL of your AAAA records matches that of your A records.
If you're hosting your own mail server, make sure your MX records point to host names returning ipv6 addresses.
If using SPF, you'll need to add ipv6 addresses to your records as well.
4) Check that your DNS records return both ipv6 and ipv4 addresses, i.e. host should return something like:
$ host www.rackspace.com
www.rackspace.com is an alias for www.wip.rackspace.com.
www.wip.rackspace.com has address 173.203.44.116
www.wip.rackspace.com has IPv6 address 2001:4801:1221:101:1c10:0:f5:116
Changes in DNS can take time to propagate (depending on the TTL of your records), so give it a couple of hours if records don't show up right away,
5) test that your services are reachable and working as expected over ipv6.
You can use ipvfox (firefox) or ipvfoo (chrome) to make sure that ipv6 was indeed used to reach your web server.
curl -6, ping6, telnet -6 are also good to test/debug.
To see what services are listening on ipv6, use nmap to run a portscan (from a different machine than the vps itself).
nmap -6 -P0 -T4 -p0-65535 <domain name or ipv6 address>
6) if you have any kind of monitoring set up to check on your ipv4 services, add monitoring checks for ipv6 as well.
Way too often people forget about this and are not notified when their ipv6 setup breaks.
