TN.Frank

Not trying to be difficult at all just looking for a simple answer so let's get Stupid Simple for a minute. I click on the "rtl_adsb" in my Kali Linux install and I get this: rtl_adsb: invalid option -- 'h' rtl_adsb, a simple ADS-B decoder Use: rtl_adsb [-R] [-g gain] [-p ppm] [output file] [-d device_index (default: 0)] [-V verbove output (default: off)] [-S show short frames (default: off)] [-Q quality (0: no sanity checks, 0.5: half bit, 1: one bit (default), 2: two bits)] [-e allowed_errors (default: 5)] [-g tuner_gain (default: automatic)] [-p ppm_error (default: 0)] filename (a '-' dumps samples to stdout) (omitting the filename also uses stdout) Streaming with netcat: rtl_adsb | netcat -lp 8080 while true; do rtl_adsb | nc -lp 8080; done Streaming with socat: rtl_adsb | socat -u - TCP4:sdrsharp.com:47806 I see I can Stream with either netcat or socat. I find in my Kali Linux install "ncat" and "socat". I click "ncat" and I get this: Ncat 6.40 ( http://nmap.org/ncat ) Usage: ncat [options] [hostname] [port] Options taking a time assume seconds. Append 'ms' for milliseconds, 's' for seconds, 'm' for minutes, or 'h' for hours (e.g. 500ms). -4 Use IPv4 only -6 Use IPv6 only -U, --unixsock Use Unix domain sockets only -C, --crlf Use CRLF for EOL sequence -c, --sh-exec <command> Executes the given command via /bin/sh -e, --exec <command> Executes the given command --lua-exec <filename> Executes the given Lua script -g hop1[,hop2,...] Loose source routing hop points (8 max) -G <n> Loose source routing hop pointer (4, 8, 12, ...) -m, --max-conns <n> Maximum <n> simultaneous connections -h, --help Display this help screen -d, --delay <time> Wait between read/writes -o, --output <filename> Dump session data to a file -x, --hex-dump <filename> Dump session data as hex to a file -i, --idle-timeout <time> Idle read/write timeout -p, --source-port port Specify source port to use -s, --source addr Specify source address to use (doesn't affect -l) -l, --listen Bind and listen for incoming connections -k, --keep-open Accept multiple connections in listen mode -n, --nodns Do not resolve hostnames via DNS -t, --telnet Answer Telnet negotiations -u, --udp Use UDP instead of default TCP --sctp Use SCTP instead of default TCP -v, --verbose Set verbosity level (can be used several times) -w, --wait <time> Connect timeout --append-output Append rather than clobber specified output files --send-only Only send data, ignoring received; quit on EOF --recv-only Only receive data, never send anything --allow Allow only given hosts to connect to Ncat --allowfile A file of hosts allowed to connect to Ncat --deny Deny given hosts from connecting to Ncat --denyfile A file of hosts denied from connecting to Ncat --broker Enable Ncat's connection brokering mode --chat Start a simple Ncat chat server --proxy <addr[:port]> Specify address of host to proxy through --proxy-type <type> Specify proxy type ("http" or "socks4") --proxy-auth <auth> Authenticate with HTTP or SOCKS proxy server --ssl Connect or listen with SSL --ssl-cert Specify SSL certificate file (PEM) for listening --ssl-key Specify SSL private key (PEM) for listening --ssl-verify Verify trust and domain name of certificates --ssl-trustfile PEM file containing trusted SSL certificates --version Display Ncat's version information and exit See the ncat(1) manpage for full options, descriptions and usage examples Not sure what to do with it. I click "socat" and I get this: socat by Gerhard Rieger - see www.dest-unreach.org Usage: socat [options] <bi-address> <bi-address> options: -V print version and feature information to stdout, and exit -h|-? print a help text describing command line options and addresses -hh like -h, plus a list of all common address option names -hhh like -hh, plus a list of all available address option names -d increase verbosity (use up to 4 times; 2 are recommended) -D analyze file descriptors before loop -ly[facility] log to syslog, using facility (default is daemon) -lf<logfile> log to file -ls log to stderr (default if no other log) -lm[facility] mixed log mode (stderr during initialization, then syslog) -lp<progname> set the program name used for logging -lu use microseconds for logging timestamps -lh add hostname to log messages -v verbose data traffic, text -x verbose data traffic, hexadecimal -b<size_t> set data buffer size (8192) -s sloppy (continue on error) -t<timeout> wait seconds before closing second channel -T<timeout> total inactivity timeout in seconds -u unidirectional mode (left to right) -U unidirectional mode (right to left) -g do not check option groups -L <lockfile> try to obtain lock, or fail -W <lockfile> try to obtain lock, or wait -4 prefer IPv4 if version is not explicitly specified -6 prefer IPv6 if version is not explicitly specified bi-address: pipe[,<opts>] groups=FD,FIFO <single-address>!!<single-address> <single-address> single-address: <address-head>[,<opts>] address-head: abstract-client:<filename> groups=FD,SOCKET,RETRY,UNIX abstract-connect:<filename> groups=FD,SOCKET,RETRY,UNIX abstract-listen:<filename> groups=FD,SOCKET,LISTEN,CHILD,RETRY,UNIX abstract-recv:<filename> groups=FD,SOCKET,RETRY,UNIX abstract-recvfrom:<filename> groups=FD,SOCKET,CHILD,RETRY,UNIX abstract-sendto:<filename> groups=FD,SOCKET,RETRY,UNIX create:<filename> groups=FD,REG,NAMED exec:<command-line> groups=FD,FIFO,SOCKET,EXEC,FORK,TERMIOS,PTY,PARENT,UNIX fd:<num> groups=FD,FIFO,CHR,BLK,REG,SOCKET,TERMIOS,UNIX,IP4,IP6,UDP,TCP,SCTP gopen:<filename> groups=FD,FIFO,CHR,BLK,REG,SOCKET,NAMED,OPEN,TERMIOS,UNIX interface:<interface> groups=FD,SOCKET ip-datagram:<host>:<protocol> groups=FD,SOCKET,RANGE,IP4,IP6 ip-recv:<protocol> groups=FD,SOCKET,RANGE,IP4,IP6 ip-recvfrom:<protocol> groups=FD,SOCKET,CHILD,RANGE,IP4,IP6 ip-sendto:<host>:<protocol> groups=FD,SOCKET,IP4,IP6 ip4-datagram:<host>:<protocol> groups=FD,SOCKET,RANGE,IP4 ip4-recv:<protocol> groups=FD,SOCKET,RANGE,IP4 ip4-recvfrom:<protocol> groups=FD,SOCKET,CHILD,RANGE,IP4 ip4-sendto:<host>:<protocol> groups=FD,SOCKET,IP4 ip6-datagram:<host>:<protocol> groups=FD,SOCKET,RANGE,IP6 ip6-recv:<protocol> groups=FD,SOCKET,RANGE,IP6 ip6-recvfrom:<protocol> groups=FD,SOCKET,CHILD,RANGE,IP6 ip6-sendto:<host>:<protocol> groups=FD,SOCKET,IP6 open:<filename> groups=FD,FIFO,CHR,BLK,REG,NAMED,OPEN,TERMIOS openssl:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP4,IP6,TCP,OPENSSL openssl-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RETRY,RANGE,IP4,IP6,TCP,OPENSSL pipe:<filename> groups=FD,FIFO,NAMED,OPEN proxy:<proxy-server>:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP4,IP6,TCP,HTTP pty groups=FD,NAMED,TERMIOS,PTY sctp-connect:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP4,IP6,SCTP sctp-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RETRY,RANGE,IP4,IP6,SCTP sctp4-connect:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP4,SCTP sctp4-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RETRY,RANGE,IP4,SCTP sctp6-connect:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP6,SCTP sctp6-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RETRY,RANGE,IP6,SCTP socket-connect:<domain>:<protocol>:<remote-address> groups=FD,SOCKET,CHILD,RETRY socket-datagram:<domain>:<type>:<protocol>:<remote-address> groups=FD,SOCKET,RANGE socket-listen:<domain>:<protocol>:<local-address> groups=FD,SOCKET,LISTEN,CHILD,RETRY,RANGE socket-recv:<domain>:<type>:<protocol>:<local-address> groups=FD,SOCKET,RANGE socket-recvfrom:<domain>:<type>:<protocol>:<local-address> groups=FD,SOCKET,CHILD,RANGE socket-sendto:<domain>:<type>:<protocol>:<remote-address> groups=FD,SOCKET socks4:<socks-server>:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP4,IP6,TCP,SOCKS4 socks4a:<socks-server>:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP4,IP6,TCP,SOCKS4 stderr groups=FD,FIFO,CHR,BLK,REG,SOCKET,TERMIOS,UNIX,IP4,IP6,UDP,TCP,SCTP stdin groups=FD,FIFO,CHR,BLK,REG,SOCKET,TERMIOS,UNIX,IP4,IP6,UDP,TCP,SCTP stdio groups=FD,FIFO,CHR,BLK,REG,SOCKET,TERMIOS,UNIX,IP4,IP6,UDP,TCP,SCTP stdout groups=FD,FIFO,CHR,BLK,REG,SOCKET,TERMIOS,UNIX,IP4,IP6,UDP,TCP,SCTP system:<shell-command> groups=FD,FIFO,SOCKET,EXEC,FORK,TERMIOS,PTY,PARENT,UNIX tcp-connect:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP4,IP6,TCP tcp-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RETRY,RANGE,IP4,IP6,TCP tcp4-connect:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP4,TCP tcp4-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RETRY,RANGE,IP4,TCP tcp6-connect:<host>:<port> groups=FD,SOCKET,CHILD,RETRY,IP6,TCP tcp6-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RETRY,RANGE,IP6,TCP tun:<ip-addr>/<bits> groups=FD,CHR,NAMED,OPEN,INTERFACE udp-connect:<host>:<port> groups=FD,SOCKET,IP4,IP6,UDP udp-datagram:<host>:<port> groups=FD,SOCKET,RANGE,IP4,IP6,UDP udp-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RANGE,IP4,IP6,UDP udp-recv:<port> groups=FD,SOCKET,RANGE,IP4,IP6,UDP udp-recvfrom:<port> groups=FD,SOCKET,CHILD,RANGE,IP4,IP6,UDP udp-sendto:<host>:<port> groups=FD,SOCKET,IP4,IP6,UDP udp4-connect:<host>:<port> groups=FD,SOCKET,IP4,UDP udp4-datagram:<remote-address>:<port> groups=FD,SOCKET,RANGE,IP4,UDP udp4-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RANGE,IP4,UDP udp4-recv:<port> groups=FD,SOCKET,RANGE,IP4,UDP udp4-recvfrom:<host>:<port> groups=FD,SOCKET,CHILD,RANGE,IP4,UDP udp4-sendto:<host>:<port> groups=FD,SOCKET,IP4,UDP udp6-connect:<host>:<port> groups=FD,SOCKET,IP6,UDP udp6-datagram:<host>:<port> groups=FD,SOCKET,RANGE,IP6,UDP udp6-listen:<port> groups=FD,SOCKET,LISTEN,CHILD,RANGE,IP6,UDP udp6-recv:<port> groups=FD,SOCKET,RANGE,IP6,UDP udp6-recvfrom:<port> groups=FD,SOCKET,CHILD,RANGE,IP6,UDP udp6-sendto:<host>:<port> groups=FD,SOCKET,IP6,UDP unix-client:<filename> groups=FD,SOCKET,NAMED,RETRY,UNIX unix-connect:<filename> groups=FD,SOCKET,NAMED,RETRY,UNIX unix-listen:<filename> groups=FD,SOCKET,NAMED,LISTEN,CHILD,RETRY,UNIX unix-recv:<filename> groups=FD,SOCKET,NAMED,RETRY,UNIX unix-recvfrom:<filename> groups=FD,SOCKET,NAMED,CHILD,RETRY,UNIX unix-sendto:<filename> groups=FD,SOCKET,NAMED,RETRY,UNIX Not sure what to do with it either. The rtl_adsb can use one of these to output to something but I'm not sure what. I know people use their browsers to localhost, 127.0.0.1 and which ever port netcat or socat uses to plot a map to watch the planes fly around but I don't know how to get from starting the rtl_adsb to getting it output to a map so I can see planes fly. I need to know if I can use ncat(netcat??) or socat to output what rtl_adsb is doing to a map of somekind so I can see in real time aircraft flying around. Any explanation or solutions needs to be simple and needs to be explained in steps that I can understand. Thanks.

