cambler@polyslo.CalPoly.EDU (Fubar) (12/25/89)
G protocol strikes again. Here is a debug script from the system that I am
calling. Can someone explain a few things to me? (comments in /**/ are mine)
--- begin debug script ---
ufubar polyslo (12/25-00:19-22015) DEBUG (Local Enabled)
rmesg - 'U' imsg sync<\003\020>got it
imsg input<Ug\000>got 2
/* we're doing g. damn. :-) */
got Ug
send 077
rec h->cntl 073
send 061
state - 01
rec h->cntl 061
send 057
state - 03
rec h->cntl 053
state - 010
/* ok, this is the INITA,B,C stuff. of the h->cntl xyz, y is the xxx and
z is the yyy, what is x?
*/
Proto started g
Protocol Ug
ufubar fubarsys (12/25-00:19-22015) OK (startup ttyi38 9600 bps)
*** TOP *** - role=SLAVE
rmesg - '' pkcget: alarm 4001
/* here i have sent an "S d.blahblahblah..... 0666" message, but it didn't
see it. on my end, the packet was k=2, tt=2, xxx=1, yyy=0, len=64. it
was a long packet, null padded to 64 bytes. Is this right?
*/
Alarm while reading SYN - RXMIT
send 040
/* they send me RR0. This bug has been explained, so i SEND THE EXACT PACKET
THAT I JUST DESCRIBED ABOVE.
*/
rec h->cntl 0210
/* now, WHAT THE HECK IS THIS?!?!?! does the h->cntl mean that it thought it
was a CONTROL packet? I figured out that of the number, say, "abcd", that
b is the tt, c is the xxx, and d is the yyy. WHAT IS a?!
*/
end pksack 00
/* when yyy is 0, this is "end pksack 00". when yyy is 1, it is "end pksack
01". what is it?
*/
PKCGET stall for 0.065600 sec
PKCGET stall for 0.059300 sec
PKCGET stall for 0.053100 sec
PKCGET stall for 0.033300 sec
PKCGET stall for 0.028100 sec
rec h->cntl 0210
/* i guess this is where it sees my second try... */
end pksack 00
PKCGET stall for 0.065600 sec
PKCGET stall for 0.059300 sec
PKCGET stall for 0.053100 sec
PKCGET stall for 0.034300 sec
pkcget: alarm 7002
Alarm while reading SYN - RXMIT
send 020
/* from now on, i keep sending the same packet over and over, and they
keep sending RJ0 to me...
*/
rec h->cntl 0210
end pksack 00
PKCGET stall for 0.065600 sec
PKCGET stall for 0.059300 sec
PKCGET stall for 0.053100 sec
PKCGET stall for 0.034300 sec
pkcget: alarm 10003
Alarm while reading SYN - RXMIT
send 020
rec h->cntl 0210
end pksack 00
PKCGET stall for 0.065600 sec
PKCGET stall for 0.059300 sec
PKCGET stall for 0.053100 sec
PKCGET stall for 0.034300 sec
PKCGET stall for 0.020800 sec
pkcget: alarm 13004
Alarm while reading SYN - RXMIT
send 020
rec h->cntl 0210
end pksack 00
PKCGET stall for 0.065600 sec
PKCGET stall for 0.059300 sec
PKCGET stall for 0.050000 sec
PKCGET stall for 0.034300 sec
pkcget: alarm 16005
Alarm while reading SYN - RXMIT
send 020
ufubar fubarsys (12/25-00:21-22015) CAUGHT (SIGNAL 1)
ufubar fubarsys (12/25-00:21-22015) FAILED (conversation complete 0 sent 0 received)
exit code 1
/* until finally i just give up. */
--- end debug script ---
Sorry if i keep whining here, but i am getting REALLY MAD. I have tried
EVERYTHING. I hardcoded my tt, xxx, and yyy for all possible permutations
just to check, no go. all packet sizes are right, they're null padded, the
data is going out, and it's all valid.
Even gropes at straws would be appreciated.
--
Sig: ++Christopher(); | Fubar Systems BBS
Internet: cambler@polyslo.calpoly.edu | (805) 544-9234 3/12/24 8-N-1
Also: chris@fubarsys.slo.ca.us | San Luis Obispo, California
Bix: cambler | "G Protocol Sucks" -- Me.