said:
>> Did you make sure that protocol and resources got installed to \mptn\etc.
>> This is a known and documented eCS install defect.
>Didn't appear to be a problem in my case. They were there.
Good. It's better that way.
>Since it's still a problem, I've enclosed a zip archive with these files.
>There were two protocol.ini files. One was in \IBMCOM and the other in
This is the one that is used. See your config.sys for details.
>\IBMCOM\MACS. The latter was renamed PROTOCO1.INI to distinguish it.
Driver vendors tend to distribute sample protocol.ini's. These typically
only have the driver specific section (port, IRQ, etc.)
A couple of comments. setup.cmd contains:
route add default 192.168.1.1 -hopcount 1
route add -net 192.168.1 192.168.1.1 -hopcount 1
The second one is redundant and should be deleted. You are already
sending packets with an otherwise unknown routing to 192.168.1.1
setup.cmd contains:
ifconfig lan0 192.168.1.14 netmask 255.255.255.0 metric 1 mtu 1500 802.3
This looks reasonable.
netstat shows:
Interface 10 Serial Interface dod
physical address 000000000000 MTU 1500
This is owned by Injoy. You might be able to trace it with:
iptrace dod
I don't know for sure.
Interface 11 Serial Interface ppp1
physical address 000000000001 MTU 1524
I have to assume this is set up by Injoy too, but I'm not sure about why
it exists.
>I did an IPTRACE on the gateway machine during an appropriate time.
>Nothing else was happening except InJoy was already connected to the
>'Net, the problem machine had Netscape open and simply made the request
>to load yahoo.com. I waited about 10 seconds to close down the iptrace
>since most of the action was done with by then. Even a couple of minutes
>later, yahoo still had not loaded on the intended machine. The text
>output of this is also in the archive called ipdump.txt.
Other than the lack of response, the trace looks like what I expect. The
trace appears to be capturing packets as they flow between the eCS machine
and the gateway machine. We are not seeing what Injoy is sending and
receiving over the dial-up connection. For that you can try:
iptrace dod ppp1
and some variants to see what, if anything works. If none of these work,
then try the trace built into Injoy. We really need to see what Injoy is
sending and receiving over the serial interface.
>The output of netstat -n (from the gateway machine) is also in the
>archive as netstat.txt. It's still a little Greek to me because it
>doesn't tell me anything.
-n is mostly statistics. It says you have 4 interfaces defined:
lan0 - the NIC
lo - the loopback interface
dod - Injoys DOD interface, whatever that is
ppp1 - Injoy's data interface, note the amount of traffic
>Sorry, I would have tried this if I understood the output of netstat -n.
Now you do. Try:
iptrace ppp1
and see if anything interesting gets captured. With luck it will look
like the trace you sent, but with different IP address because NAT did its
job.
Steven
--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.31a #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
---------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
Return to [ 04 |
July |
2002 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.