The functions of such a device might include,

• Easy configuration (via web interface) and use
• NAT to mesh network addresses
• 3 types of ports/interfaces (NAT to mesh network addresses)
  • LAN (with DHCPd, NAT, etc)
  • Mesh (for the radios and wired links to the mesh network fabric)
  • Internet/WAN
• Auto-peering
• Support for multiple routing protocols 
  • OLSR
  • cjdns
  • batman-adv
  • I2P
  • etc
• Configuration tools for setting up Internet sharing gateway (for those people who want to donate bandwidth) and searching/connecting to someones gateway
• DHCPd/NAT on the mesh interfaces with Internet access to the public for X number of days after which display captive portal page with instructions on how to set up their own node (this should be easy, maybe have volunteers help?).  This is needed to force users to help create the mesh network infrastructure.
• Auto-configuration drivers for various popular devices: users dont need to mess with configuring their antennas when it can be done automatically.  Directional devices might require user help in aiming.

Meeki's Portland Meshnet Access Device v0.1

Forum post here has build instructions.