home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Action Ware 14: Rise of the Triad
/
ACWARE14.iso
/
acware14
/
network
/
kali
/
help.me!
< prev
next >
Wrap
Text File
|
1995-08-30
|
7KB
|
166 lines
Kali Help Document version 1.1
This document is very new and doesn't include everything. Hopefully this
might help some people who are having trouble getting Kali to work.
Just read the questions.
Q1: Where can I get Kali?
A1: DOH! You must already have a copy or you wouldn't be reading this
document. Well, ok, if you insist. Get Kali from:
ftp://ftp.axxis.com/pub/kali/
ftp://ftp.internexus.net/pub/kali/
Q2: Why does Kali report, "ERROR: Cannot access packet driver"?
A2: You either don't have a packet driver loaded or you have another driver
loaded on top of your packet driver which won't allow Kali to access it.
Most packet drivers only allow one program to be loaded over them. Some
packet drivers will automatically multiplex and allow you to run 2 or more
TCPIP applications on top of them.
Find the proper packet driver for your setup. Instructions for obtaining
and installing the packet driver can be found in kali.doc.
Q3: Why does Kali report, "Error: no response from xxx.xxx.xxx.xxx"?
A3: Either because the ip# you are trying to attach to is not running Kali
or you don't have Kali configured properly. Kali Central at 204.96.20.10
should be up and running 24hr a day.
Have you tested your connection yet? Can you ping 204.96.20.10? Have you
tried these steps? If not, read the kali.doc file and pay special attention
to the section titled "Testing your TCPIP Setup".
Q4: Why can't I ping my gateway?
A4: Good question! This means you are actually trying to test your connection
before using Kali! I'm so happy!
Anyway, this is almost always caused by an incorrect value in wattcp.cfg.
Either your gateway or my_ip value is most likely wrong.
If using a modem, are you sure you connected to your host properly? Did the
host report that SLIP or PPP was started? If using PPP, did the PPP driver
report your ip# (many SLIP hosts will do this too)? Are you absolutely
positive that your modem is configured for hardware flow control (RTS/CTS)
and not software (XON/XOFF)? For Hayes modems, this is normally done with
AT&F2. For USR modems, try using AT&F1.
PPP users: try using a netmask of 0.0.0.0 and put the line ppp=1 in wattcp.cfg.
Using a netmask of 0.0.0.0 will make the wattcp kernel think that all nodes
are in your local network. It will cause Kali and other wattcp apps to quit
trying to use the gateway. Using ppp=1 with Kali will cause wattcp to quit
trying to resolve ethernet addresses (which it can't do anyway...but tries).
PPP and SLIP users: if using bootp, try entering your actual ip# instead.
If using ethernet, are you sure you loaded the driver with the correct I/O
port, interrupt, and address (if used)?
Q5: I can ping my gateway, but I can't ping 204.96.20.10 or other ip numbers
that I know exist around the world. What's wrong?
A5: If most cases, this is the result of an incorrect netmask value in
wattcp.cfg. Try using 255.255.0.0 or 255.255.255.0. The wrong value for
my_ip and gateway can also cause this.
Q6: I can ping 204.96.20.10, but I can't connect with Kali. Why?
A6: Wow...getting close. The most common problem causing this is an incorrect
modem init string. Make sure that hardware flow control and NOT software flow
control is enable on the modem (see A4 above).
This can also be caused by having the wrong info in wattcp.cfg.
Q7: Ok, I finally connected to Kali Central. Now my PC locks up after a few
seconds. I haven't even started a game yet. Sometimes it locks up before I
even run Kali. Sometimes I get the player list. What did I do wrong?
A7: The most common cause is not having hardware (RTS/CTS) flow control
enabled (and software/XON/XOFF disabled). Check the manual for your modem
and make sure your init string enables RTS/CTS and disables XON/XOFF.
The second most common reason for PPP users is the omission of the ppp=1
line in wattcp.cfg. Also try using a netmask of 0.0.0.0 (PPP only).
If using ppp, your provider might be using Link Quality Monitoring. If you
cannot disable this option, you will not be able to use Merit's etherppp
driver. Get a copy of pppshare.zip from one of the sites listed above for
Kali and try this driver instead (get lsl.zip while you are there).
Q8: I can connect to Kali Central, and I can even start playing a game. Now
my PC locks up after a few seconds of playing. What now?
A8: Check the answer to Q7 above and if using ppp, be sure you have the line
"ppp=1" in wattcp.cfg.
Q9: Why do I see myself listed twice in the kali /s list?
A9: This is almost always a SLiRP problem. If the ip number for both entries
is the same, and the port number is different, then the redirection command
in .slirprc failed (or you used the wrong command). If the ip number for
both entries is different, then you are using the wrong ip number in wattcp.cfg
and probably the wrong ip# in the redirection commands. The second number you
see is the correct ip#. Use this number in .slirprc and in wattcp.cfg.
Q10: Why do I see myself listed more than 2 times in the kali /s list?
A10: You are using a SLIP emulator that is not compatable with Kali. The only
SLIP emulator that works with Kali is SLiRP. TIA will NOT work.
Q11: How can I get more conventional memory?
A11: Use a memory manager such as DOS's emm386 or QEMM. Load DOS high and
load Kali high (lh Kali). You should be able to get Kali into an upper
memory block on most systems. Read your DOS manual or type "help emm386"
at the DOS prompt. If use have a CDROM, try to avoid loading all of its
drivers. Using DOS 6.0 and above you can create multiple configurations
in your config.sys. Again, read the DOCS.
Most games that use their own memory menager (like Doom and Descent) will
still work when used with emm386 or qemm. They also still need at least
some minimal conventional memory. Both Doom and Descent will have fits if
the conventional memory is below 350K (approx).
Q99: This stupid document didn't help. What do I do now?
A99: If this list doesn't answer your question, please send your question to:
jay@calc.vet.uga.edu
***NOTE*** You must include the following information for me to be able to
help. Without this information, I won't answer most questions.
1. What version of Kali are you using?
2. Connection type: {PPP, SLIP, SLiRP, ethernet}
3. Packet driver: {etherppp, slipper, cslipper, wd8003e, 3c509, etc.}
4. If using modem, what brand/model of modem and speed?
5. If using modem, what init string are you using?
6. Command line used to start packet driver.
7. Script used when connecting to host (or at least outline the prompts)
8. A copy of wattcp.cfg.
9. A copy of kali.cfg.
10. A description of the problem and what steps you have taken to try to
resolve the problem. I want to know at what point in the instructions
in kali.doc you can't get past. If you send me email stating that you
cannot connect to Kali Central and don't tell me that you can ping it
successfully, I will just send you a copy of this message. Please try
to read the instructions first.
Thanks,
Jay