AMD_IBSS networks
From an upload from yesterday: 114 new networks with gps locations, 10 new networks without gps locations.
The laptop was on the table the whole time and never moved, the gps on the chair sometimes not having a 2d/3d fix.
All those new networks are named AMD_IBSS, are indeed ad-hoc (IBSS) networks and have weird BSSIDs (network addresses) which don't look like IEEE vendor assigned addresses:
A search yields me that the 8th bit in an ethernet address is for broadcast/multicast and the 7th is for a 'locally administrated' network address. As far as I can see all of the AMD_IBSS addresses have broadcast set to 0 and locally administrated to 1.
I'm still not sure what I'm seeing here, some sort of new weird accesspoint or some weird client. A google search yields other wardriving forums with people asking the same thing. Answers still welcome!
But I think this 'phenomena' pollutes the wigle database. Maybe a filter on bssids with that 'local' bit set. Opinions?
The laptop was on the table the whole time and never moved, the gps on the chair sometimes not having a 2d/3d fix.
All those new networks are named AMD_IBSS, are indeed ad-hoc (IBSS) networks and have weird BSSIDs (network addresses) which don't look like IEEE vendor assigned addresses:
Code: Select all
Fri Aug 10 23:28:14 2007 Found new network "AMD_IBSS" bssid A2:A9:6A:0D:BB:FA Crypt N Ch 5 @ 11.00 mbit
Fri Aug 10 23:28:23 2007 Found new network "AMD_IBSS" bssid B2:02:47:0D:BB:FA Crypt N Ch 6 @ 11.00 mbit
Fri Aug 10 23:28:26 2007 Found new network "AMD_IBSS" bssid 9E:9F:74:FF:B3:3A Crypt N Ch 7 @ 11.00 mbit
Fri Aug 10 23:28:29 2007 Found new network "AMD_IBSS" bssid 7E:75:30:FF:B3:3A Crypt N Ch 9 @ 11.00 mbit
Fri Aug 10 23:30:51 2007 Found new network "AMD_IBSS" bssid 32:4C:DC:C9:CF:A8 Crypt N Ch 1 @ 11.00 mbit
Fri Aug 10 23:30:54 2007 Found new network "AMD_IBSS" bssid BE:A7:74:15:83:9A Crypt N Ch 2 @ 11.00 mbit
Fri Aug 10 23:30:57 2007 Found new network "AMD_IBSS" bssid A2:D3:FF:43:B8:A6 Crypt N Ch 2 @ 11.00 mbit
I'm still not sure what I'm seeing here, some sort of new weird accesspoint or some weird client. A google search yields other wardriving forums with people asking the same thing. Answers still welcome!
But I think this 'phenomena' pollutes the wigle database. Maybe a filter on bssids with that 'local' bit set. Opinions?
we do already flag ad-hoc networks as ad-hoc, for what its worth.
we'll certainly have a looksee into it, and see what kind of error-checking belt+suspendering we can throw at the normally very high quality output from most net-hugging software packages.
we'll certainly have a looksee into it, and see what kind of error-checking belt+suspendering we can throw at the normally very high quality output from most net-hugging software packages.
As for the "strange" BSSIDs, according to the specs (IIRC, but I'm not 100% sure) ad-hoc networks are actually meant to use a random BSSID.
Return to “WiGLE Project Suggestions”
Who is online
Users browsing this forum: No registered users and 5 guests