# Not connected to FlightAware
**URL:** https://discussions.flightaware.com/t/not-connected-to-flightaware/19600
**Category:** ADS-B Flight Tracking
**Created:** [January 25, 2017, 6:03pm UTC](https://discussions.flightaware.com/t/not-connected-to-flightaware/19600 "2017-01-25T18:03:20Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@JoseADuran](https://discussions.flightaware.com/u/JoseADuran)
#### Post date: [January 25, 2017, 6:03pm UTC](https://discussions.flightaware.com/t/not-connected-to-flightaware/19600/1 "2017-01-25T18:03:20Z")
Today I haven’t been able to connect my PiAware to FlightAware.
My ADS-B page says:
1. Anomaly report for PiAware feeder with a MAC address of b8:27:eb:6c:4e:20:
This feeder last checked in several hours ago.
2. My STATUS page:
Radio: Received Mode S data recently
PiAware: Piaware 3.1.0 is running
FilghtAware: Not connected to FlightAware
MLAT: Multilateration is not enabled
My FlighAware dump1090 is showing ADS-B aircraft on the map however, the STATUS page says “PiAware doesn’t seem to be running”
Help appreciated
---
### Author:  [@JoseADuran](https://discussions.flightaware.com/u/JoseADuran)
#### Post date: [January 25, 2017, 8:23pm UTC](https://discussions.flightaware.com/t/not-connected-to-flightaware/19600/2 "2017-01-25T20:23:56Z")
Apparently, it was something with piaware-config.txt’s “wired-address” It was set as 192.168.1.255 and the original was 192.168.1.10. I copied the original to the SD Card, rebooted and it immediately communicated with FlightAware.
I have to change some lines but, I’ll do it “one step at a time”
---
### Author:  [@obj](https://discussions.flightaware.com/u/obj)
#### Post date: [January 25, 2017, 9:10pm UTC](https://discussions.flightaware.com/t/not-connected-to-flightaware/19600/3 "2017-01-25T21:10:05Z")
> [@JoseADuran](#):
>
> “wired-address” It was set as 192.168.1.255
Yeah, that’s not going to work.
I’d just use DHCP if you can.