Posts made by Chuck Malloch

I am a retired programmer / engineer and am now playing with an Omega2+. I'm learning node.js and have it installed on a Mac laptop and now also on the Omega. I have been using Subversion for many years for version control, and would like to install it (the client) onto the Omega so I can keep my node.js files synchronized. opkg doesn't know anything about Subversion, and while I saw a reference to using apt-get to install it onto an Omega, neither the Omega nor opkg knows anything about apt-get.
Any ideas? Thanks!

Gabe - the MAC labels are correct (or at least within your assigned MAC address space) while the MAC on my device

root@Omega-A551:~# ifconfig
apcli0    Link encap:Ethernet  HWaddr 42:A3:6B:00:A5:51  
          inet addr:172.16.70.16  Bcast:172.16.255.255  Mask:255.255.0.0
          inet6 addr: fe80::40a3:6bff:fe00:a551/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2068814 errors:0 dropped:2 overruns:0 frame:0
          TX packets:238544 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:232288865 (221.5 MiB)  TX bytes:21739943 (20.7 MiB)

br-wlan   Link encap:Ethernet  HWaddr 40:A3:6B:C0:A5:53  
          inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::42a3:6bff:fec0:a553/64 Scope:Link
          inet6 addr: fd1d:48c4:7633::1/60 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10985 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:904544 (883.3 KiB)

eth0      Link encap:Ethernet  HWaddr 40:A3:6B:C0:A5:53  
          inet6 addr: fe80::42a3:6bff:fec0:a553/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59463 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:19784524 (18.8 MiB)
          Interrupt:5 

eth0.1    Link encap:Ethernet  HWaddr 40:A3:6B:C0:A5:53  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2903 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:208772 (203.8 KiB)

eth0.2    Link encap:Ethernet  HWaddr 40:A3:6B:C0:A5:53  
          inet6 addr: fe80::42a3:6bff:fec0:a553/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56534 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:19332621 (18.4 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:129209 errors:0 dropped:0 overruns:0 frame:0
          TX packets:129209 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:8418410 (8.0 MiB)  TX bytes:8418410 (8.0 MiB)

ra0       Link encap:Ethernet  HWaddr 40:A3:6B:C0:A5:51  
          inet6 addr: fe80::42a3:6bff:fec0:a551/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:6 

only for the apcli0 interface is quite wrong, being outside said MAC address space.

I'm not planning to figure out how to set up a tool chain and everything to rebuild the firmware.
Is there another solution? Will waiting for a firmware upgrade? Or will even that help?

The MAC on my Onion2+ begins with 42:a3:6b:00 instead of 40:a3:6b:c0 as on both the box and device stickers.

Omega2+ box and processor both have MAC address stickers, which match each other, but which DO NOT MATCH the MAC address of the actual device! Oops!