piaware logging as guest, even with correct credentials


#1

/tmp/piaware.out:

tail -f /tmp/piaware.out

11/04/2014 13:20:54 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
11/04/2014 13:20:54 i see dump1090 serving on port 10001
11/04/2014 13:20:54 connecting to dump1090 on port 10001…
11/04/2014 13:20:54 piaware is connected to dump1090 on port 10001
11/04/2014 13:20:55 dump1090 is listening for connections on FA-style port 10001
11/04/2014 13:20:55 logged in to FlightAware as user guest
11/04/2014 13:20:57 piaware received a message from the ADS-B source!
11/04/2014 13:21:12 piaware has successfully sent several msgs to FlightAware!
11/04/2014 13:21:25 18 msgs recv’d from dump1090; 18 msgs sent to FlightAware
11/04/2014 13:21:54 server is sending alive messages; we will expect them

I’ve run the piaware-config script with my correct credentials and I’m still seeing only guest login.

I will note, I’ve been switching between different devices due to wireless issues where I have the device placed, but those are resolved now, is it possible I have too many different MAC addresses associated with my account? Some of my troubleshooting has involved trying out different wifi dongles, which would show numerous different MAC addresses for my account. These two issues may be completely unrelated, but I thought I’d mention it.


#2

This is sometimes a glitch on our side. What version of PiAware are you running? Are you connected now?


#3

Seem to be:

version:
piaware -v
1.16

/tmp/piaware.out

11/04/2014 21:31:09 piaware version 1.16 is running, process ID 1854
11/04/2014 21:31:09 your system info is: Linux cubienocard 3.4.79 #6 SMP PREEMPT Fri Feb 14 23:58:54 CST 2014 armv7l armv7l armv7l GNU/Linux
11/04/2014 21:31:09 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
11/04/2014 21:31:09 i see dump1090 serving on port 10001
11/04/2014 21:31:09 connecting to dump1090 on port 10001…
11/04/2014 21:31:09 piaware is connected to dump1090 on port 10001
11/04/2014 21:31:09 dump1090 is listening for connections on FA-style port 10001
11/04/2014 21:31:09 logged in to FlightAware as user guest

*Note current version is running on a cubietruck (the wifi is a little more stable where I have my ads-b antenna placed.)

My Current MAC address is HWaddr 98:3b:16:80:b6:80 (wifi) but I only see my previous mac addresses from previous attempts with my raspberry pi, listed.


#4

Just remembered something about the Cubietruck, the image I’m using seems to auto-generate its mac addresses, a weird quirk. I’m going to statically set this and see what changes.

Update: Have set mac address to previously active MAC address listed with Flightaware that had correctly identified me prior, no improvement. Checked and piaware.out shows still logging in as ‘guest’. So,
I set my piaware credentials with username ‘corq’ as opposed to my email address that I log into flightaware with. Seems I’ve used corq as my username previously, without issue, but I’m open to correction if this is an incorrect method :wink:

Thanks for any help.


#5

Hi, the MAC addresses that I can find that are associated with username ‘corq’, the last checkin was on the 2nd of November. I don’t see any checkin from the wifi mac you reported of 98:3b:16:80:b6:80. Do you have an eth0 MAC address (even if you’re not using it for your gateway) and if so can you paste that or can you paste whatever MAC you are using? Thanks.

Another thing to try, you might log into the piaware box and do sudo piaware-config -user corq -password and then enter your password and do a sudo reboot and see if that works. Although we (FA) really need to fix this guest-attribution bug that still seems to be cropping up in our code.


#6

Hi Karl, thanks for your time and assistance with this.

Did the username/password update, and rebooted.
No change yet, still only connecting as guest.

Interface macs on the device are as follows:

eth0 02:94:04:42:70:66 (unused interface)

wlan0 02:89:09:82:2a:76 (current active interface)

Thanks again for your help!


#7

