mirror of
https://github.com/opsxcq/mirror-textfiles.com.git
synced 2025-08-21 03:41:20 +02:00
64 lines
3.7 KiB
Plaintext
64 lines
3.7 KiB
Plaintext
Wardialer for unix
|
|
------------------
|
|
Shok
|
|
|
|
Serial programming for unix.....boy this stuff is fun. Well unix
|
|
is famous for it's special files. The modem is just a file you can open(),
|
|
read(), and write() to...for that reason this program can be used on all
|
|
unixs'. The only thing different that needs to be changed, is the
|
|
#define MODEMPORT "/dev/cua1", because most unix/unix clones have their
|
|
own modem port. For example /dev/ttyS? which is COM1 (to the DOS users),
|
|
would be /dev/ttym? in IRIX. Now once this program opens the modem (via
|
|
device/special file) for reading/writing, it will write() to it, and send
|
|
it standard modem instructions like +++ATH, ATZ etc....this comes before
|
|
any dialing to get the modem ready....we also use a function to check for
|
|
"OK" so we know that all is well. On receiving this, then enter the number
|
|
we want to dial into a character buffer, append a "\r" to it (to it
|
|
actually sends the command), we then write(fd (the file desc. for
|
|
/dev/cua1), thebufwiththenum, strlen(thebufwiththenum)); Now once you do
|
|
this..you can't write "+++ATH" to it, because it will send that as the
|
|
login name (assuming you've connected to a host), so what I did, was I
|
|
opened the other modem port (there are two, /dev/cua0 and /dev/ttyS0 are
|
|
essentially the same thing (both COM1 to explain it easier), one is used
|
|
for dialing out (cua?) and one is used for dialling in and out (ttyS?). So
|
|
I opened up the other port and used that to send the command to hang up.
|
|
But all the other stuff isn't complex, they are all C primitive
|
|
instructions like ScanMin++; which would increse ScanMin by 1, repeat a
|
|
while loop, and then the next strcat(phonenum, ScanMin); ... would dial
|
|
the next number......you get the idea. That's about all there really is to
|
|
say about the technical stuff about it.
|
|
|
|
Oh yeah one thing.....when it connects, it looks for the string
|
|
"CONNECT" returned from the modem serial file. You won't get this message
|
|
from faxes as you will only get this message when the connection is
|
|
complete, so this will only return *** CONNECT *** if it was a modem. It
|
|
will both output to the screen and logfile *** CONNECT *** to
|
|
1-xxx-xxx-xxxx. You can use local or long distance, although international
|
|
numbers haven't been added at this time (not hard to do just didn't care
|
|
to add an extra scanf and an extra CountryCode variable ;)
|
|
|
|
About ShokDial (it's temp name for now)
|
|
---------------------------------------
|
|
|
|
This supports random scanning (pseudorandom to be honest, heh) and
|
|
sequential (the range you specified and up) scanning. You can give it a
|
|
range too but that still does under sequential scanning. To use random
|
|
scanning use 'shokdial -r', otherwise it will by default use sequential
|
|
scanning. For the other options type 'shokdial -h'. You want to keep track
|
|
of the version because I'd almsot guarntee this program is going to
|
|
continue changing. I need to add some ncurses GUI effects (heh) and a
|
|
function to resume scanning for those of you who are too lazy to even look
|
|
at the (by default) wardialer.log and get the last number it dialed
|
|
(assuming you used sequential scanning) and entering that as the Scan
|
|
number to begin on!
|
|
|
|
It will output to wardialer.log and on to the screen. If you have
|
|
BEEP = WANTBEEP in the Makefile, it will beep when it connects to a host.
|
|
That's about all I really have to say about it. I don't actually use war
|
|
dialers (really), so I haven't actually tested this (sorry if there are
|
|
any problems but there shouldn't be)....if you do however find a problem,
|
|
please let me know! I will fix it and send out a patched version.....you
|
|
can get all of them from ftp.janova.org or www.janova.org. Enjoy ;)
|
|
|
|
Shok
|