[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Slip Slidin' Away: Take 2.5
- To: mint@atari.archive.umich.edu
- Subject: Slip Slidin' Away: Take 2.5
- From: "troy (t.) carpenter" <troyc@bnr.ca>
- Date: Fri, 17 Feb 1995 12:21:00 -0500
- Sender: "troy (t.) carpenter" <troyc@bnr.ca>
- X400-content-type: P2-1984 (2)
- X400-mts-identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.076:17.01.95.17.23.18]
- X400-originator: /dd.id=1745965/g=troy/i=t/s=carpenter/@bnr.ca
Ok, I have tried everything that was recommended to try. In one last effort
to isolate the problem to either my system, or the remote system, here is
the result of my last test:
Here is the lowdown on what I've got for the PPP interface problem.
I called up the terminal server and got the following IP number:
47.31.132.2
(in the rest of this example, this certain terminal port gave me an MTU of 256)
I exited back to my local system and gave the following command:
slattach -t /dev/ttya -r 47.31.140.1 -l 47.31.132.2 -p ppp &
Which attaches device ttya (modem port) with the remote address 47.31.140.1,
which is the IP number for batpcts3, local interface number using the PPP
protocol.
The resulting routing table gives me the following:
Destination Gateway Flags Ref Use Metric Iface
default 47.31.140.1 UG 1 24 0 ppp0
47.31.132.2 * UH 1 0 0 lo0
47.31.140.1 * UH 1 0 0 ppp0
127.0.0.0 * U 1 16 0 lo0
192.0.2.1 * UH 1 40 0 lo0
Since the interface I was connected to was one that had MTU of 256, my
interfaces are configured as follows:
lo0: flags=0x4b<UP,BROADCAST,LOOPBACK,RUNNING>
inet 192.0.2.1 netmask 255.255.255.0 broadcast 192.0.2.255
metric 0 mtu 16384
in-packets 28 in-errors 0 collisions 0
out-packets 28 out-errors 0
ppp0: flags=0x51<UP,POINTOPOINT,RUNNING>
link-level-flags=0x0
inet 47.31.132.2 netmask 255.0.0.0 dstaddr 47.31.140.1
metric 0 mtu 256
in-packets 0 in-errors 0 collisions 0
out-packets 24 out-errors 0
Finally, my ttya is configured as follows:
speed 19200 baud;
erase = ^H; eol = ^M; min = 1; time = 0;
ignbrk -brkint -icrnl
-isig -icanon -iexten -echo -echoe -echok
I tried PINGing a remote machine and got 100% packet loss. I can see the SD
light on my modem flash to send the packets, but I never get a response (this
assures me that I am not receiving packets and my machine is throwing them
away).
This happens when I have MTU of 1500 also (the interface is configured for MTU
of 1500 in that case).
I have sent a similar message to my sysadmins with the above output in hopes
that they can determine if there is a probelm on their end.
Troy Carpenter
Bell-Northern Research
Atlanta, Georgia
troyc@bnr.ca
"You're so open minded that your brain leaked out" - Steve Taylor
*>>>>>>>>>>>>>>>>>> The best thing in life costs exactly that <<<<<<<<<<<<<<<*