You’re super welcome. Well, the good news is that your login messages got logged and your MAC is in there. The bad news is it’s still logging you in as guest. The other good news is that although I’m a little suspicious that the problem is related to the non-raspberry pi you’re using, I’m considerably suspicious that we introduced a bug in some logic changes we made to the adept server (the thing piaware talks to on the FlightAware server side) to support password-less logins and “claiming”). Anyway I’m testing that theory now and actually I hope that is it. I’ll let you know in a bit.

[UPDATE - I tried piaware-config and it worked for me with stock 1.16 on a Raspberry Pi. I then tried disconnecting the adept backend from your session from the mac 02:94:04:42:70:66 and your side didn’t reconnect, which is rather curious. (Sorry about that, by the way.) If you’d paste relevant lines of /tmp/piaware.out that’d be helpful. Still looking… -karl]

[UPDATE 2 - I replicated the problem on a test box. Looks like a problem on the client side. I’ve manually bound your user to that device and I think if you restart piaware it will log in properly as you. In the meantime I can debug this and if it is on the client, at least have it fixed for 1.17.]


#8

Looking good!

11/06/2014 15:30:57 piaware version 1.16 is running, process ID 10764
11/06/2014 15:30:57 your system info is: Linux cubienocard 3.4.79 #6 SMP PREEMPT Fri Feb 14 23:58:54 CST 2014 armv7l armv7l armv7l GNU/Linux
11/06/2014 15:30:57 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
11/06/2014 15:30:57 i see dump1090 serving on port 10001
11/06/2014 15:30:57 connecting to dump1090 on port 10001…
11/06/2014 15:30:57 piaware is connected to dump1090 on port 10001
11/06/2014 15:30:58 dump1090 is listening for connections on FA-style port 10001
11/06/2014 15:30:58 logged in to FlightAware as user corq
11/06/2014 15:30:58 piaware received a message from the ADS-B source!

Just for my own edification, what about the identification is so specific to the raspberry pi? Is it debian specific?

The cubietruck can run either debian or ubuntu, and I think the current image on mine is Ubuntu 14.04. I probably should have mentioned it earlier, I was just focused on this being a login issue rather than device-specific.

FWIW, I have multiple arm devices, Several Raspberry Pi, Banana pi, cubietruck (this one), if flightaware at any time wants to test against other devices, I’d be glad to help out.

Thanks again.


#9

Seeing multiple entries for my device, is this normal? Should only live devices be shown?

If image doesn’t show I have it posted at imgur: imgur.com/BwuLEDw


#10

Thanks for the offer and thanks for being cool with us while we sorted things out. I just was reading about the Banana Pi a couple days ago (hadn’t seen the cubietruck before), and they’re all interesting and point to a future of a plethora of powerful, inexpensive computers running “real” operating systems.

There’s nothing magic about the Raspberry Pi other than that it’s the thing we initially supported and it’s the main thing we test on, so it’s effectively our standard platform.

Other versions of Debian should work or be very close and Ubuntu is built on top of Debian so it’s probably close if not fine.

We use the MAC address of the eth0 interface on the device as a unique key to identify the device to the backend software piaware talks to at FlightAware. Of course this can be configured on many devices (and easily faked for that matter) but on the whole it seems to work pretty well.

A couple of problems that have turned up are versions of Linux that don’t have quite the same methods of finding out the MAC address (and I find these incompatibilities kind of gratuitous and annoying, but I get how it happens) and some devices like the Raspberry Pi Model A don’t have an Ethernet interface at all and we added code to use like the wlan0 MAC address if an eth0 one can’t be found but I’m not 100% sure it works and we will be testing that today, actually.


#11

maybe the feeder could use an argument to over-ride any discovered / specify a MAC address to to use the login.
Shouldn’t be needed 98% of the time, but for the 2% …


#12

Yes, exactly. I actually broke this on the client in one of the recent releases. It’s fixed for 1.17 (coming in the next few days) that if you set a user and password with piaware-config the user will claim the piaware host, wresting it away from any user that might have previously had it (or the dreaded “guest”).