Just an idea: generate a random MAC on first boot of NanoNote and then remember it? BTW, is there any way to identify uniquely every Ben? Perhaps read the serial number of CPU or something like this from the software? Then we could generate MAC from that.

On Mon, 18 Jun 2012, Xiangfu Liu wrote:

Hi

I just feel not right to set Nanonote with a static MAC address. it's not a real NIC and
all nanonote have same MAC address make me feel not good.

As you wrote in email. for people who want the static MAC address.
it's easy to setup:
 fw_printenv  # for get the bootargs
fw_setenv bootargs g_ether.host_addr=xx:xx:xx:xx:xx:xx FW_PRINTENV_BOOTARGS_OUTPUT

BTW:
All recently image included 'mtd.nn', and 'mtd.nn fw_setenv_default' run once after
reflash.

Best Regards
Xiangfu

On 06/17/2012 06:14 PM, EdorFaus wrote:

I wanted the static MAC address so that NetworkManager could
recognize the device and automatically start its network sharing, so
the NanoNote could access the internet via the host without having to
fiddle with config files or do any further manual setup.

This works perfectly now that I've configured my NanoNote to use a
static MAC address (which is not overly difficult, see [1]), but I
figured it might be a good idea to make that the default (or at least
the (10.42.43.x) static IP that I also had to set on the NN). It
seems like the maintainers either weren't listening or didn't agree
though.

Of course, my proposal was for a change in how the IPv4 networking
worked - you might have better luck, as your IPv6 proposal doesn't
change a currently (mostly) working status quo, but makes something
work that didn't previously.


_______________________________________________
Qi Hardware Discussion List
Mail to list (members only): [email protected]
Subscribe or Unsubscribe: http://lists.en.qi-hardware.com/mailman/listinfo/discussion


_______________________________________________
Qi Hardware Discussion List
Mail to list (members only): [email protected]
Subscribe or Unsubscribe: 
http://lists.en.qi-hardware.com/mailman/listinfo/discussion

Reply via email to