So you're basically saying that there's no way to get "There"(tracking planes) from "here"(my Kali Linux install) so I have to add some extra stuff to get the job done. I guess someone needs to put a tutorial together on how to get this going from step one to finish for those of us who aren't Linux Gurus and only have a limited understanding of Terminal commands. Maybe someday, until then I'll just have to wait I guess.

Ahh, ok. Sounds like it'd be cool if you lived on the coast. Thanks.

What is AIS, need more info on it.

Kali already has WINE installed by default but I don't see why I'd need to use it when they have Linux based rtl_adsb installed and modes_gui installed as well. With the rtl_adsb you can go netcat(ncat??) or socat to run it in Terminal but I have no idea where to go from there. I see that the dongle is up and running in rtl_adsb but don't know how to, for instance, port it out to socat which also opens in Terminal when I click on it. All the stuff is already pre-installed in Kali, just need to know how to connect the dots to get it working.

Can no one tell me how to get ads-b going in Kali???

Aside from Kali and Pentoo what other Distros have pre-installed SDR and ADS-B stuff right out of the box? I know you can install SDR stuff on about any Distro but it's such a pain that if it's already part of the Distro Bundle it's just that much easier to get your SDR on. So, any other's or just Kali and Pentoo?

Probably so I just don't have a clue as to how to get it to work. I start my rtl_adsb program in Terminal and I see it's working but have no clue where to go from there. modes_gui doesn't do anything even though it's suppose to be the front end for adsb. and there's nothing else listed that looks like something I'd use with adsb.

