Hi,
> >and disable natd and the firewall code, these delays go away so I am
> >assuming that it is natd/firewall/divert that is responsible for this
> >delay.
>
> I think that is a bad assumption.
[snip]
> I'm running FreeBSD 3.3 with IPFIREWALL, IPDIVERT, and natd also over a
> 56k modem, and I _never_ have seen the kind of slow echo effect you
> are speaking of, except on very rare occasions when _somebody_ between
> me and whichever machine I'm talking to happens to be dropping a lot of
> packets. And obviously, in those cases, it ain't the fault of my FreeBSD
> box.
>
> >Is there a parameter or anything that I can tune to eliminate or
> >reduce this affect?
>
> But seriously, next time it happens, try doing some pings to the remote
> system that you are telnetting to. Look for dropped packets. Doing a
> couple of traceroutes to the remote system from your location might pro-
> vide some useful info also.
OK, here's a little snippet from 'ping':
[bsd@vger]:/conf- ping dean
PING dean (10.26.2.60): 56 data bytes
64 bytes from 10.26.2.60: icmp_seq=0 ttl=252 time=3146.649 ms
64 bytes from 10.26.2.60: icmp_seq=1 ttl=252 time=2172.951 ms
64 bytes from 10.26.2.60: icmp_seq=2 ttl=252 time=1184.808 ms
64 bytes from 10.26.2.60: icmp_seq=3 ttl=252 time=198.578 ms
64 bytes from 10.26.2.60: icmp_seq=4 ttl=252 time=1725.051 ms
64 bytes from 10.26.2.60: icmp_seq=5 ttl=252 time=737.457 ms
64 bytes from 10.26.2.60: icmp_seq=6 ttl=252 time=128.368 ms
64 bytes from 10.26.2.60: icmp_seq=7 ttl=252 time=127.593 ms
64 bytes from 10.26.2.60: icmp_seq=8 ttl=252 time=160.611 ms
64 bytes from 10.26.2.60: icmp_seq=9 ttl=252 time=148.561 ms
64 bytes from 10.26.2.60: icmp_seq=10 ttl=252 time=138.905 ms
64 bytes from 10.26.2.60: icmp_seq=11 ttl=252 time=194.196 ms
64 bytes from 10.26.2.60: icmp_seq=12 ttl=252 time=226.685 ms
64 bytes from 10.26.2.60: icmp_seq=13 ttl=252 time=1194.855 ms
64 bytes from 10.26.2.60: icmp_seq=14 ttl=252 time=127.343 ms
64 bytes from 10.26.2.60: icmp_seq=15 ttl=252 time=138.772 ms
No dropped packets, but definitely some occasional long delays before
I get the echo. However, I must concede, based on other respondants,
that something else must be going on and I cannot necessarily
attribute this to divert/firewall/natd.
However, the above numbers don't really illustrate the long response
times that I experience while typing at the shell prompt, or in elm.
It's really frustrating.
I have an external US Robotics Sportster modem and I can see the rx/tx
leds which are both off during the times when there was a delay, so I
can confirm that there was no other line-contention on my end.
Currently, I am connected from my home into work via a ppp link. I
notice the delays primarily when connected into work. Here's a
traceroute from my home machine to my work machine:
[bsd@vger]:/bsd- traceroute dean
traceroute to dean (10.26.2.60), 30 hops max, 40 byte packets
1 R09d016Rb410nc0.net.sas.com (172.16.0.1) 120.659 ms 139.603 ms 121.679 ms
2 R01r025Rb319nc0.net.sas.com (172.25.1.2) 116.139 ms 113.945 ms 119.767 ms
3 R42axxxRb319nc0.net.sas.com (10.19.0.3) 118.763 ms 125.350 ms 184.147 ms
4 dean (10.26.2.60) 132.987 ms 119.363 ms 120.193 ms
Using netstat, I see 6 input errors on my ppp0 interface. I can't
account for the cause of these, maybe they are a clue:
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ppp0 1500 <Link> 68826 6 73148 0 0
ppp0 1500 172.16 brdean 68826 6 73148 0 0
Thanks for the suggestions. I'll keep looking.
-Brian
--
Brian Dean [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
