|
|
| Author |
Message |
| 25 new of 292 responses total. |
jazz
|
|
response 225 of 292:
| 
Nov 20 13:54 UTC 1999 |
Yup, I was using "ISDN CODEC" for what most people mean when they're
talking about "ISDN modems" - the box that sits between the ISDN line jack,
acts as a terminator, and may or may not route packets or manage PPP or mlPPP.
In this case it's clearly acting as a router if it's doing NAT, so "ISDN
router" would be my term of choice, but I didn't want to rule out the
possibility it was a fairly dumb serial device like a Motorola Bitsurfr.
I was thinking the ISDN router would be the likely culprit, but now
I'm wondering, since it doesn't seem likely that the router would recieve the
packet in question under normal circumstances - since there was only one box
sitting behind the router at the time the problem was seen - and it would be
unlikely that a third party could produce a packet that accidentally matched
a source/destination port pair and sequence number for a telnet session, and
that still wouldn't explain the connection hanging, something which I hadn't
read correctly before (and therefore didn't take into account).
|
gull
|
|
response 226 of 292:
|
Nov 20 18:41 UTC 1999 |
I've always heard it referred to as an "ISDN pipeline," but that might be
some company's proprietary name for them.
|
scg
|
|
response 227 of 292:
|
Nov 20 20:37 UTC 1999 |
Pipeline is Ascend's name for its routers.
|
flem
|
|
response 228 of 292:
|
Nov 20 20:39 UTC 1999 |
I think the technical term is "ISDN thingy". :)
|
gelinas
|
|
response 229 of 292:
|
Nov 20 22:38 UTC 1999 |
ISDN router works. I know it's not really a modem, since modems convert
from digital to analog and back, but that's what 3Com calls it, probably
to avoid confusing J Random Dialup User with too much accuracy. ;)
|
mdw
|
|
response 230 of 292:
|
Nov 21 08:13 UTC 1999 |
Grex wouldn't know anything at all about the ISDN router. TCP header
compression works by taking all the bits that are easily predictable
(like the IP header, tcp sequence number, etc.), & throwing them out.
They're put back into the packet by the receiving end. As long as the
two ends don't get confused, there shouldn't be any problems doing this.
However, in Joe's case, one end is also handling ISDN connections from N
other users, and Joe's end is doing NAT translation. So both ends have
at least the opportunity to get confused, and send packet data, with
forged "apparently real" tcp sequence numbers out. These forged packets
will contain someone else's data, which will explain Joe's confusion,
and since the real sender doesn't know this packet was sent, the real
sender's tcp sequence number will be behind the client's sequence
number. So, when the real sender sends data to the client, the client
will just toss it as "old" data. If Joe can, typing blindly, convince
the other end to send enough data, he *might* be able to get it to
resync, but that would definitely be a pretty desperate measure.
|
gelinas
|
|
response 231 of 292:
|
Nov 21 23:37 UTC 1999 |
It just happened again:
be played on the 3d: It would interfere with Monday Night Football.
Or be confused with it.) So again not a good day for collegs
~
~
~
~
~
~ than ho rCcg.
Note the tildes. My cursor jumped from trying to enter the final 'e' in
college to a spot six lines down, with random text added as displayed.
I wonder what would have happened had I been typing in one of the other
telnet windows I had open at the time?
As before, the session hung until Grex closed it.
|
gelinas
|
|
response 232 of 292:
|
Nov 22 01:18 UTC 1999 |
Some additional comments:
I've been using my ISDN line since last November or December. The only
thing that has changed is that I now use grex instead of confer.itd.umich.edu
for my conferencing. Selective memory may be in play, but I really don't
remember seeing this kind of problem before I started using grex.
|
drew
|
|
response 233 of 292:
|
Nov 22 21:20 UTC 1999 |
I'm getting GOT errors and trashed participation files again.
|
krj
|
|
response 234 of 292:
|
Nov 22 21:32 UTC 1999 |
Out of disk space again:
/dev/sd2h 842574 748646 9671 99% /c
/dev/sd1c 1944365 1749411 518 100% /a
|
davel
|
|
response 235 of 292:
|
Nov 23 14:07 UTC 1999 |
Re 231: Looks like part of someone's vi session, somewhere.
|
pfv
|
|
response 236 of 292:
|
Nov 23 18:38 UTC 1999 |
Been an interesting morning - verio.net has twice fubared the routing into
grex.. Here's the latest "wtf?":
traceroute grex.org
traceroute to grex.org (204.212.46.130), 30 hops max, 40 byte packets
1 as1-nmc.gylr.mi.voyager.net (216.93.16.131) 166.663 ms 169.280 ms
169.717 ms
2 gld-router-pool.freeway.net (208.137.20.254) 169.105 ms 169.477 ms
159.741 ms
3 216.93.15.61 (216.93.15.61) 179.115 ms 259.464 ms 179.715 ms
4 rtr1-ethX-X.mnpl.mi.voyager.net (209.153.156.65) 179.366 ms 249.469
ms 289.710 ms
5 rtr1-ser3-0-9-0.lnng.mi.voyager.net (209.153.151.17) 329.174 ms
289.448 ms 269.706 ms
6 border1-hssi16-0.arb.qual.net (198.87.206.1) 299.168 ms 289.464 ms
279.710 ms
7 border1-hssi3-0.dtw.qual.net (131.103.4.5) 289.175 ms 189.480 ms
209.693 ms
8 serial1-1.csr0.cv.oh.verio.net (131.103.4.18) 209.181 ms 219.471 ms
199.705 ms
9 serial1-0.csr8.or.il.verio.net (131.103.5.1) 219.175 ms 219.448 ms
229.729 ms
10 ord0-0.qualnet-0.verio.net (129.250.16.78) 249.164 ms 239.469 ms
319.709 ms
11 ord0-0.qualnet-0.verio.net (129.250.16.78) 269.146 ms 239.462 ms
229.765 ms
12 ord0-0.qualnet-0.verio.net (129.250.16.78) 289.090 ms 289.485 ms
259.712 ms
13 ord0-0.qualnet-0.verio.net (129.250.16.78) 309.144 ms 289.478 ms
359.696 ms
14 ord0-0.qualnet-0.verio.net (129.250.16.78) 299.142 ms 339.465 ms *
15 ord0-0.qualnet-0.verio.net (129.250.16.78) 399.525 ms 399.464 ms
349.706 ms
16 * ord0-0.qualnet-0.verio.net (129.250.16.78) 369.888 ms 449.500 ms
17 * ord0-0.qualnet-0.verio.net (129.250.16.78) 509.894 ms 449.465 ms
18 * ord0-0.qualnet-0.verio.net (129.250.16.78) 489.888 ms *
19 * * grex.cyberspace.org (204.212.46.130) 409.898 ms
|
gelinas
|
|
response 237 of 292:
|
Nov 24 01:43 UTC 1999 |
re: #235: Yes, #231 records _my_ vi session, up until the s in "collegs" and
following, which was popped in from . . . somewhere. It is another example
of a recurring problem that I believe to be limited to grex.
|
gelinas
|
|
response 238 of 292:
|
Nov 24 03:16 UTC 1999 |
OK, folks, here it is:
>Back to vans. It looks like the choices are 1999 Dodge 1500 (Transedan or
>Sapphire) and 1999 Cheverolet Express 1500. We've taken both for
>familiarisation drives (not extensiv added an HTML version of the judge's
rulin
g. It's at
<a
href="http://www.cyberspace.org/lawsuit/injunction.html">ht
tp://www.cyberspace.org/lawsuit/injunction.html</a>
</PRE><br clear=all><hr>
#267
of 300 by Jan Wolter (<a href=/cgi-bin/bt/vanilla/bio?login=janc>janc</a>) on
Fr
i Jul 30 00:44:57 1999:<p>
<PRE>A couple notes on where things stand and where
th
ey are going, as I
understand it.
What we have now is a "preliminary
injunction".
This prevents
enforcement of the law until further rulings. It is *not* a
rulin
g that
the law is unconstitutional. It is just a ruling that says that the
likeli
hood of the law being found unconstitutional is high enough that
people
shouldn't
be prosecuted under it until it has been examined
further.
The ruling is quite
sa
tisfactory - Judge Tarnow appears to have pretty
much accepted all the ACLU's
rea
soning, and even added some arguments
against the law that they didn't make.
Thing
s do not end here. Lots of different things could happen next, but
the most
like
ly
|
gelinas
|
|
response 239 of 292:
|
Nov 24 03:22 UTC 1999 |
And it happened again:
>Cutting and pasting from window to another caused re-wrapping, but it iss
>QUstand that part about "there are still some males who believe
that lesbians..
." - could you explain what you meant there, Sonja?
</PRE><br clear=all><hr>
#6
of
12 by Sweet Pea (<a href=/cgi-bin/bt/vanilla/bio?login=simcha>simcha</a>) on
Tu
e Dec 27 08:14:31 1994:<p>
<PRE>Wow, are there a lot of women out there who must
be going out (read:
sleeping with) the wrong men! I have never had trouble
with
my "civil
rights" in bed! Im very mainstream,a nd believe that if you make
your
bed, you lie in it for any o
} I took time to rewrap the above to match what appeared on my screen. In
} at least the first instance, it is very clear that it is something from
} grex. I suspect the second is also recognisable (by some here) as being
} from grex.
|
scg
|
|
response 240 of 292:
|
Nov 24 05:06 UTC 1999 |
Hmm... So it looks like it's either Grex or Grex's routers. I just turned
off header compression on Grex's ISDN link, and also rebooted the Pipeline
on Grex's end of it, since it seemed generally confused. Let me know if the
problem goes away.
|
gelinas
|
|
response 241 of 292:
|
Nov 24 05:10 UTC 1999 |
Actually, I can only let you know when it happens. ;)
|
tsty
|
|
response 242 of 292:
|
Nov 25 08:43 UTC 1999 |
filled again ...
grex.cyberspace.org% df
Filesystem kbytes used avail capacity Mounted on
/dev/sd0a 109823 71181 27660 72% /
/dev/sd0d 156783 131196 9909 93% /usr
/dev/sd0e 706783 625481 10624 98% /usr/local
/dev/sd0f 471183 211699 212366 50% /x
/dev/sd2e 699223 565503 63798 90% /var
/dev/sd4h 1952573 861289 896027 49% /var/spool/mail
/dev/sd0h 284215 229821 25973 90% /bbs
/dev/sd2a 31023 12073 15848 43% /rootbak
/dev/sd2d 31023 12871 15050 46% /suidbin
/dev/sd2f 62863 588 55989 1% /tmp
/dev/sd2h 842574 750399 7918 99% /c
/dev/sd1c 1944365 1720330 29599 98% /a
g
|
otaking
|
|
response 243 of 292:
|
Nov 28 18:23 UTC 1999 |
When I tried to access my inbox in pine, I got an error message telling me
that no such file existed.
|
sno
|
|
response 244 of 292:
|
Dec 1 03:36 UTC 1999 |
I've finally figured out the problems I've been having with backspace on
grex. Frankly, I'm surprised that the basic configuration inquiry does
not automatically create a default file that simply includes the line:
tset -Q -e<backspace>
whatever that character might be. Since the newuser scripts *do* ask
what to use for backspace, it would seem appropriate to modify the
users .profile or .login to include this line.
The difficulty stems from the fact that a simple stty erase <backspace>
does not propagate to bbs. It's beyond me why. bbs fails to
inherit TTY settings within its environment and I've been fighting with
it ever since. So tonight I bashed and brooded over it until I came
to this solution. Perhaps my effort will help other Linux users be
able to use the grex system with less difficulty.
|
gelinas
|
|
response 245 of 292:
|
Dec 1 04:12 UTC 1999 |
Hmm... My .login says:
if ($?prompt) then
stty intr '^C' kill '^U' erase '^H'
I don't know why it chose ^H, but that's the right choice for me. Maybe
because of the check newuser did?
|
mcnally
|
|
response 246 of 292:
|
Dec 1 05:32 UTC 1999 |
You (gelinas) use csh and sno apparently uses bash (an sh variant..)
|
gelinas
|
|
response 247 of 292:
|
Dec 1 05:50 UTC 1999 |
That's what he meant by 'bashed'. :/
|
cmcgee
|
|
response 248 of 292:
|
Dec 3 02:40 UTC 1999 |
Hope this reboot solves the "few seconds to connect" problem. It's been
taking more than 80 seconds.
|
orinoco
|
|
response 249 of 292:
|
Dec 3 04:36 UTC 1999 |
it went much faster for me this time than it has been going recently.
|