You could always do a hard reset to the router and that'd would put everything back to factory specs including the password. Most routers have the password on the bottom or it's just "admin" for login and "admin" for the password. Worth a shot if you can't get it done any other way.

Kali all the way. Newer, Debian based, Software Defined Radio tools out of the box(main reason I use it) so Kali gets my vote.

Somehow in ifconfig you'll need to bring wlan0 "up" so it'll be active. You may need to do your cracking from wif and disconnect your ehternet to get things working correctly. Not that I'm any kind of expert, never did any wifi cracking but it just seems like as long as you're hooked up via ethernet your computer may default to it and not let you use your wifi. You need to think of this as an "I'm out and about and need to hak someone's wifi so I can check my e-mail" kind of deal where you only have wifi to work with, no ethernet. If it's WEP it might not be that bad to crack but if it's WPA/WPA2 it might take awhile. Something else you might try, most routers use "admin" for the login and password. You may still have "admin" as your login then just think of what you might have used "back in the day" for your password and try it. Once you're in you can change it to something that you'll remember more easily. I know this probably hasn't been much help but at least I'm trying, LOL.

I like Suspend because it's handy when I'm going to be off and on my laptop during the day. I'd like to install TLP for Power Management but for Debian there's a few hoops to jump though, not as easy as for an Ubuntu Distro. Still, I might give it a try and see if it'll fix the problem.

