eeh@Dixie.Com (Ed Howland) (04/09/91)
I am having trouble installing the Ungermann-Bass nicps2 packet driver
and running it with Phil Karn's NET PC. I have installed the driver
and using no options like interupt#, IO Addr etc. it finds it just fine
and reports back just what I have my NCSA package set to. Then I installed
NET pc with the attach line in autoexec.net set to the recommended settings
'packet ...' (I forget them at the moment.). Net comes up without any errors
but when I try either telnet or ftp commands, (or trace) I get the message
'Host unreachable...'. Can anybody tell me what I am doing wrong?
My first attempt to fix this is to get the latest version of NET PC, the
version I have is suspect, although the package had some packet drivers with
it.
Confused, Hopeless and alone.....
--
Ed Howland Internet: eeh@dixie.com uucp: ...{uunet,emory}!rsiatl!eeh
"I am expressly forbidden to offer any kind of warranty. This covers ideas,
thoughts, opinions, or just plain gibberish. They are only offered 'As is'." nelson@sun.soe.clarkson.edu (Russ Nelson) (04/09/91)
In article <9385@rsiatl.Dixie.Com> eeh@Dixie.Com (Ed Howland) writes:
Net comes up without any errors but when I try either telnet or ftp
commands, (or trace) I get the message 'Host unreachable...'. Can
anybody tell me what I am doing wrong?
1) You probably don't have the routing statements set up properly.
2) KA9Q (aka NET, aka NOS) is only free for use by educational institutions
and radio amateurs.
--
--russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker.
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.eeh@Dixie.Com (Ed Howland) (04/10/91)
Please excuse if you saw my original post twice, our software seems to
duplicate the message going out.
But in order help people help me with the Clarkson driver + KA9Q Net PC
software, here is some sesions captures when I try to start things up.
After some experimentation I found out that my NCSA software had config.tel
interrupt=5. But when I call ubnicps2.com with:
ubnicps2 0x60 5 or with all parameters 0x60 5 0x1550 0xD000
it comes back with interrupt = 3. What gives. The .asm has some mysterious
thing about it always is 3??? The NCSA stuff works fine.
Anyway here is the data....
----Session capture of 'ubnicps2 0x60 5 0x1550 0xd000'
Packet driver for the ubnicps2, version 9.1.2
Packet driver skeleton copyright 1988-91, Russell Nelson.
This program is free software; see the file COPYING for details.
NO WARRANTY; see the file COPYING for details.
Packet driver is at segment 152D
TDR: Ok
Interrupt number 0x3 (3)
I/O port 0x1550 (5456)
Memory address 0xD000 (53248)
My Ethernet address is 00:DD:01:0A:05:0A
-----------------------------------------
----- lines from autoexec.net -----------
attach packet 0x60 eth 5 1500
#
ip ttl 16
#
tcp window 432
-----------------------------------------
---- hosts.net --------------------------
#
97.0.0.1 don
97.0.0.6 pluto
97.0.0.12 pickens
97.0.0.50 carthage
97.0.0.10 cobb
-----------------------------------------
---- Session capture from starting ------
-----net.exe and trying telnet don ------
KA9Q Internet Protocol Package, v871225.31 DS = 2dae
Copyright 1988 by Phil Karn, KA9Q
net> telnet don
SYN sent
Closed (ICMP: Host unreachable)
net> exit
-----------------------------------------
---- Comparison of NCSA config.tel lines-
hardware=nicps
interrupt=5 # hardware IRQ interrupt
address=d000
ioaddr=0x1550
---- THESE WORK with NCSA Telnet !!!!!!!
Thanks in advance.
Ed
--
Ed Howland Internet: eeh@dixie.com uucp: ...{uunet,emory}!rsiatl!eeh
"I am expressly forbidden to offer any kind of warranty. This covers ideas,
thoughts, opinions, or just plain gibberish. They are only offered 'As is'." nelson@sun.soe.clarkson.edu (Russ Nelson) (04/11/91)
In article <9436@rsiatl.Dixie.Com> eeh@Dixie.Com (Ed Howland) writes:
After some experimentation I found out that my NCSA software had config.tel
interrupt=5. But when I call ubnicps2.com with:
ubnicps2 0x60 5 or with all parameters 0x60 5 0x1550 0xD000
it comes back with interrupt = 3. What gives. The .asm has some mysterious
thing about it always is 3??? The NCSA stuff works fine.
The technical documentation says that it always uses interrupt 3. Perhaps
NCSA Telnet is ignoring the interrupt= parameter for the nic-ps/2 because
it doesn't make any sense for that adapter?
--
--russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker.
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.eeh@Dixie.Com (Ed Howland) (04/12/91)
Thanks to all who responded that my probelm with NOS was the missing
'route add default eth' line in autoexec.net.
Special thanks to Rich and Russ for further clarifications.
Ed.
--
Ed Howland Internet: eeh@dixie.com uucp: ...{uunet,emory}!rsiatl!eeh
Saw a licence (tag) 2day: JOJATK He must go to Georgia Tech. Can't spell tho.
"Support the concept of 'Organized Anarchy' on the net. Not too much though!"