I connect between 46k and 50k RX & 26400 TX. I've noticed an problem which
causes the modem to stop receiving packets for long periods of time (2 to 10
seconds). This is horrible for file transfers. When I ping my PM from a dialup,
the timeouts tend to look like this:
64 bytes from 206.105.188.6: icmp_seq=36 ttl=255 time=100.2 ms
64 bytes from 206.105.188.6: icmp_seq=37 ttl=255 time=12960.2 ms
64 bytes from 206.105.188.6: icmp_seq=38 ttl=255 time=11970.3 ms
64 bytes from 206.105.188.6: icmp_seq=39 ttl=255 time=10980.3 ms
64 bytes from 206.105.188.6: icmp_seq=40 ttl=255 time=9990.4 ms
64 bytes from 206.105.188.6: icmp_seq=41 ttl=255 time=9001.1 ms
64 bytes from 206.105.188.6: icmp_seq=42 ttl=255 time=8010.4 ms
64 bytes from 206.105.188.6: icmp_seq=43 ttl=255 time=7020.3 ms
64 bytes from 206.105.188.6: icmp_seq=44 ttl=255 time=6030.3 ms
64 bytes from 206.105.188.6: icmp_seq=45 ttl=255 time=5040.3 ms
64 bytes from 206.105.188.6: icmp_seq=46 ttl=255 time=4050.2 ms
64 bytes from 206.105.188.6: icmp_seq=47 ttl=255 time=3070.3 ms
64 bytes from 206.105.188.6: icmp_seq=48 ttl=255 time=2080.3 ms
64 bytes from 206.105.188.6: icmp_seq=49 ttl=255 time=1090.2 ms
64 bytes from 206.105.188.6: icmp_seq=50 ttl=255 time=109.7 ms
64 bytes from 206.105.188.6: icmp_seq=51 ttl=255 time=100.1 ms
I'm connecting with V.42bis & LAP-M. I've tried disabling V.42bis and using
MNP, but I ended up with no compression and the same problem (except higher
ping times).
I've also tried to disable retraining & fallback/foward without much sucess (it
gets a lot worse).
Now, at first I thought it might be my phone lines causing the problem, so I
connected it to another phone line (which terminates at a different dmark), and
had the same problems. I then tried to connect it to yet another phone line and
had the exact same problem.
So, I sat on the PM3 and tried getting status reports on the modem. First I see
a TX of 50k, then after one of those bursts I see 46k, then I see 48k. My RX
speed (from pm3 perspective), never changes.
I'm curious, what would cause this problem? Bad firmware on the zoom? Problems
with the PRI? Overloaded Bell? It seemed to work fine just a few nights ago
(zip files downloaded at ~4.2K/s).
One more thing, why doesn't Zoom have their firmware on their web page?
Jordan
-- Jordan Mendelson : www.wserv.com/~jordy/ Web Services, Inc. : www.wserv.com