HP/Compaq NC6400. 1.83GHz Core Duo processor, Intel 945 graphics chip set, 2GB DDR2-667MHz RAM.

I know for some laptops Linux Mint had this same problem and I've now got it with my Kali install. I suspend then when I wake my fan runs constantly and won't stop until I reboot the laptop. Didn't have that problem with Point Linux 2.2 which is also Debian based so I'm not sure why it's doing what it's doing. Anyone have a clue as to how to fix this problem? Thanks.

No problem pard. I'm all about taking the easy way out. LOL

Download a copy of Kali LInux 1.0.6 and install it. It has Gqrx which is a great front end that uses GNU Radio and it's stupid simple to use. That's how I got my SDR goodness on.

I mean with the pre-installed stuff that's already on Kali. Not with stuff I'd have to compile from source or get from github. :D

I installed Kali 1.0.6 so I'd have "out of the box" SDR and there's also some adsb stuff installed but for the life of me I can't figure out how to get it working. I can start rtl_adsb and I see in the Terminal that pops up that it's running as far as I know but from there nothing else seems to work. If anyone has gotten adsb working under Kali please share how you got things going with us here. Thanks.

Very cool info. Need to see if I can tune into my local tower. Thanks.

Just as long as you don't start seeing Dead People, LOL.

Hey, I stuck my little stock antenna on a chunk of metal too so it'd stop falling over, LOL. I used the old weight off of a pressure cooker, it's about the size of a half dollar coin and around 1/2" thick so it's heavier enough to keep the antenna stable but small enough to not take up much space.

Ok, figured out a HUGE solution. Buy an acutal laptop with a dual core processor and a bigger screen so you can see all of Gqrx when it's running. The 12.1" HP/Compaq NC4400 took to Gqrx like a duck to water. Still smaller then my 14.1" laptops but it is a bit larger then the 8.9" Netbook. Still, it's working where the Netbook didn't so that's a huge plus right there for the little extra size and weight.

I think I didn't leave the CMOS battery out long enough the first time. This time I left it out for about 20 minuites and put it all back together and LEFT THE LAPTOP battery OUT.LOL I think that was one step that I messed up on last time. Anyway, it's working like a champ, loading Kali on it now and I can't wait to see the numbers I get when I benchmarke it using CPU Blowfish. This is my fastest laptop to date, Core 2 Duo 2.0GHZ. Should be pretty fast. Oh well, see ya'll on the forums.

Got it whipped, just didn't leave the battery out long enough last time I guess. Also, I installed the laptop battery before I should have so that might have been another reason. Anyway, loading Kali Linux on it as we speak. Talk to ya'll later.