# Switch to Pi 3

**URL:** <https://discussions.flightaware.com/t/switch-to-pi-3/18269>\
**Category:** ADS-B Flight Tracking\
**Created:** [April 8, 2016, 12:33pm UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269 "2016-04-08T12:33:37Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![wingnut](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wingnut/32/73634_2.png) [@wingnut](https://discussions.flightaware.com/u/wingnut)\
**Post date:** [April 8, 2016, 12:33pm UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/1 "2016-04-08T12:33:37Z")

</div>

I want to switch from Pi 2B to Pi 3 with filter and Pro amp at antenna. I do not want to lose my stats that date back to Jan /15. Can I do this with losing all my past data?

---

<div class="post-metadata">

**Author:** ![LitterBug](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/litterbug/32/36812_2.png) [@LitterBug](https://discussions.flightaware.com/u/LitterBug)\
**Post date:** [April 8, 2016, 1:29pm UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/2 "2016-04-08T13:29:07Z")

</div>

> [@wingnut](#):
>
> I want to switch from Pi 2B to Pi 3 with filter and Pro amp at antenna. I do not want to lose my stats that date back to Jan /15. Can I do this with losing all my past data?

You will need to clone the MAC address of your old Pi to the RPi3 if you don’t want to loose your FlightAware stats. It is normally done by editing the /boot/cmdline.txt file and adding the following to the end of the line smsc95xx.macaddr=##:##:##:##:##:##

where ##:##:##:##:##:## is the MAC of your previous pi.

Cheers!  
LitterBug

---

<div class="post-metadata">

**Author:** ![crkbday](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/crkbday/32/122325_2.png) [@crkbday](https://discussions.flightaware.com/u/crkbday)\
**Post date:** [April 8, 2016, 3:41pm UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/3 "2016-04-08T15:41:44Z")

</div>

> [@wingnut](#):
>
> I want to switch from Pi 2B to Pi 3 with filter and Pro amp at antenna. I do not want to lose my stats that date back to Jan /15. Can I do this with losing all my past data?

I believe if you save off and then restore the .rrd files in /var/lib/collectd/rrd/piaware/dump1090-rpi you will retain your stats. (I have never tried it though.)

---

<div class="post-metadata">

**Author:** ![JonHanford](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jonhanford/32/17237_2.png) [@JonHanford](https://discussions.flightaware.com/u/JonHanford)\
**Post date:** [April 10, 2016, 2:33am UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/4 "2016-04-10T02:33:31Z")

</div>

> [@LitterBug](#):
>
> > [@wingnut](#):
> >
> > I want to switch from Pi 2B to Pi 3 with filter and Pro amp at antenna. I do not want to lose my stats that date back to Jan /15. Can I do this with losing all my past data?
> 
> You will need to clone the MAC address of your old Pi to the RPi3 if you don’t want to loose your FlightAware stats. It is normally done by editing the /boot/cmdline.txt file and adding the following to the end of the line smsc95xx.macaddr=##:##:##:##:##:##
> 
> where ##:##:##:##:##:## is the MAC of your previous pi.
> 
> Cheers!  
> LitterBug

I can confirm that adding the mac to boot/cmdline.txt means you can just pop your SD card into the new Pi and pick up right where you left off.  
… assuming the image on your card is already compat with the Rpi3

---

<div class="post-metadata">

**Author:** ![41south](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/41south/32/50628_2.png) [@41south](https://discussions.flightaware.com/u/41south)\
**Post date:** [April 14, 2016, 4:01am UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/5 "2016-04-14T04:01:07Z")

</div>

Having just spent the day re configuring a new Pi (due to failure of the old one) I only wish that this method had worked! I’ve tried about 20 different methods, none of them worked until I added a script into crontab that uses macchange. Anyway, problem solved via another method, could not get this to work at all.

Now - who do I contact to get rid of the other station that was created by the new mac that temporarily sent data to FA??

Edit: Found the link to disassociate the site 8)

Not sure why but it’s interesting to note that Piaware uses the eth0 mac not my usb wifi mac to identify itself.

---

<div class="post-metadata">

**Author:** ![bioyuki](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/bioyuki/32/1802_2.png) [@bioyuki](https://discussions.flightaware.com/u/bioyuki)\
**Post date:** [April 14, 2016, 5:11pm UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/6 "2016-04-14T17:11:59Z")

</div>

> [@41south](#):
>
> Having just spent the day re configuring a new Pi (due to failure of the old one) I only wish that this method had worked! I’ve tried about 20 different methods, none of them worked until I added a script into crontab that uses macchange. Anyway, problem solved via another method, could not get this to work at all.
> 
> Now - who do I contact to get rid of the other station that was created by the new mac that temporarily sent data to FA??
> 
> Edit: Found the link to disassociate the site 8)
> 
> Not sure why but it’s interesting to note that Piaware uses the eth0 mac not my usb wifi mac to identify itself.

What method did you use?

---

<div class="post-metadata">

**Author:** ![jprochazka](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jprochazka/32/122364_2.png) [@jprochazka](https://discussions.flightaware.com/u/jprochazka)\
**Post date:** [April 14, 2016, 5:35pm UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/7 "2016-04-14T17:35:19Z")

</div>

> [@41south](#):
>
> I added a script into crontab that uses macchange

That’s the way I have done it in the past as well.  
When installing macchanger it will ask if you want it to run .  
If not you could probably get away with just adding the command to /etc/rc.local and have it run once at boot up as well.

[packages.debian.org/jessie/macchanger](https://packages.debian.org/jessie/macchanger)  
[github.com/alobbs/macchanger](https://github.com/alobbs/macchanger)

Install on Debian based OS’s:

```auto

sudo apt-get install macchanger

```

Command to change your MAC address: _(Replace XX:XX:XX:XX:XX:XX with the MAC address of your choice.)_

```auto

sudo ifdown eth0
sudo macchanger -m XX:XX:XX:XX:XX:XX eth0
sudo ifup eth0

```

---

<div class="post-metadata">

**Author:** ![41south](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/41south/32/50628_2.png) [@41south](https://discussions.flightaware.com/u/41south)\
**Post date:** [April 15, 2016, 9:44pm UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/8 "2016-04-15T21:44:59Z")

</div>

```auto

sudo ifdown eth0
sudo macchanger -m XX:XX:XX:XX:XX:XX eth0
sudo ifup eth0

```

Yep, that’s the one. I just created a script file using nano called piawaremac - but call it whatever you want

```auto

sudo nano piawaremac

```

Saved it with the above code in it - pretty quick and dirty but it works fine.

Set it to be executable using

```auto

sudo chmod 755 piawaremac 

```

The added it to crontab using the @reboot so it runs anytime the Pi reboots or starts

---

<div class="post-metadata">

**Author:** ![JonAHupp](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jonahupp/32/121024_2.png) [@JonAHupp](https://discussions.flightaware.com/u/JonAHupp)\
**Post date:** [April 22, 2016, 1:45am UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/9 "2016-04-22T01:45:51Z")

</div>

While changing the MAC address works, this is a such a hack.

Why can’t the folks at FlightAware make it possible to update one’s hardware without losing statistics or ‘pretending’ to have the old Pi’s MAC address?

This seems especially important now, since many of us would like to upgrade from our B+ to a 3.

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [April 22, 2016, 9:51am UTC](https://discussions.flightaware.com/t/switch-to-pi-3/18269/10 "2016-04-22T09:51:50Z")

</div>

It’s on my list of stuff to fix but it is relatively involved and the current setup is not actually broken, except for rare cases of MAC collisions (I know of two cases total). You only have to mess with the mac it you want to pretend that new hardware isn’t actually new, which is purely a stats display thing. So it is not the top priority and I have few things ahead of it.
